download.yoosee.com speed test — 20 Oct 2026

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

https://download.yoosee.com/

20 October 2026 at 14:14 UTC · Free test · report pt_8474bba78e58
Grade
C
72/100
Performance69/100
Structure76/100

11 audit(s) passed, 5 need work

First byte (TTFB)1.20 smeasured from this server
Fully loaded2.54 sfirst byte + slowest asset
Requests6document + assets
Page weight352.7 KBcompressed transfer
HTML document437 Bgzip
ProtocolHTTP/3nginx

Where the first byte went

  • DNS lookup 197 ms 16%
  • TCP connect 237 ms 20%
  • Server wait 763 ms 64%

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 91% of 4,999 pages tested here1.20 s against a median of 448 ms
Page weightlighter than 68% of 4,999 pages tested here352.7 KB against a median of 650.5 KB
Fully loadedslower than 74% of 4,999 pages tested here2.54 s against a median of 1.84 s
Requestssends fewer requests than 92% of 4,999 pages tested here6 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 1.20 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 352.7 KB over 6 request(s), which is lean. Javascript files are 88% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • 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 took 2.94 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
  • Layout shift is 0.155 (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 105 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 download.yoosee.com
Mobile 390 × 844 · 87.5 KB · page is 4435 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.94 sgood is under 2.5 s
Cumulative layout shift0.155under 0.1 is stable
Total blocking time105 mslong tasks during load
First contentful paint2.68 sfirst content on screen
Browser page weight515.0 KB19 request(s), scripts included
Largest contentful paint2.94 s
Needs improvementgood under 2.5 s, poor over 4 s
Cumulative layout shift0.155
Needs improvementgood under 0.1, poor over 0.25
Total blocking time105 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests
311.6 KB 88%
Css 2 requests
40.2 KB 11%
Html 1 request
437 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1196 ms. Of that, 763 ms was the server thinking and 434 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.

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.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: chunk-vendors.538ef099.js (272.6 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Avoid extra redirects

medium impact

2 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

JAVASCRIPTdownload.yoosee.com/statics/js/app.32a4fc75.js
1.34 s
HTMLdownload.yoosee.com/false
1.24 s
JAVASCRIPTdownload.yoosee.com/statics/js/chunk-vendors.538ef099.js
1.19 s
CSSdownload.yoosee.com/statics/css/chunk-vendors.420a74e9.css
1.01 s
CSSdownload.yoosee.com/statics/css/app.4ddb6c9ad.css
968 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://download.yoosee.com/statics/js/app.32a4fc75.jsjavascript2001.34 s38.9 KB
https://download.yoosee.com/falsehtml2001.24 s437 B
https://download.yoosee.com/statics/js/chunk-vendors.538ef099.jsjavascript2001.19 s272.6 KB
https://download.yoosee.com/statics/css/chunk-vendors.420a74e9.csscss2001.01 s32.5 KB
https://download.yoosee.com/statics/css/app.4ddb6c9ad.csscss200968 ms7.8 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.