www.mundodeportivo.com speed test — 20 Oct 2026

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

https://www.mundodeportivo.com/

20 October 2026 at 12:42 UTC · Free test · report pt_eeb5a654c499

Re-test this page Test your own site

Grade

94/100

Performance96/100

Structure92/100

13 audit(s) passed, 3 need work

First byte (TTFB)360 msmeasured from this server

Fully loaded1.31 sfirst byte + slowest asset

Requests26document + assets

Page weight200.6 KBcompressed transfer

HTML document77.6 KBgzip

ProtocolHTTP/3nginx

Third-party123.0 KBother hosts

Where the first byte went

DNS lookup 44 ms 12%
TCP connect 14 ms 4%
Server wait 303 ms 84%

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 63% of 4,999 pages tested here360 ms against a median of 449 ms

Page weightlighter than 79% of 4,999 pages tested here200.6 KB against a median of 650.5 KB

Fully loadedfaster than 82% of 4,999 pages tested here1.31 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 arrived in 360 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 200.6 KB over 26 request(s). Images files are 61% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
61% 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 1.08 s, inside the 2.5 s Google calls good.
The main thread was blocked for 349 ms, so taps and scrolling wait while scripts run.

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

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 www.mundodeportivo.com — **Mobile** 390 × 844 · 109.9 KB · page is 6000 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 paint1.08 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time349 mslong tasks during load

First contentful paint968 msfirst content on screen

Browser page weight3.08 MB149 request(s), scripts included

Largest contentful paint1.08 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time349 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

123.0 KB 61%

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

Top issues

Cache static assets

medium impact

1 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.

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.

Waterfall

Slowest requests

IMAGESstatic2.mundodeportivo.com/images/int-icon.png

949 ms

IMAGESimagenes2.mundodeportivo.com/files/image_36_36/uploads/2024/07/15/6…

935 ms