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 ·

iturbides.dev

https://www.iturbides.dev/

95 98 100 100 –CWV 4AXE

Data from Aug 21, 2026, 1:00 PM UTC — 6h old.

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

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.

Eleventy Built with Eleventy
Netlify Hosted by Netlify

Scores

95
Performance
no change
98
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 2.31 s — — 2.31 s 2.31 s
CLS Cumulative Layout Shift 0.046 — — 0.046 0.046
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.31 s — — 2.31 s 2.31 s
Speed Index 2.31 s — — 2.31 s 2.31 s
TTFB Time to First Byte 629 ms — — 629 ms 629 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 98 ms
time to first byte 30 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 19.4 kB — — 19.4 kB 19.4 kB
Requests 10 — — 10 10
Third-party Weight 11.4 kB — — 11.4 kB 11.4 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

font 7.9 kB · 1 req
stylesheet 4.7 kB · 3 req
document 3.3 kB · 1 req
image 3.0 kB · 3 req
other 66 B · 1 req
third party 11.5 kB · 4 req

Third parties 2 entities

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

Google Fonts 9.8 kB · 0 ms CPU
licensebuttons.net 1.6 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 175 ms — — 175 ms 175 ms
Long Tasks 0 — — 0 0
DOM Elements 65 — — 65 65
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 105 ms
style layout 37 ms
paint composite render 13 ms
parse HTML 11 ms
script evaluation 9 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 2 rules, 143 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-one-main — Document should have one main landmark 1 node

Accessibility failures 1 of 19 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 21, 2026, 1:00 PM UTC 95 2.31 s 0.046 0 ms 19.4 kB 3/3 ±1 2,455 22.3s

Embed this score

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