zenweb.proofpoint.com/urldefense?locale=en-US speed test — 20 Oct 2026

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

https://zenweb.proofpoint.com/urldefense?locale=en-US

20 October 2026 at 13:18 UTC · Free test · report pt_3f1cbbc2f6b0
Grade
A
93/100
Performance95/100
Structure91/100

13 audit(s) passed, 3 need work

First byte (TTFB)403 msmeasured from this server
Fully loaded403 msfirst byte + slowest asset
Requests1document + assets
Page weight9.5 KBcompressed transfer
HTML document9.5 KBgzip
ProtocolHTTP/3server not sent

Where the first byte went

  • DNS lookup 78 ms 19%
  • TCP connect 96 ms 24%
  • Server wait 229 ms 57%

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 56% of 4,999 pages tested here403 ms against a median of 449 ms
Page weightlighter than 95% of 4,999 pages tested here9.5 KB against a median of 650.5 KB
Fully loadedfaster than 99% of 4,999 pages tested here403 ms against a median of 1.84 s
Requestssends fewer requests than 98% of 4,999 pages tested here1 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 403 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 9.5 KB over 1 request(s), which is lean.
  • 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 painted at 476 ms, inside the 2.5 s Google calls good.

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 zenweb.proofpoint.com
Mobile 390 × 844 · 78.1 KB · page is 957 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 paint476 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint476 msfirst content on screen
Browser page weight10.0 KB1 request(s), scripts included
Largest contentful paint476 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 403 ms. Of that, 229 ms was the server thinking and 174 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.

TLS certificate validity

high impact

The certificate for zenweb.proofpoint.com has 19 day(s) left.

Fix: Renew automatically (certbot with a working renewal timer) and alert on the certificate, not on the renew command, so a silent failure is caught weeks before a browser warning.

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.

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.