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 ·

elrastrillo.pe

https://elrastrillo.pe/

98 77 92 100 –CWV 32AXE

Data from Aug 20, 2026, 9:28 PM UTC — 21h old.

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

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
Li Hosted by Self-hosted

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP — no data
INP — no data
CLS — no data

Scores

98
Performance
no change
77
Accessibility
no change
92
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.44 s — — 2.44 s 2.44 s
CLS Cumulative Layout Shift 0.003 — — 0.003 0.003
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 816 ms — — 816 ms 816 ms
Speed Index 816 ms — — 816 ms 816 ms
TTFB Time to First Byte 643 ms — — 643 ms 643 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.

resource load delay 193 ms
resource load duration 51 ms
time to first byte 46 ms
element render delay 29 ms

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 — — — — —
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 — — — — —
2026-07-18 — — — — —
2026-07-11 — — — — —
2026-07-04 — — — — —
2026-06-27 — — — — —
2026-06-20 — — — — —
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.23 MB — — 1.23 MB 1.23 MB
Requests 64 — — 64 64
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 1.04 MB · 58 req
font 177.4 kB · 2 req
stylesheet 5.6 kB · 1 req
document 4.1 kB · 1 req
script 1.4 kB · 2 req

Page health

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

Main thread work

other 264 ms
style layout 57 ms
paint composite render 44 ms
script evaluation 27 ms
parse HTML 11 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

32 violating nodes across 6 rules, 433 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 18 nodes
  • moderate region — All page content should be contained by landmarks 9 nodes
  • critical button-name — Buttons must have discernible text 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • serious link-name — Links must have discernible text 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 4 of 17 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. 11 nodes
  • button-name — Buttons do not have an accessible name 3 nodes
  • link-name — Links do not have a discernible name 1 node
  • 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 1 console error

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, 9:28 PM UTC 98 2.44 s 0.003 0 ms 1.23 MB 3/3 ±15 3,269 26.1s

Embed this score

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