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 ·

filtercoffee.netlify.app

https://filtercoffee.netlify.app/

100 95 100 92 –CWV 4AXE

Data from Aug 20, 2026, 10:33 PM UTC — 20h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 20h

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

100
Performance
no change
95
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 1.11 s — — 1.11 s 1.11 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 813 ms — — 813 ms 813 ms
Speed Index 813 ms — — 813 ms 813 ms
TTFB Time to First Byte 657 ms — — 657 ms 657 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.

time to first byte 80 ms
resource load duration 59 ms
element render delay 17 ms
resource load delay 8 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 55.9 kB — — 55.9 kB 55.9 kB
Requests 3 — — 3 3
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 54.8 kB · 1 req
document 831 B · 1 req
stylesheet 324 B · 1 req

Page health

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

Main thread work

other 53 ms
script evaluation 8 ms
style layout 5 ms
parse HTML 3 ms
paint composite render 2 ms
garbage collection 1 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 3 rules, 11 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 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

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

  • landmark-one-main — Document does not have a main landmark. 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, 10:33 PM UTC 100 1.11 s 0 0 ms 55.9 kB 3/3 ±0 3,371 20.2s

Embed this score

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