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 ·

simpleerb.com/blog

https://www.simpleerb.com/blog

70 94 100 92 0AXE CWV

Data from Aug 21, 2026, 7:33 PM UTC 2d old

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

This URL redirects to https://www.simpleerb.com/blog/.

A trailing slash only, so both forms are treated as one site rather than two — one history, measured once. Lighthouse follows the redirect, so the numbers below describe the canonical page; the only cost is an extra hop on each run.

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 Built with Eleventy
Netlify Hosted by Netlify

Core Web Vitals field data, origin-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

70
Performance
no change
94
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.90 s 2.90 s 2.90 s
CLS Cumulative Layout Shift 1.113 1.113 1.113
TBT Total Blocking Time 54 ms 54 ms 54 ms
FCP First Contentful Paint 1.51 s 1.51 s 1.51 s
Speed Index 1.51 s 1.51 s 1.51 s
TTFB Time to First Byte 603 ms 603 ms 603 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 2.90 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.

time to first byte 219 ms
element render delay 55 ms
resource load duration 14 ms
resource load delay 10 ms

Field data Chrome UX Report, origin-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.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 99 ms good 92.5% good
CLS CWV 0 good 99.8% good
FCP 821 ms good 95.6% good
TTFB 414 ms good 91.6% good

Lab vs field

Lab LCP 2.90 s · field p75 843 ms · real users are 0.29× 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 856 ms 103 ms 0 809 ms 415 ms
2026-08-08 872 ms 101 ms 0 821 ms 407 ms
2026-08-01 892 ms 96 ms 0 821 ms 400 ms
2026-07-25 915 ms 96 ms 0 832 ms 401 ms
2026-07-18 866 ms 91 ms 0 786 ms 400 ms
2026-07-11 859 ms 89 ms 0 759 ms 394 ms
2026-07-04 862 ms 90 ms 0 744 ms 384 ms
2026-06-27 831 ms 89 ms 0 719 ms 361 ms
2026-06-20 860 ms 88 ms 0 746 ms 378 ms
2026-06-13 882 ms 86 ms 0 787 ms 403 ms
2026-06-06 886 ms 83 ms 0 791 ms 415 ms
2026-05-30 814 ms 83 ms 0 749 ms 406 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 484 kB 484 kB 484 kB
Requests 16 16 16
Third-party Weight 200 kB 200 kB 200 kB
Third-party CPU 54 ms 54 ms 54 ms
Unused JS 78.9 kB 78.9 kB 78.9 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 234 kB · 3 req
script 217 kB · 5 req
other 14.5 kB · 5 req
stylesheet 10.1 kB · 1 req
document 8.2 kB · 1 req
third party 200 kB · 4 req

Third parties 3 entities

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

Google Tag Manager 174 kB · 40 ms CPU
Google Analytics 20.9 kB · 14 ms CPU
JSDelivr CDN 4.4 kB · 0 ms CPU

Page health

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

Main thread work

script evaluation 289 ms
other 172 ms
style layout 103 ms
paint composite render 55 ms
script parse compile 54 ms
parse HTML 19 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 644 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.

Accessibility failures 1 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

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, 7:33 PM UTC 70 2.90 s 1.113 54 ms 484 kB 3/3 ±15 2,477 24.5s

Embed this score

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