www.ceneo.pl speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:33 UTC. Grade B (84/100), with the screenshots, the timings and the fixes that matter.

https://www.ceneo.pl/

20 October 2026 at 14:33 UTC · Free test · report pt_0ab8aa7940a9
Grade
B
84/100
Performance80/100
Structure91/100

13 audit(s) passed, 3 need work

First byte (TTFB)879 msmeasured from this server
Fully loaded1.83 sfirst byte + slowest asset
Requests8document + assets
Page weight13.7 KBcompressed transfer
HTML document9.9 KBgzip
ProtocolHTTP/3server not sent

Where the first byte went

  • DNS lookup 248 ms 28%
  • TCP connect 194 ms 22%
  • Server wait 438 ms 50%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First byteslower than 80% of 4,999 pages tested here879 ms against a median of 448 ms
Page weightlighter than 95% of 4,999 pages tested here13.7 KB against a median of 650.5 KB
Fully loadedfaster than 51% of 4,999 pages tested here1.83 s against a median of 1.84 s
Requestssends fewer requests than 90% of 4,999 pages tested here8 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte took 879 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 13.7 KB over 8 request(s), which is lean.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The main thread was blocked for 219 ms, so taps and scrolling wait while scripts run.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paintnot reportedgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time219 mslong tasks during load
First contentful paintnot reportedfirst content on screen
Browser page weight293.6 KB6 request(s), scripts included
Largest contentful paintnot reported
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time219 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 1 request
2.1 KB 16%
Javascript 1 request
1.6 KB 12%

Transfer size, compressed as sent. 8 request(s) in total, 13.7 KB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 879 ms. Of that, 438 ms was the server thinking and 442 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Cache static assets

medium impact

2 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Waterfall

Slowest requests

HTMLwww.ceneo.pl/c(b,a&&a.id,!0
952 ms
HTMLwww.ceneo.pl/d
894 ms
HTMLwww.ceneo.pl/m
802 ms
JAVASCRIPTwww.ceneo.pl/Scripts/dist/Desktop/config.js
774 ms
IMAGESwww.ceneo.pl/Content/img/icons/logo-ceneo-simple-or…
743 ms
HTMLwww.ceneo.pl/d,b,c
728 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.ceneo.pl/c(b,a&&a.id,!0html404952 ms0 B
https://www.ceneo.pl/dhtml404894 ms0 B
https://www.ceneo.pl/mhtml404802 ms0 B
https://www.ceneo.pl/Scripts/dist/Desktop/config.js?486+3SPzNjpo/H2WH85Fmw==javascript200774 ms1.6 KB
https://www.ceneo.pl/Content/img/icons/logo-ceneo-simple-orange.svgimages200743 ms2.1 KB
https://www.ceneo.pl/d,b,chtml404728 ms0 B
https://www.ceneo.pl/+ t +other00 ms0 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.