speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

yaes.netlify.app

https://yaes.netlify.app/

100 100 100 100 1AXE –CWV

Data from Aug 21, 2026, 8:31 PM UTC 2d old

Build Awesome Starters #48 · 1 measurement · since Aug 21, 2026

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
100
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.44 s — — 1.44 s 1.44 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 773 ms — — 773 ms 773 ms
Speed Index 773 ms — — 773 ms 773 ms
TTFB Time to First Byte 603 ms — — 603 ms 603 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.44 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 33 ms
resource load delay 11 ms
resource load duration 9 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 120 kB — — 120 kB 120 kB
Requests 13 — — 13 13
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 57.8 kB · 1 req
font 45.0 kB · 3 req
document 6.9 kB · 1 req
other 5.4 kB · 3 req
script 3.4 kB · 1 req
stylesheet 598 B · 1 req

Page health

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

Main thread work

other 149 ms
script evaluation 31 ms
style layout 25 ms
parse HTML 6 ms
paint composite render 6 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 65 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 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, 8:31 PM UTC 100 1.44 s 0 0 ms 120 kB 3/3 ±0 2,457 21s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show yaes.netlify.app's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://yaes.netlify.app/"></speedlify2-score>