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 ·

cantautor.es

https://cantautor.es/

100 96 100 100 –CWV 5AXE

Data from Aug 20, 2026, 7:35 PM UTC — 23h old.

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

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 3.1.6 Built with Eleventy 3.1.6
Netlify Hosted by Netlify

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.84 s — — 1.84 s 1.84 s
CLS Cumulative Layout Shift 0.014 — — 0.014 0.014
TBT Total Blocking Time 23 ms — — 23 ms 23 ms
FCP First Contentful Paint 1.00 s — — 1.00 s 1.00 s
Speed Index 1.00 s — — 1.00 s 1.00 s
TTFB Time to First Byte 626 ms — — 626 ms 626 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 68 ms
resource load delay 30 ms
resource load duration 29 ms
time to first byte 27 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 325.2 kB — — 325.2 kB 325.2 kB
Requests 44 — — 44 44
Third-party Weight 2.4 kB — — 2.4 kB 2.4 kB
Third-party CPU 3 ms — — 3 ms 3 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 250.4 kB · 28 req
font 37.2 kB · 2 req
document 18.6 kB · 1 req
other 11.5 kB · 5 req
script 6.4 kB · 6 req
third party 2.4 kB · 2 req

Third parties 1 entities

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

Plausible 2.4 kB · 3 ms CPU

Page health

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

Main thread work

other 273 ms
style layout 264 ms
script evaluation 96 ms
parse HTML 79 ms
paint composite render 52 ms
script parse compile 20 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 1 rule, 1048 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 5 nodes

Accessibility failures 1 of 26 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. 6 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 20, 2026, 7:35 PM UTC 100 1.84 s 0.014 23 ms 325.2 kB 3/3 ±2 2,386 26.8s

Embed this score

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