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 ·

webperformancereport.com

https://webperformancereport.com/

85 97 96 100 CWV 20AXE

Data from Aug 21, 2026, 10:32 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

Scores

85
Performance
no change
97
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.90 s 3.90 s 3.90 s
CLS Cumulative Layout Shift 0.036 0.036 0.036
TBT Total Blocking Time 137 ms 137 ms 137 ms
FCP First Contentful Paint 1.98 s 1.98 s 1.98 s
Speed Index 2.83 s 2.83 s 2.83 s
TTFB Time to First Byte 1.05 s 1.05 s 1.05 s

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.

resource load duration 522 ms
time to first byte 521 ms
element render delay 47 ms
resource load delay 11 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 458.0 kB 458.0 kB 458.0 kB
Requests 21 21 21
Third-party Weight 320.8 kB 320.8 kB 320.8 kB
Third-party CPU 105 ms 105 ms 105 ms
Unused JS 116.8 kB 116.8 kB 116.8 kB
Unused CSS 12.8 kB 12.8 kB 12.8 kB

By resource type

script 320.2 kB · 5 req
image 78.0 kB · 6 req
font 35.9 kB · 2 req
document 11.2 kB · 2 req
stylesheet 9.8 kB · 1 req
other 1.2 kB · 2 req
third party 321.7 kB · 7 req

Third parties 3 entities

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

Google Tag Manager 163.8 kB · 62 ms CPU
Cookiebot 145.4 kB · 39 ms CPU
Cloudflare 11.6 kB · 4 ms CPU

Page health

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

Main thread work

script evaluation 415 ms
other 216 ms
style layout 142 ms
script parse compile 120 ms
parse HTML 65 ms
paint composite render 48 ms
garbage collection 19 ms

Axe violations axe-core 4.13.0, full rule set

20 violating nodes across 1 rule, 1120 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 20 nodes

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

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 20 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 5 console errors

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:32 AM UTC 85 3.90 s 0.036 137 ms 458.0 kB 3/3 ±17 2,303 33.9s

Embed this score

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