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 ·

getzola.org

https://www.getzola.org/

100 97 100 100 2AXE ✓CWV

Data from Aug 23, 2026, 1:15 AM UTC 21h old

Site Generators #2 · 2 measurements · since Aug 22, 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.

GitHub Pages Hosted by GitHub Pages

Core Web Vitals field data, url-level

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

LCP 1.02 s good
INP 63 ms good
CLS 0 good

Scores

100
Performance
no change
97
Accessibility
no change
100
Best Practices
no change
100
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 792 ms 982 ms ↓ -190 ms (-19.3%) 792 ms 982 ms
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 792 ms 839 ms ↓ -47 ms (-5.6%) 792 ms 839 ms
Speed Index 792 ms 839 ms ↓ -47 ms (-5.6%) 792 ms 839 ms
TTFB Time to First Byte 609 ms 607 ms ↑ +2 ms (+0.3%) 607 ms 609 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 792 ms 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 52 ms
time to first byte 10 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.02 s good 96.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 63 ms good 98% good
CLS CWV 0 good 100% good
FCP 1.02 s good 90.2% good
TTFB 786 ms good 75.7% good

Lab vs field

Lab LCP 792 ms · field p75 1.02 s · real users are 1.29× slower 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 1.10 s 69 ms 0 1.12 s 825 ms
2026-08-08 1.12 s 69 ms 0 1.14 s 814 ms
2026-08-01 997 ms 65 ms 0 1.00 s 694 ms
2026-07-25 997 ms 68 ms 0 1.01 s 690 ms
2026-07-18 1.03 s 65 ms 0 1.04 s 694 ms
2026-07-11 1.04 s 60 ms 0 1.04 s 715 ms
2026-07-04 1.07 s 67 ms 0 1.07 s 767 ms
2026-06-27 1.05 s 61 ms 0 1.06 s 758 ms
2026-06-20 1.06 s 60 ms 0 1.06 s 768 ms
2026-06-13 1.01 s 66 ms 0 1.01 s 712 ms
2026-06-06 943 ms 63 ms 0 944 ms 605 ms
2026-05-30 1.01 s 63 ms 0 1.01 s 596 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 49.4 kB 49.5 kB ↓ -47 B (-0.1%) 49.4 kB 49.5 kB
Requests 8 8 → no change 8 8
Third-party Weight 0 B 0 B → no change 0 B 0 B
Third-party CPU 0 ms 0 ms → no change 0 ms 0 ms
Unused JS 0 B 0 B → no change 0 B 0 B
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

script 8.0 kB · 2 req
stylesheet 3.4 kB · 1 req
document 1.7 kB · 1 req
image 1.4 kB · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 155 ms 260 ms ↓ -105 ms (-40.3%) 155 ms 260 ms
Long Tasks 0 1 ↓ -1 (-100%) 0 1
DOM Elements 51 51 → no change 51 51
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 2 2 → no change 2 2
A11y Failures 1 1 → no change 1 1
A11y Failing Nodes 1 1 → no change 1 1

Main thread work

other 83 ms
style layout 47 ms
script evaluation 11 ms
parse HTML 5 ms
paint composite render 5 ms
script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 115 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 landmark-one-main — Document should have one main landmark 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 1 of 15 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.

  • 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

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 23, 2026, 1:15 AM UTC 100 792 ms 0 0 ms 49.4 kB 3/3 ±0 2,505 23.3s
Aug 22, 2026, 1:09 AM UTC 100 982 ms 0 0 ms 49.5 kB 3/3 ±0 2,477 24.4s

Embed this score

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