www.zscaler.com speed test — 20 Oct 2026

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

https://www.zscaler.com:443/

20 October 2026 at 13:22 UTC · Free test · report pt_b832b17e371d

Re-test this page Test your own site

Grade

94/100

Performance97/100

Structure89/100

14 audit(s) passed, 2 need work

First byte (TTFB)294 msmeasured from this server

Fully loaded1.30 sfirst byte + slowest asset

Requests26document + assets

Page weight345.8 KBcompressed transfer

HTML document51.5 KBbr

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 60 ms 20%
TCP connect 43 ms 15%
Server wait 192 ms 65%

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

Page weightlighter than 69% of 4,999 pages tested here345.8 KB against a median of 650.5 KB

Fully loadedfaster than 83% of 4,999 pages tested here1.30 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 294 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 345.8 KB over 26 request(s). Images files are 83% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 1.54 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.005), so nothing jumps under the reader's cursor.
The main thread was blocked for 87 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.zscaler.com — **Mobile** 390 × 844 · 74.6 KB · page is 5289 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.54 sgood is under 2.5 s

Cumulative layout shift0.005under 0.1 is stable

Total blocking time87 mslong tasks during load

First contentful paint828 msfirst content on screen

Browser page weight4.12 MB200 request(s), scripts included

Largest contentful paint1.54 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.005

Goodgood under 0.1, poor over 0.25

Total blocking time87 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 24 requests

288.3 KB 83%

Html 1 request

6.0 KB 2%

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

Top issues

Render-blocking resources

high impact

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

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.