auctollo.com speed test — 20 Oct 2026

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

https://auctollo.com/

20 October 2026 at 16:07 UTC · Free test · report pt_cf55c63fd62c

Re-test this page Test your own site

Grade

83/100

Performance86/100

Structure79/100

12 audit(s) passed, 4 need work

First byte (TTFB)400 msmeasured from this server

Fully loaded1.58 sfirst byte + slowest asset

Requests20document + assets

Page weight1.92 MBcompressed transfer

HTML document13.6 KBgzip

ProtocolHTTP/3Apache

Third-party290.6 KBother hosts

Where the first byte went

DNS lookup 122 ms 31%
TCP connect 39 ms 10%
Server wait 239 ms 60%

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 bytefaster than 56% of 4,999 pages tested here400 ms against a median of 449 ms

Page weightheavier than 80% of 4,999 pages tested here1.92 MB against a median of 650.3 KB

Fully loadedfaster than 65% of 4,999 pages tested here1.58 s against a median of 1.84 s

Requestssends fewer requests than 79% of 4,999 pages tested here20 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 arrived in 400 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 1.92 MB over 20 request(s). Fonts files are 73% of it, so subset the fonts and stop preloading the weights you do not render.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 716 ms, inside the 2.5 s Google calls good.
The main thread was blocked for 12 ms in total, which is not enough to feel.

Fix first: Image delivery and format - Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of auctollo.com — **Mobile** 390 × 844 · 42.8 KB · page is 2719 px tall

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 paint716 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time12 mslong tasks during load

First contentful paint716 msfirst content on screen

Browser page weight903.1 KB19 request(s), scripts included

Largest contentful paint716 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time12 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Fonts 11 requests

1.40 MB 73%

Images 2 requests

280.3 KB 14%

Javascript 5 requests

239.5 KB 12%

Html 1 request

92 B 0%

Transfer size, compressed as sent. 20 request(s) in total, 1.92 MB across all of them.

Top issues

Image delivery and format

high impact

1 image(s) over 200 KB and 1 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Total page weight

high impact

The page transfers 1.92 MB across 20 request(s), with the document itself at 13.6 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Third-party weight

medium impact

4 third-party host(s) serve 290.6 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.