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 ·

webawesome.com

https://webawesome.com/

56 97 100 100 ✗CWV 8AXE

Data from Aug 21, 2026, 10:31 AM UTC — 8h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 8h

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.

Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

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

LCP 6.22 s poor
INP 337 ms needs-improvement
CLS 0.070 good

Scores

56
Performance
no change
97
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 5.69 s — — 5.69 s 5.69 s
CLS Cumulative Layout Shift 0.043 — — 0.043 0.043
TBT Total Blocking Time 642 ms — — 642 ms 642 ms
FCP First Contentful Paint 2.46 s — — 2.46 s 2.46 s
Speed Index 5.10 s — — 5.10 s 5.10 s
TTFB Time to First Byte 660 ms — — 660 ms 660 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 2.02 s
resource load duration 257 ms
time to first byte 44 ms
resource load delay 10 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 6.22 s poor 31.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 337 ms needs-improvement 56% good
CLS CWV 0.070 good 82.5% good
FCP 6.20 s poor 24.1% good
TTFB 1.20 s needs-improvement 54% good

Lab vs field

Lab LCP 5.69 s · field p75 6.22 s · real users are 1.09× slower 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 6.24 s 336 ms 0.060 6.20 s 1.20 s
2026-08-08 6.24 s 334 ms 0.060 6.20 s 1.20 s
2026-08-01 6.09 s 336 ms 0.060 5.99 s 1.15 s
2026-07-25 5.84 s 339 ms 0.050 5.82 s 1.13 s
2026-07-18 5.76 s 348 ms 0.050 5.79 s 1.13 s
2026-07-11 5.68 s 329 ms 0.050 5.76 s 1.14 s
2026-07-04 5.34 s 329 ms 0.030 5.76 s 1.17 s
2026-06-27 5.69 s 319 ms 0.030 5.99 s 1.24 s
2026-06-20 5.82 s 303 ms 0.010 6.11 s 1.17 s
2026-06-13 5.84 s 351 ms 0 6.13 s 1.13 s
2026-06-06 5.87 s 315 ms 0 5.82 s 1.07 s
2026-05-30 6.10 s 282 ms 0 6.03 s 1.04 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 807.2 kB — — 807.2 kB 807.2 kB
Requests 347 — — 347 347
Third-party Weight 215.1 kB — — 215.1 kB 215.1 kB
Third-party CPU 40 ms — — 40 ms 40 ms
Unused JS 97.4 kB — — 97.4 kB 97.4 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 385.7 kB · 178 req
other 237.8 kB · 116 req
font 79.6 kB · 3 req
stylesheet 50.4 kB · 38 req
document 31.0 kB · 1 req
image 16.5 kB · 1 req
third party 215.1 kB · 116 req

Third parties 3 entities

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

posthog.com 117.7 kB · 39 ms CPU
FontAwesome CDN 64.5 kB · 0 ms CPU
JSDelivr CDN 32.9 kB · 1 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.80 s — — 3.80 s 3.80 s
Long Tasks 15 — — 15 15
DOM Elements 4,961 — — 4,961 4,961
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 8 — — 8 8
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

script evaluation 1.39 s
other 1.26 s
style layout 801 ms
parse HTML 143 ms
garbage collection 112 ms
script parse compile 59 ms
paint composite render 31 ms

Axe violations axe-core 4.13.0, full rule set

8 violating nodes across 3 rules, 1544 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.

  • serious aria-tab-name — ARIA tab nodes must have an accessible name 4 nodes
  • moderate region — All page content should be contained by landmarks 3 nodes
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 1 node

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

  • target-size — Touch targets do not have sufficient size or spacing. 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, 10:31 AM UTC 56 5.69 s 0.043 642 ms 807.2 kB 3/3 ±1 2,350 41.8s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show webawesome.com'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://webawesome.com/"></speedlify-score>