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 ·

cookingtimers.org

https://www.cookingtimers.org/

83 96 100 100 –CWV 4AXE

Data from Aug 21, 2026, 11:31 AM UTC — 7h old.

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

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.

Cloudflare Hosted by Cloudflare

Scores

83
Performance
no change
96
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 4.38 s — — 4.38 s 4.38 s
CLS Cumulative Layout Shift 0.010 — — 0.010 0.010
TBT Total Blocking Time 127 ms — — 127 ms 127 ms
FCP First Contentful Paint 1.68 s — — 1.68 s 1.68 s
Speed Index 1.68 s — — 1.68 s 1.68 s
TTFB Time to First Byte 466 ms — — 466 ms 466 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 165 ms
time to first byte 24 ms
resource load duration 22 ms
resource load delay 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 577.0 kB — — 577.0 kB 577.0 kB
Requests 12 — — 12 12
Third-party Weight 274.6 kB — — 274.6 kB 274.6 kB
Third-party CPU 42 ms — — 42 ms 42 ms
Unused JS 143.2 kB — — 143.2 kB 143.2 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 291.3 kB · 1 req
script 274.4 kB · 5 req
stylesheet 5.0 kB · 2 req
document 3.1 kB · 1 req
other 1.1 kB · 2 req
third party 274.6 kB · 5 req

Third parties 3 entities

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

Google Tag Manager 171.9 kB · 28 ms CPU
JSDelivr CDN 91.2 kB · 11 ms CPU
Cloudflare 11.5 kB · 4 ms CPU

Page health

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

Main thread work

script evaluation 273 ms
other 118 ms
script parse compile 73 ms
style layout 21 ms
parse HTML 7 ms
paint composite render 7 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 1 rule, 328 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 4 nodes

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

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 4 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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, 11:31 AM UTC 83 4.38 s 0.010 127 ms 577.0 kB 3/3 ±3 2,513 22.8s

Embed this score

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