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 ·

lamprecht-rechtsanwaelte.de

https://www.lamprecht-rechtsanwaelte.de/

97 100 100 100 –CWV 17AXE

Data from Aug 21, 2026, 11:24 AM UTC — 7h old.

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

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.2 Built with Eleventy 3.1.2
Netlify Hosted by Netlify

Core Web Vitals field data, origin-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

97
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.56 s — — 2.56 s 2.56 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 62 ms — — 62 ms 62 ms
FCP First Contentful Paint 1.06 s — — 1.06 s 1.06 s
Speed Index 1.06 s — — 1.06 s 1.06 s
TTFB Time to First Byte 608 ms — — 608 ms 608 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 35 ms
resource load duration 23 ms
resource load delay 11 ms
time to first byte 10 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 212.0 kB — — 212.0 kB 212.0 kB
Requests 20 — — 20 20
Third-party Weight 75.3 kB — — 75.3 kB 75.3 kB
Third-party CPU 51 ms — — 51 ms 51 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 31.9 kB — — 31.9 kB 31.9 kB

By resource type

script 89.0 kB · 5 req
font 51.1 kB · 3 req
image 42.0 kB · 2 req
stylesheet 14.6 kB · 2 req
document 10.2 kB · 1 req
other 3.7 kB · 5 req
third party 75.3 kB · 7 req

Third parties 3 entities

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

Netlify 55.2 kB · 27 ms CPU
JSDelivr CDN 15.2 kB · 21 ms CPU
Plausible 4.9 kB · 2 ms CPU

Page health

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

Main thread work

other 316 ms
script evaluation 292 ms
style layout 151 ms
paint composite render 140 ms
script parse compile 35 ms
parse HTML 27 ms

Axe violations axe-core 4.13.0, full rule set

17 violating nodes across 4 rules, 587 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 14 nodes
  • minor aria-allowed-role — ARIA role should be appropriate for the element 1 node
  • moderate landmark-no-duplicate-contentinfo — Document should not have more than one contentinfo landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 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 21, 2026, 11:24 AM UTC 97 2.56 s 0 62 ms 212.0 kB 3/3 ±5 2,325 28.4s

Embed this score

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