www.tupi.fm speed test — 20 Oct 2026

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

https://www.tupi.fm/

20 October 2026 at 12:51 UTC · Free test · report pt_c491860edd99

Re-test this page Test your own site

Grade

85/100

Performance87/100

Structure82/100

12 audit(s) passed, 4 need work

First byte (TTFB)264 msmeasured from this server

Fully loaded4.35 sfirst byte + slowest asset

Requests26document + assets

Page weight517.3 KBcompressed transfer

HTML document57.5 KBzstd

ProtocolHTTP/3cloudflare

Third-party43 Bother hosts

Where the first byte went

DNS lookup 50 ms 19%
TCP connect 42 ms 16%
Server wait 173 ms 66%

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

Page weightlighter than 57% of 4,999 pages tested here517.3 KB against a median of 650.5 KB

Fully loadedslower than 89% of 4,999 pages tested here4.35 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 264 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 517.3 KB over 26 request(s). Images files are 89% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives zstd-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 632 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.024), so nothing jumps under the reader's cursor.
The main thread was blocked for 79 ms in total, which is not enough to feel.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

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.tupi.fm — **Mobile** 390 × 844 · 253.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 paint632 msgood is under 2.5 s

Cumulative layout shift0.024under 0.1 is stable

Total blocking time79 mslong tasks during load

First contentful paint432 msfirst content on screen

Browser page weight7.97 MB1792 request(s), scripts included

Failed requests36blocked or unreachable

Largest contentful paint632 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.024

Goodgood under 0.1, poor over 0.25

Total blocking time79 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

459.7 KB 89%

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

Top issues

Render-blocking resources

high impact

13 render-blocking resource(s) in the document head (2 script(s), 11 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Image delivery and format

medium impact

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

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.

Waterfall

Slowest requests

IMAGESwww.tupi.fm/wp-content/uploads/2026/10/proverbio-j…

4.09 s

IMAGESwww.tupi.fm/wp-content/uploads/2026/10/Jade_plant_…

987 ms