www.vibeshort.live speed test — 20 Oct 2026

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

https://www.vibeshort.live/

20 October 2026 at 15:10 UTC · Free test · report pt_26a5e6d1f74c

Re-test this page Test your own site

Grade

78/100

Performance87/100

Structure64/100

9 audit(s) passed, 7 need work

First byte (TTFB)394 msmeasured from this server

Fully loaded1.67 sfirst byte + slowest asset

Requests26document + assets

Page weight1.74 MBcompressed transfer

HTML document105.0 KBgzip

ProtocolHTTP/3cloudflare

Third-party802.6 KBother hosts

Where the first byte went

DNS lookup 100 ms 25%
TCP connect 58 ms 15%
Server wait 236 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 57% of 4,999 pages tested here394 ms against a median of 449 ms

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

Fully loadedfaster than 60% of 4,999 pages tested here1.67 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 394 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 1.74 MB over 26 request(s). Images files are 94% 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.
45% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Images 25 requests

1.64 MB 94%

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

Top issues

Image delivery and format

high impact

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

Render-blocking resources

high impact

4 render-blocking resource(s) in the document head (1 script(s), 3 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.

Total page weight

high impact

The page transfers 1.74 MB across 26 request(s), with the document itself at 105.0 KB.

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

Cache static assets

medium impact

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

Third-party weight

medium impact

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