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 ·

repado.com

https://repado.com/

60 94 58 85 ✗CWV 47AXE

Data from Aug 21, 2026, 2:41 PM UTC — 4h old.

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

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.5 Built with Eleventy 3.1.5
Self-hosted · Apache Hosted by Self-hosted

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 2.53 s needs-improvement
INP — no data
CLS 0 good

Scores

60
Performance
no change
94
Accessibility
no change
58
Best Practices
no change
85
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 9.55 s — — 9.55 s 9.55 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 286 ms — — 286 ms 286 ms
FCP First Contentful Paint 3.04 s — — 3.04 s 3.04 s
Speed Index 5.27 s — — 5.27 s 5.27 s
TTFB Time to First Byte 760 ms — — 760 ms 760 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 1.39 s
resource load duration 793 ms
time to first byte 156 ms
resource load delay 12 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.53 s needs-improvement 73.8% good
CLS CWV 0 good 97.6% good
FCP 2.20 s needs-improvement 61.4% good
TTFB 1.39 s needs-improvement 55.3% good

Lab vs field

Lab LCP 9.55 s · field p75 2.53 s · real users are 0.26× faster than the lab.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 2.64 s — 0 2.28 s 1.39 s
2026-08-08 — — — — —
2026-08-01 2.81 s — 0 2.34 s 1.23 s
2026-07-25 2.33 s — 0 2.14 s 1.19 s
2026-07-18 2.29 s — 0 1.82 s 1.11 s
2026-07-11 2.00 s — 0 1.72 s 977 ms
2026-07-04 2.29 s — 0 1.92 s 1.20 s
2026-06-27 2.35 s — 0 1.92 s 1.20 s
2026-06-20 2.35 s — 0 2.00 s 1.38 s
2026-06-13 2.51 s — 0 2.06 s 1.46 s
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.16 MB — — 4.16 MB 4.16 MB
Requests 61 — — 61 61
Third-party Weight 711.0 kB — — 711.0 kB 711.0 kB
Third-party CPU 202 ms — — 202 ms 202 ms
Unused JS 211.6 kB — — 211.6 kB 211.6 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

media 1.90 MB · 3 req
image 1.50 MB · 26 req
script 603.2 kB · 14 req
font 115.7 kB · 3 req
stylesheet 18.3 kB · 6 req
document 8.9 kB · 1 req
other 6.8 kB · 8 req
third party 711.0 kB · 22 req

Third parties 7 entities

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

Google Tag Manager 500.0 kB · 173 ms CPU
Google Fonts 120.1 kB · 0 ms CPU
LinkedIn Ads 41.3 kB · 13 ms CPU
Cloudflare CDN 23.1 kB · 7 ms CPU
Google Analytics 20.9 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.46 s — — 1.46 s 1.46 s
Long Tasks 5 — — 5 5
DOM Elements 353 — — 353 353
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 47 — — 47 47
A11y Failures 1 — — 1 1
A11y Failing Nodes 18 — — 18 18

Main thread work

script evaluation 745 ms
other 348 ms
style layout 158 ms
script parse compile 154 ms
paint composite render 29 ms
parse HTML 28 ms

Axe violations axe-core 4.13.0, full rule set

47 violating nodes across 3 rules, 538 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 28 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 18 nodes
  • minor empty-heading — Headings should not be empty 1 node

Accessibility failures 1 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. 18 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, 2:41 PM UTC 60 9.55 s 0 286 ms 4.16 MB 3/3 ±1 2,492 33.9s

Embed this score

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