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 ·

complite.jcubic.pl

https://complite.jcubic.pl/

86 96 100 100 –CWV 1AXE

Data from Aug 20, 2026, 7:35 PM UTC — 23h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 23h

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.

Self-hosted · nginx Hosted by Self-hosted

Scores

86
Performance
no change
96
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.29 s — — 3.29 s 3.29 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 3.29 s — — 3.29 s 3.29 s
Speed Index 3.29 s — — 3.29 s 3.29 s
TTFB Time to First Byte 720 ms — — 720 ms 720 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 1.24 s
time to first byte 117 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 123.9 kB — — 123.9 kB 123.9 kB
Requests 8 — — 8 8
Third-party Weight 81.0 kB — — 81.0 kB 81.0 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 79.8 kB · 2 req
other 17.4 kB · 2 req
stylesheet 6.7 kB · 2 req
document 4.8 kB · 1 req
third party 81.0 kB · 3 req

Third parties 1 entities

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

Google Fonts 81.0 kB · 0 ms CPU

Page health

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

Main thread work

style layout 123 ms
other 91 ms
script evaluation 14 ms
parse HTML 11 ms
paint composite render 7 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 321 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 aria-prohibited-attr — Elements must only use permitted ARIA attributes 1 node

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

  • aria-prohibited-attr — Elements use prohibited ARIA 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 20, 2026, 7:35 PM UTC 86 3.29 s 0 0 ms 123.9 kB 3/3 ±27 2,346 26.3s

Embed this score

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