speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

11tytips.netlify.app

https://11tytips.netlify.app/

87 98 100 100 –CWV 61AXE

Data from Aug 20, 2026, 3:35 PM UTC — 27h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 27h

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

Netlify Hosted by Netlify

Scores

87
Performance
no change
98
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.67 s — — 1.67 s 1.67 s
CLS Cumulative Layout Shift 0.245 — — 0.245 0.245
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.56 s — — 1.56 s 1.56 s
Speed Index 1.56 s — — 1.56 s 1.56 s
TTFB Time to First Byte 608 ms — — 608 ms 608 ms

What LCP is made of

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

element render delay 77 ms
time to first byte 9 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 70.1 kB — — 70.1 kB 70.1 kB
Requests 17 — — 17 17
Third-party Weight 2.8 kB — — 2.8 kB 2.8 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 39.6 kB · 2 req
script 13.7 kB · 4 req
document 6.7 kB · 2 req
other 4.5 kB · 4 req
stylesheet 3.8 kB · 4 req
image 1.8 kB · 1 req
third party 2.9 kB · 3 req

Third parties 2 entities

2.8 kB transferred, 0 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Netlify 1.8 kB · 0 ms CPU
instant.page 1.0 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 459 ms — — 459 ms 459 ms
Long Tasks 0 — — 0 0
DOM Elements 218 — — 218 218
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 61 — — 61 61
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

other 222 ms
style layout 135 ms
script evaluation 52 ms
paint composite render 25 ms
parse HTML 19 ms
script parse compile 6 ms

Axe violations axe-core 4.13.0, full rule set

61 violating nodes across 2 rules, 242 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • moderate region — All page content should be contained by landmarks 60 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 1 of 18 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 20, 2026, 3:35 PM UTC 87 1.67 s 0.245 0 ms 70.1 kB 3/3 ±5 2,275 21.6s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show 11tytips.netlify.app's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify-score.js component code into your site! 

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://11tytips.netlify.app/"></speedlify-score>