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 ·

przemekmiros.pl

https://przemekmiros.pl/

95 97 77 100 –CWV 10AXE

Data from Aug 21, 2026, 4:44 AM UTC — 14h old.

11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 14h

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.

Astro 5.16.12 Built with Astro 5.16.12
Netlify Hosted by Netlify

Scores

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.14 s — — 2.14 s 2.14 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 231 ms — — 231 ms 231 ms
FCP First Contentful Paint 1.02 s — — 1.02 s 1.02 s
Speed Index 1.02 s — — 1.02 s 1.02 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 121 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.04 MB — — 1.04 MB 1.04 MB
Requests 46 — — 46 46
Third-party Weight 159.7 kB — — 159.7 kB 159.7 kB
Third-party CPU 85 ms — — 85 ms 85 ms
Unused JS 61.3 kB — — 61.3 kB 61.3 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

other 375.4 kB · 4 req
image 343.6 kB · 33 req
script 166.3 kB · 4 req
font 130.3 kB · 2 req
document 14.6 kB · 1 req
stylesheet 10.3 kB · 1 req
third party 159.7 kB · 5 req

Third parties 3 entities

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

Google Tag Manager 156.9 kB · 84 ms CPU
Google/Doubleclick Ads 2.7 kB · 1 ms CPU
Other Google APIs/SDKs 105 B · 0 ms CPU

Page health

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

Main thread work

other 356 ms
script evaluation 329 ms
style layout 172 ms
script parse compile 76 ms
paint composite render 37 ms
parse HTML 24 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 1 rule, 913 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 10 nodes

Accessibility failures 2 of 28 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. 8 nodes
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 3 nodes

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, 4:44 AM UTC 95 2.14 s 0 231 ms 1.04 MB 3/3 ±30 2,502 34.2s

Embed this score

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