uisp.com speed test — 20 Oct 2026

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

https://uisp.com/

20 October 2026 at 13:22 UTC · Free test · report pt_d9e3e79e1ed2
Grade
A
96/100
Performance97/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)301 msmeasured from this server
Fully loaded580 msfirst byte + slowest asset
Requests4document + assets
Page weight291.1 KBcompressed transfer
HTML document424 Bgzip
ProtocolHTTP/2nginx

Where the first byte went

  • DNS lookup 103 ms 34%
  • TCP connect 55 ms 18%
  • Server wait 143 ms 48%

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 74% of 4,999 pages tested here301 ms against a median of 449 ms
Page weightlighter than 73% of 4,999 pages tested here291.1 KB against a median of 650.5 KB
Fully loadedfaster than 97% of 4,999 pages tested here580 ms against a median of 1.84 s
Requestssends fewer requests than 94% of 4,999 pages tested here4 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 301 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 291.1 KB over 4 request(s), which is lean. Javascript files are 95% 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/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.00 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 58 ms in total, which is not enough to feel.

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

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 uisp.com
Mobile 390 × 844 · 182.2 KB · page is 4972 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.00 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time58 mslong tasks during load
First contentful paint648 msfirst content on screen
Browser page weight19.65 MB60 request(s), scripts included
Failed requests5blocked or unreachable
Largest contentful paint1.00 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time58 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 1 request
276.5 KB 95%
Css 1 request
9.3 KB 3%
Images 1 request
4.8 KB 2%

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

Top issues

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: index-CTvKF-4O.js (276.5 KB)

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

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

IMAGESuisp.com/favicon.ico
279 ms
JAVASCRIPTuisp.com/assets/index-CTvKF-4O.js
255 ms
CSSuisp.com/assets/index-BsOBj2DL.css
225 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://uisp.com/favicon.icoimages200279 ms4.8 KB
https://uisp.com/assets/index-CTvKF-4O.jsjavascript200255 ms276.5 KB
https://uisp.com/assets/index-BsOBj2DL.csscss200225 ms9.3 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.