www.veeam.com speed test — 20 Oct 2026

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

https://www.veeam.com/

20 October 2026 at 13:53 UTC · Free test · report pt_d4aeda0c9e76

Re-test this page Test your own site

Grade

86/100

Performance92/100

Structure76/100

10 audit(s) passed, 6 need work

First byte (TTFB)454 msmeasured from this server

Fully loaded1.85 sfirst byte + slowest asset

Requests26document + assets

Page weight462.8 KBcompressed transfer

HTML document34.7 KBgzip

ProtocolHTTP/3nginx

Third-party428.1 KBother hosts

Where the first byte went

DNS lookup 94 ms 21%
TCP connect 82 ms 18%
Server wait 278 ms 61%

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 51% of 4,999 pages tested here454 ms against a median of 448 ms

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

Fully loadedfaster than 50% of 4,999 pages tested here1.85 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 454 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 462.8 KB over 26 request(s). Images files are 92% 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.
92% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 2.99 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.
The main thread was blocked for 481 ms, so taps and scrolling wait while scripts run.

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 www.veeam.com — **Mobile** 390 × 844 · 138.1 KB · page is 6000 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.99 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time481 mslong tasks during load

First contentful paint1.85 sfirst content on screen

Browser page weight4.09 MB133 request(s), scripts included

Failed requests1blocked or unreachable

Largest contentful paint2.99 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time481 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

428.1 KB 92%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 454 ms. Of that, 278 ms was the server thinking and 176 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.

Render-blocking resources

high impact

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

Image delivery and format

medium impact

0 image(s) over 200 KB and 1 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.

Cache static assets

medium impact

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