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 ·

slrconsulting.com

https://www.slrconsulting.com/

48 96 77 92 ✓CWV 1AXE

Data from Aug 21, 2026, 1:54 PM UTC — 5h old.

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

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

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 2.46 s good
INP 159 ms good
CLS 0.020 good

Scores

48
Performance
no change
96
Accessibility
no change
77
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 9.04 s — — 9.04 s 9.04 s
CLS Cumulative Layout Shift 0.190 — — 0.190 0.190
TBT Total Blocking Time 278 ms — — 278 ms 278 ms
FCP First Contentful Paint 3.41 s — — 3.41 s 3.41 s
Speed Index 6.31 s — — 6.31 s 6.31 s
TTFB Time to First Byte 644 ms — — 644 ms 644 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.31 s
time to first byte 63 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 2.46 s good 74.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 159 ms good 82.3% good
CLS CWV 0.020 good 79.5% good
FCP 1.81 s needs-improvement 74.9% good
TTFB 796 ms good 75.2% good

Lab vs field

Lab LCP 9.04 s · field p75 2.46 s · real users are 0.27× 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 2.68 s 159 ms 0.030 1.95 s 877 ms
2026-08-08 2.80 s 160 ms 0.050 2.08 s 945 ms
2026-08-01 2.93 s 170 ms 0.050 2.15 s 1.06 s
2026-07-25 3.08 s 176 ms 0.070 2.30 s 1.12 s
2026-07-18 2.98 s 178 ms 0.080 2.23 s 1.09 s
2026-07-11 2.96 s 176 ms 0.090 2.20 s 1.09 s
2026-07-04 2.80 s 171 ms 0.090 2.10 s 994 ms
2026-06-27 2.81 s 173 ms 0.120 2.07 s 1.01 s
2026-06-20 2.88 s 171 ms 0.140 2.09 s 1.06 s
2026-06-13 2.72 s 172 ms 0.140 2.02 s 1.01 s
2026-06-06 2.80 s 174 ms 0.090 2.15 s 1.06 s
2026-05-30 2.74 s 171 ms 0.100 1.99 s 980 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.46 MB — — 4.46 MB 4.46 MB
Requests 54 — — 54 54
Third-party Weight 4.05 MB — — 4.05 MB 4.05 MB
Third-party CPU 167 ms — — 167 ms 167 ms
Unused JS 171.4 kB — — 171.4 kB 171.4 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

media 3.35 MB · 1 req
script 572.0 kB · 28 req
image 426.8 kB · 10 req
font 60.5 kB · 3 req
document 19.9 kB · 1 req
stylesheet 15.6 kB · 1 req
other 11.7 kB · 6 req
third party 4.05 MB · 20 req

Third parties 5 entities

4.05 MB transferred, 167 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

sanity.io 3.58 MB · 0 ms CPU
Google Tag Manager 318.0 kB · 91 ms CPU
Hubspot 125.9 kB · 46 ms CPU
Cookie-Script.com 29.2 kB · 31 ms CPU
Google Analytics 48 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 1.49 s
other 701 ms
style layout 408 ms
script parse compile 154 ms
paint composite render 143 ms
parse HTML 45 ms
garbage collection 42 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 1222 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 heading-order — Heading levels should only increase by one 1 node

Accessibility failures 2 of 34 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.

  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • link-in-text-block — Links rely on color to be distinguishable. 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, 1:54 PM UTC 48 9.04 s 0.190 278 ms 4.46 MB 3/3 ±3 2,529 45.9s

Embed this score

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