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 ·

tkackielodzkie.pl

https://www.tkackielodzkie.pl/

83 89 96 82 –CWV 5AXE

Data from Aug 21, 2026, 12:47 PM UTC — 6h old.

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

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

83
Performance
no change
89
Accessibility
no change
96
Best Practices
no change
82
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.87 s — — 1.87 s 1.87 s
CLS Cumulative Layout Shift 0.327 — — 0.327 0.327
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 812 ms — — 812 ms 812 ms
Speed Index 1.01 s — — 1.01 s 1.01 s
TTFB Time to First Byte 632 ms — — 632 ms 632 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.

resource load duration 47 ms
time to first byte 34 ms
element render delay 26 ms
resource load delay 9 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 433.0 kB — — 433.0 kB 433.0 kB
Requests 11 — — 11 11
Third-party Weight 55.3 kB — — 55.3 kB 55.3 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 356.3 kB · 3 req
image 67.0 kB · 3 req
stylesheet 6.3 kB · 1 req
script 1.9 kB · 1 req
document 1.5 kB · 1 req
third party 55.3 kB · 1 req

Third parties 1 entities

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

Cloudinary 55.3 kB · 0 ms CPU

Page health

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

Main thread work

other 107 ms
style layout 53 ms
script evaluation 13 ms
paint composite render 11 ms
parse HTML 5 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 2 rules, 76 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 4 nodes
  • critical image-alt — Images must have alternative text 1 node

Accessibility failures 2 of 20 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. 4 nodes
  • image-alt — Image elements do not have `[alt]` attributes 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, 12:47 PM UTC 83 1.87 s 0.327 0 ms 433.0 kB 3/3 ±18 2,349 22.1s

Embed this score

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