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 ·

robinrendle.com

https://robinrendle.com/

76 94 100 100 CWV 13AXE

Data from Aug 21, 2026, 5:42 AM UTC — 13h old.

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

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, origin-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP no data
INP no data
CLS no data

Scores

76
Performance
no change
94
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 6.38 s 6.38 s 6.38 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.81 s 1.81 s 1.81 s
Speed Index 1.81 s 1.81 s 1.81 s
TTFB Time to First Byte 609 ms 609 ms 609 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 134 ms
resource load delay 77 ms
resource load duration 27 ms
time to first byte 11 ms

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15
2026-08-08
2026-08-01
2026-07-25
2026-07-18
2026-07-11
2026-07-04
2026-06-27
2026-06-20
2026-06-13
2026-06-06
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.14 MB 1.14 MB 1.14 MB
Requests 8 8 8
Third-party Weight 0 B 0 B 0 B
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 930.2 kB · 2 req
font 164.0 kB · 1 req
document 38.7 kB · 1 req
other 1.6 kB · 2 req

Page health

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

Main thread work

other 174 ms
style layout 89 ms
parse HTML 80 ms
script evaluation 29 ms
paint composite render 8 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

13 violating nodes across 4 rules, 199 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 region — All page content should be contained by landmarks 6 nodes
  • serious nested-interactive — Interactive controls must not be nested 5 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node

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

  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 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, 5:42 AM UTC 76 6.38 s 0 0 ms 1.14 MB 3/3 ±1 2,334 26.6s

Embed this score

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