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 ·

htmlrecipes.dev

https://htmlrecipes.dev/

99 100 100 91 –CWV 16AXE

Data from Aug 20, 2026, 11:31 PM UTC — 19h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 19h

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

Scores

99
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.70 s — — 1.70 s 1.70 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.70 s — — 1.70 s 1.70 s
Speed Index 1.70 s — — 1.70 s 1.70 s
TTFB Time to First Byte 636 ms — — 636 ms 636 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 97 ms
time to first byte 38 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 14.1 kB — — 14.1 kB 14.1 kB
Requests 9 — — 9 9
Third-party Weight 2.7 kB — — 2.7 kB 2.7 kB
Third-party CPU 3 ms — — 3 ms 3 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

document 9.3 kB · 1 req
stylesheet 2.2 kB · 1 req
script 2.2 kB · 1 req
other 521 B · 1 req
third party 2.7 kB · 7 req

Third parties 1 entities

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

Plausible 2.7 kB · 3 ms CPU

Page health

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

Main thread work

style layout 108 ms
other 104 ms
paint composite render 25 ms
script evaluation 21 ms
parse HTML 19 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

16 violating nodes across 4 rules, 3031 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 scrollable-region-focusable — Scrollable region must have keyboard access 13 nodes
  • moderate landmark-main-is-top-level — Main landmark should not be contained in another landmark 1 node
  • moderate landmark-no-duplicate-main — Document should not have more than one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 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 20, 2026, 11:31 PM UTC 99 1.70 s 0 0 ms 14.1 kB 3/3 ±1 2,311 26.8s

Embed this score

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