smadex.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:53 UTC. Grade C (71/100), with the screenshots, the timings and the fixes that matter.

https://smadex.com/

20 October 2026 at 12:53 UTC · Free test · report pt_40da47055a90

Re-test this page Test your own site

Grade

71/100

Performance78/100

Structure61/100

9 audit(s) passed, 7 need work

First byte (TTFB)754 msmeasured from this server

Fully loaded1.68 sfirst byte + slowest asset

Requests26document + assets

Page weight1.65 MBcompressed transfer

HTML document335.9 KBno compression

ProtocolHTTP/3AmazonS3

Third-party967.4 KBother hosts

Where the first byte went

DNS lookup 46 ms 6%
TCP connect 11 ms 1%
Server wait 696 ms 92%

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 73% of 4,999 pages tested here754 ms against a median of 448 ms

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

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

Requestssends more requests than 100% of 4,999 pages tested here26 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 754 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 1.65 MB over 26 request(s). Fonts files are 57% of it, so subset the fonts and stop preloading the weights you do not render.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
57% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 2.42 s, inside the 2.5 s Google calls good.
Layout shift is 0.880 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 22 ms in total, which is not enough to feel.

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.

Screenshot

What the page looks like

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

Mobile screenshot of smadex.com — **Mobile** 390 × 844 · 116.2 KB · page is 3093 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 paint2.42 sgood is under 2.5 s

Cumulative layout shift0.880under 0.1 is stable

Total blocking time22 mslong tasks during load

First contentful paint1.54 sfirst content on screen

Browser page weight1.18 MB47 request(s), scripts included

Failed requests1blocked or unreachable

Largest contentful paint2.42 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.880

Poorgood under 0.1, poor over 0.25

Total blocking time22 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Fonts 22 requests

967.4 KB 57%

Images 1 request

264.1 KB 16%

Javascript 1 request

85.5 KB 5%

Css 1 request

41.6 KB 2%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 754 ms. Of that, 696 ms was the server thinking and 57 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.

Compress text responses

high impact

0 text response(s) of 10 KB or more are sent uncompressed, and the document itself is compressed. That is 0 B of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Image delivery and format

high impact

1 image(s) over 200 KB and 0 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.65 MB across 26 request(s), with the document itself at 335.9 KB.

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

Third-party weight

medium impact

1 third-party host(s) serve 967.4 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.