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 ·

wiltomakesfood.com

https://wiltomakesfood.com/

100 96 100 100 ✓CWV 4AXE

Data from Aug 21, 2026, 5:15 PM UTC — 1h old.

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

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-23 → 2026-08-19). This is what Google measures you on.

LCP 1.60 s good
INP — no data
CLS 0 good

Scores

100
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 1.65 s — — 1.65 s 1.65 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 904 ms — — 904 ms 904 ms
Speed Index 904 ms — — 904 ms 904 ms
TTFB Time to First Byte 604 ms — — 604 ms 604 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 56 ms
resource load delay 13 ms
resource load duration 8 ms
time to first byte 5 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 1.60 s good 90.1% good
CLS CWV 0 good 95.9% good
FCP 1.55 s good 81.7% good
TTFB 804 ms needs-improvement 74.1% good

Lab vs field

Lab LCP 1.65 s · field p75 1.60 s · real users are 0.97× 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 1.59 s — 0 1.55 s 798 ms
2026-08-08 1.50 s — 0 1.46 s 758 ms
2026-08-01 1.51 s — 0 1.50 s 784 ms
2026-07-25 1.46 s — 0 1.42 s 711 ms
2026-07-18 1.40 s — 0 1.39 s 697 ms
2026-07-11 1.47 s — 0 1.40 s 704 ms
2026-07-04 1.41 s — 0 1.35 s 652 ms
2026-06-27 1.48 s — 0 1.40 s 697 ms
2026-06-20 1.48 s — 0 1.40 s 693 ms
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.09 MB — — 1.09 MB 1.09 MB
Requests 23 — — 23 23
Third-party Weight 257.8 kB — — 257.8 kB 257.8 kB
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 969.2 kB · 12 req
font 92.5 kB · 3 req
stylesheet 13.3 kB · 1 req
other 9.2 kB · 3 req
document 6.6 kB · 1 req
script 1.9 kB · 3 req
third party 257.8 kB · 3 req

Third parties 1 entities

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

Cloudinary 257.8 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 281 ms — — 281 ms 281 ms
Long Tasks 0 — — 0 0
DOM Elements 224 — — 224 224
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 8 — — 8 8

Main thread work

other 169 ms
style layout 51 ms
parse HTML 22 ms
script evaluation 21 ms
paint composite render 16 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 2 rules, 362 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 3 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

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.

  • target-size — Touch targets do not have sufficient size or spacing. 8 nodes

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:15 PM UTC 100 1.65 s 0 0 ms 1.09 MB 3/3 ±1 2,433 23.6s

Embed this score

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