speedlify2

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

Measurement runs · Embed a score ·

lit.dev

https://lit.dev/

87 100 100 100 3AXE ✓CWV

Data from Aug 21, 2026, 3:10 AM UTC 2d old

Built Awesome #642 · 1 measurement · since Aug 21, 2026

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.

Go Hosted by Google Frontend

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-22 → 2026-08-18). This is what Google measures you on.

LCP 1.93 s good
INP 71 ms good
CLS 0 good

Scores

87
Performance
no change
100
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 3.98 s — — 3.98 s 3.98 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 100 ms — — 100 ms 100 ms
FCP First Contentful Paint 1.02 s — — 1.02 s 1.02 s
Speed Index 1.02 s — — 1.02 s 1.02 s
TTFB Time to First Byte 678 ms — — 678 ms 678 ms

What LCP is made of observed, unthrottled

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

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 3.98 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 446 ms
time to first byte 72 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-22 → 2026-08-18). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.93 s good 86.2% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 71 ms good 96.9% good
CLS CWV 0 good 99.6% good
FCP 997 ms good 90.3% good
TTFB 769 ms good 76% good

Lab vs field

Lab LCP 3.98 s · field p75 1.93 s · real users are 0.49× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.93 s 71 ms 0 994 ms 751 ms
2026-08-08 1.77 s 74 ms 0 993 ms 752 ms
2026-08-01 1.74 s 74 ms 0 976 ms 735 ms
2026-07-25 1.85 s 77 ms 0 1.05 s 788 ms
2026-07-18 1.85 s 78 ms 0 1.05 s 787 ms
2026-07-11 1.88 s 74 ms 0 1.04 s 779 ms
2026-07-04 1.91 s 72 ms 0 1.05 s 802 ms
2026-06-27 1.82 s 70 ms 0 1.02 s 766 ms
2026-06-20 1.73 s 69 ms 0 963 ms 738 ms
2026-06-13 1.77 s 71 ms 0 989 ms 768 ms
2026-06-06 1.80 s 71 ms 0 1.03 s 775 ms
2026-05-30 1.86 s 69 ms 0 1.03 s 801 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 512 kB — — 512 kB 512 kB
Requests 35 — — 35 35
Third-party Weight 156 kB — — 156 kB 156 kB
Third-party CPU 51 ms — — 51 ms 51 ms
Unused JS 69.7 kB — — 69.7 kB 69.7 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

font 289 kB · 8 req
script 197 kB · 17 req
document 18.9 kB · 1 req
image 4.7 kB · 5 req
other 3.4 kB · 4 req
third party 156 kB · 1 req

Third parties 1 entities

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

Google Tag Manager 156 kB · 51 ms CPU

Page health

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

Main thread work

script evaluation 277 ms
other 234 ms
style layout 180 ms
script parse compile 47 ms
paint composite render 44 ms
parse HTML 39 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 1 rule, 1007 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 3 nodes

Accessibility failures 1 of 28 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.

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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 21, 2026, 3:10 AM UTC 87 3.98 s 0 100 ms 512 kB 3/3 ±2 2,475 24.4s

Embed this score

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

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://lit.dev/"></speedlify2-score>