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 ·

simpleerb.com

https://www.simpleerb.com/

77 86 77 100 ✓CWV 2AXE

Data from Aug 21, 2026, 6:41 PM UTC — 32m old.

Built Awesome · 2 measurements · since Aug 21, 2026 · last attempt 32m

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.

Eleventy 2.0.1 Built with Eleventy 2.0.1
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 843 ms good
INP 99 ms good
CLS 0 good

Scores

77
Performance
no change
86
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.66 s — — 4.66 s 4.66 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 297 ms — — 297 ms 297 ms
FCP First Contentful Paint 989 ms — — 989 ms 989 ms
Speed Index 989 ms — — 989 ms 989 ms
TTFB Time to First Byte 606 ms — — 606 ms 606 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 6 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 843 ms good 97.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 99 ms good 92.4% good
CLS CWV 0 good 100% good
FCP 824 ms good 95.5% good
TTFB 411 ms good 91.6% good

Lab vs field

Lab LCP 4.66 s · field p75 843 ms · real users are 0.18× 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 847 ms 103 ms 0 821 ms 413 ms
2026-08-08 868 ms 101 ms 0 830 ms —
2026-08-01 874 ms 96 ms 0 829 ms —
2026-07-25 912 ms 96 ms 0 838 ms 401 ms
2026-07-18 862 ms 91 ms 0 800 ms 400 ms
2026-07-11 857 ms 90 ms 0 762 ms 393 ms
2026-07-04 859 ms 90 ms 0 744 ms 384 ms
2026-06-27 829 ms 89 ms 0 720 ms 358 ms
2026-06-20 856 ms 88 ms 0 748 ms 374 ms
2026-06-13 886 ms 86 ms 0 791 ms 397 ms
2026-06-06 890 ms 83 ms 0 792 ms 415 ms
2026-05-30 824 ms 85 ms 0 752 ms 405 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.34 MB — — 1.34 MB 1.34 MB
Requests 20 — — 20 20
Third-party Weight 558.5 kB — — 558.5 kB 558.5 kB
Third-party CPU 220 ms — — 220 ms 220 ms
Unused JS 209.7 kB — — 209.7 kB 209.7 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 712.9 kB · 4 req
script 575.9 kB · 8 req
document 28.0 kB · 1 req
other 14.3 kB · 5 req
stylesheet 10.2 kB · 1 req
third party 558.5 kB · 11 req

Third parties 6 entities

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

Google Tag Manager 347.9 kB · 111 ms CPU
Facebook 175.6 kB · 86 ms CPU
Google Analytics 20.9 kB · 13 ms CPU
Twitter Online Conversion Tracking 13.9 kB · 11 ms CPU
Twitter Short URL 154 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 825 ms
other 201 ms
script parse compile 167 ms
style layout 100 ms
parse HTML 52 ms
paint composite render 20 ms
garbage collection 18 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 832 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 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 3 of 21 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.

  • button-name — Buttons do not have an accessible name 1 node
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 1 node
  • heading-order — Heading elements are not in a sequentially-descending order 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, 6:41 PM UTC 77 4.66 s 0 297 ms 1.34 MB 3/3 ±18 2,330 28.3s
Aug 21, 2026, 11:36 AM UTC TRACING_ALREADY_STARTED: An internal Chrome error occurred. Please restart Chrome and try re-running Lighthouse. 23.3s

Embed this score

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