speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

codeberg.page

https://codeberg.page/

59 76 100 91 8AXE CWV

Data from Aug 22, 2026, 10:20 PM UTC 23h old

Web Hosts #14 · 3 measurements · since Aug 20, 2026

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.

Self-hosted · git-pages Hosted by Self-hosted

Core Web Vitals field data, url-level

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

LCP 2.76 s needs-improvement
INP 69 ms good
CLS 0.020 good

Scores

59
Performance
no change
76
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 8.23 s 8.13 s ↑ +96 ms (+1.2%) 7.94 s 8.23 s
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 0 ms 0 ms → no change 0 ms 0 ms
FCP First Contentful Paint 7.15 s 7.10 s ↑ +47 ms (+0.7%) 6.95 s 7.15 s
Speed Index 7.15 s 7.10 s ↑ +47 ms (+0.7%) 6.95 s 7.15 s
TTFB Time to First Byte 718 ms 700 ms ↑ +18 ms (+2.6%) 699 ms 718 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 8.23 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 1.23 s
time to first byte 120 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.76 s needs-improvement 69.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 69 ms good 96.8% good
CLS CWV 0.020 good 93.9% good
FCP 2.77 s needs-improvement 58.6% good
TTFB 878 ms needs-improvement 68% good

Lab vs field

Lab LCP 8.23 s · field p75 2.76 s · real users are 0.34× 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.77 s 70 ms 0.020 2.79 s 890 ms
2026-08-08 2.81 s 69 ms 0.020 2.84 s 912 ms
2026-08-01 2.84 s 73 ms 0.020 2.88 s 899 ms
2026-07-25 2.66 s 74 ms 0.020 2.70 s 893 ms
2026-07-18 2.88 s 77 ms 0.020 2.94 s 986 ms
2026-07-11 2.84 s 80 ms 0.020 2.94 s 975 ms
2026-07-04 2.82 s 89 ms 0.020 2.98 s 973 ms
2026-06-27 2.77 s 84 ms 0.020 2.90 s 964 ms
2026-06-20 2.63 s 79 ms 0.020 2.73 s 869 ms
2026-06-13 2.54 s 76 ms 0.020 2.65 s 864 ms
2026-06-06 2.59 s 73 ms 0.020 2.64 s 884 ms
2026-05-30 2.52 s 76 ms 0.010 2.53 s 876 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.18 MB 1.18 MB ↓ -30 B 1.18 MB 1.18 MB
Requests 14 14 → no change 14 14
Third-party Weight 1.17 MB 1.17 MB ↓ -30 B 1.17 MB 1.17 MB
Third-party CPU 7 ms 6 ms ↑ +1 ms (+9.7%) significant 6 ms 7 ms
Unused JS 110 kB 110 kB → no change 110 kB 110 kB
Unused CSS 393 kB 393 kB → no change 393 kB 393 kB

By resource type

stylesheet 505 kB · 3 req
font 496 kB · 5 req
script 160 kB · 2 req
document 6.4 kB · 1 req
image 6.0 kB · 1 req
other 1.3 kB · 1 req
third party 1.17 MB · 12 req

Third parties 1 entities

1.17 MB transferred, 7 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

codeberg.org 1.17 MB · 7 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 325 ms 320 ms ↑ +6 ms (+1.7%) 295 ms 325 ms
Long Tasks 0 0 → no change 0 0
DOM Elements 222 222 → no change 222 222
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 8 8 → no change 8 8
A11y Failures 3 3 → no change 3 3
A11y Failing Nodes 5 5 → no change 5 5

Main thread work

other 168 ms
style layout 72 ms
parse HTML 40 ms
script evaluation 20 ms
script parse compile 17 ms
paint composite render 8 ms

Axe violations axe-core 4.13.0, full rule set

8 violating nodes across 4 rules, 263 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 4 nodes
  • moderate region — All page content should be contained by landmarks 2 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node

Accessibility failures 3 of 14 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. 3 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 1 node
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 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 22, 2026, 10:20 PM UTC 59 8.23 s 0 0 ms 1.18 MB 3/3 ±12 2,348 29.8s
Aug 21, 2026, 9:23 PM UTC 59 8.13 s 0 0 ms 1.18 MB 3/3 ±9 2,486 28.6s
Aug 20, 2026, 8:31 PM UTC 59 7.94 s 0 0 ms 1.18 MB 3/3 ±0 2,459 25.8s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show codeberg.page's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://codeberg.page/"></speedlify2-score>