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 ·

meinamsterdam.nl

https://meinamsterdam.nl/

56 96 73 100 16AXE –CWV

Data from Aug 22, 2026, 6:44 AM UTC 39h old

Built Awesome #1,073 · 4 measurements · since Aug 21, 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.

Eleventy 3.1.6 Built with Eleventy 3.1.6
Self-hosted · nginx Hosted by Self-hosted

Scores

56
Performance
no change
96
Accessibility
no change
73
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 15.53 s — — 15.53 s 15.53 s
CLS Cumulative Layout Shift 0.008 — — 0.008 0.008
TBT Total Blocking Time 73 ms — — 73 ms 73 ms
FCP First Contentful Paint 9.09 s — — 9.09 s 9.09 s
Speed Index 9.09 s — — 9.09 s 9.09 s
TTFB Time to First Byte 699 ms — — 699 ms 699 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 15.53 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 2.25 s
time to first byte 101 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.39 MB — — 1.39 MB 1.39 MB
Requests 139 — — 139 139
Third-party Weight 335 kB — — 335 kB 335 kB
Third-party CPU 183 ms — — 183 ms 183 ms
Unused JS 109 kB — — 109 kB 109 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 639 kB · 24 req
image 220 kB · 31 req
font 182 kB · 7 req
document 174 kB · 18 req
other 133 kB · 48 req
stylesheet 38.9 kB · 5 req
third party 1.23 MB · 125 req

Third parties 4 entities

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

Google/Doubleclick Ads 223 kB · 169 ms CPU
Google Fonts 89.4 kB · 0 ms CPU
adtrafficquality.google 21.3 kB · 11 ms CPU
bsky.app 1.6 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 2.65 s — — 2.65 s 2.65 s
Long Tasks 9 — — 9 9
DOM Elements 447 — — 447 447
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 16 — — 16 16
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

script evaluation 1.17 s
style layout 790 ms
other 525 ms
script parse compile 60 ms
paint composite render 59 ms
parse HTML 24 ms
garbage collection 19 ms

Axe violations axe-core 4.13.0, full rule set

16 violating nodes across 6 rules, 1239 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 page-has-heading-one — Page should contain a level-one heading 5 nodes
  • serious link-name — Links must have discernible text 4 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 2 nodes
  • serious frame-title — Frames must have an accessible name 2 nodes
  • critical image-alt — Images must have alternative text 2 nodes
  • serious aria-command-name — ARIA commands must have an accessible name 1 node

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

  • frame-title — `<frame>` or `<iframe>` elements do not have a title 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache http/1.1 3 console errors

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, 6:44 AM UTC 56 15.53 s 0.008 73 ms 1.39 MB 3/3 ±11 2,472 95.9s
Aug 21, 2026, 11:33 PM UTC TRACING_ALREADY_STARTED: An internal Chrome error occurred. Please restart Chrome and try re-running Lighthouse. 27.4s
Aug 21, 2026, 4:50 PM UTC lighthouse timed out after 120000ms 360.5s
Aug 21, 2026, 4:46 AM UTC TRACING_ALREADY_STARTED: An internal Chrome error occurred. Please restart Chrome and try re-running Lighthouse. 25.4s

Embed this score

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