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 ·

perrodinero.blog

https://perrodinero.blog/

98 100 100 100 –CWV 8AXE

Data from Aug 21, 2026, 4:41 AM UTC — 14h old.

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

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

98
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 2.43 s — — 2.43 s 2.43 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 905 ms — — 905 ms 905 ms
Speed Index 905 ms — — 905 ms 905 ms
TTFB Time to First Byte 605 ms — — 605 ms 605 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 40 ms
resource load duration 15 ms
resource load delay 9 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 347.7 kB — — 347.7 kB 347.7 kB
Requests 14 — — 14 14
Third-party Weight 29.0 kB — — 29.0 kB 29.0 kB
Third-party CPU 12 ms — — 12 ms 12 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 275.8 kB · 4 req
script 35.4 kB · 4 req
other 13.8 kB · 3 req
stylesheet 13.0 kB · 1 req
document 9.6 kB · 1 req
third party 29.0 kB · 1 req

Third parties 1 entities

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

JSDelivr CDN 29.0 kB · 12 ms CPU

Page health

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

Main thread work

other 118 ms
script evaluation 92 ms
style layout 77 ms
parse HTML 41 ms
paint composite render 19 ms
script parse compile 14 ms

Axe violations axe-core 4.13.0, full rule set

8 violating nodes across 1 rule, 457 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 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, 4:41 AM UTC 98 2.43 s 0 0 ms 347.7 kB 3/3 ±6 2,485 25s

Embed this score

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