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 ·

akademia.instytutsprawobywatelskich.pl

https://akademia.instytutsprawobywatelskich.pl/

87 95 100 100 CWV 3AXE

Data from Aug 20, 2026, 4:12 PM UTC — 27h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 27h

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

Scores

87
Performance
no change
95
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 3.75 s 3.75 s 3.75 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 82 ms 82 ms 82 ms
FCP First Contentful Paint 1.95 s 1.95 s 1.95 s
Speed Index 1.95 s 1.95 s 1.95 s
TTFB Time to First Byte 604 ms 604 ms 604 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 94 ms
resource load duration 37 ms
resource load delay 11 ms
time to first byte 7 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 973.6 kB 973.6 kB 973.6 kB
Requests 26 26 26
Third-party Weight 710.3 kB 710.3 kB 710.3 kB
Third-party CPU 34 ms 34 ms 34 ms
Unused JS 0 B 0 B 0 B
Unused CSS 21.3 kB 21.3 kB 21.3 kB

By resource type

image 698.5 kB · 14 req
font 191.5 kB · 5 req
script 57.0 kB · 2 req
document 20.8 kB · 1 req
stylesheet 4.6 kB · 1 req
other 1.1 kB · 2 req
third party 710.3 kB · 11 req

Third parties 3 entities

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

Cloudinary 652.7 kB · 0 ms CPU
Netlify 55.1 kB · 32 ms CPU
Plausible 2.4 kB · 2 ms CPU

Page health

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

Main thread work

style layout 216 ms
other 201 ms
script evaluation 128 ms
script parse compile 41 ms
paint composite render 29 ms
parse HTML 19 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 590 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 2 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 of 19 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. 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 20, 2026, 4:12 PM UTC 87 3.75 s 0 82 ms 973.6 kB 3/3 ±8 2,492 24.7s

Embed this score

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