www.vmware.com speed test — 20 Oct 2026

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

https://www.vmware.com/

20 October 2026 at 12:56 UTC · Free test · report pt_9141b8c2b2ad
Grade
A
97/100
Performance99/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)240 msmeasured from this server
Fully loaded879 msfirst byte + slowest asset
Requests15document + assets
Page weight484.2 KBcompressed transfer
HTML document1.7 KBbr
ProtocolHTTP/3cloudflare
Third-party13.7 KBother hosts

Where the first byte went

  • DNS lookup 49 ms 20%
  • TCP connect 31 ms 13%
  • Server wait 160 ms 67%

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 86% of 4,999 pages tested here240 ms against a median of 449 ms
Page weightlighter than 59% of 4,999 pages tested here484.2 KB against a median of 650.5 KB
Fully loadedfaster than 94% of 4,999 pages tested here879 ms against a median of 1.84 s
Requestssends fewer requests than 83% of 4,999 pages tested here15 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 240 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 484.2 KB over 15 request(s), which is lean. Javascript files are 44% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • 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 964 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.063), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 90 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.

Desktop screenshot of www.vmware.com
Desktop 1366 × 768 · 234.8 KB · page is 3842 px tall
Mobile screenshot of www.vmware.com
Mobile 390 × 844 · 83.0 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 paint964 msgood is under 2.5 s
Cumulative layout shift0.063under 0.1 is stable
Total blocking time90 mslong tasks during load
First contentful paint536 msfirst content on screen
Browser page weight4.18 MB103 request(s), scripts included
Failed requests3blocked or unreachable
Largest contentful paint964 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.063
Goodgood under 0.1, poor over 0.25
Total blocking time90 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 4 requests
215.4 KB 44%
Css 3 requests
211.9 KB 44%
Fonts 3 requests
49.5 KB 10%
Images 3 requests
5.6 KB 1%
Html 1 request
92 B 0%

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

Top issues

Render-blocking resources

high impact

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

Waterfall

Slowest requests

JAVASCRIPTcdn.cookielaw.org/scripttemplates/otSDKStub.js
639 ms
HTMLwww.googletagmanager.com/ns.html
627 ms
JAVASCRIPTwww.vmware.com/js/vendor.bundle.js
616 ms
FONTSwww.vmware.com/css/fonts/metro/woff2/Metropolis-Light…
607 ms
CSSwww.vmware.com/css/fonts/metro_fonts.css
602 ms
CSSwww.vmware.com/css/fonts/fonts_com_fonts.css
600 ms
FONTSwww.vmware.com/css/fonts/Fonts/a3dac99c-9132-4c77-bc1…
599 ms
CSSwww.vmware.com/css/main.styles.css
597 ms
JAVASCRIPTwww.vmware.com/js/reactvendor.bundle.js
597 ms
JAVASCRIPTwww.vmware.com/js/main.bundle.js
597 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://cdn.cookielaw.org/scripttemplates/otSDKStub.js 3rd partyjavascript200639 ms13.6 KB
https://www.googletagmanager.com/ns.html?id=GTM-KF7XWD 3rd partyhtml200627 ms92 B
https://www.vmware.com/js/vendor.bundle.js?hash=336c31031a326b94f92fjavascript200616 ms49.6 KB
https://www.vmware.com/css/fonts/metro/woff2/Metropolis-Light.woff2fonts200607 ms16.4 KB
https://www.vmware.com/css/fonts/metro_fonts.csscss200602 ms534 B
https://www.vmware.com/css/fonts/fonts_com_fonts.csscss200600 ms1.2 KB
https://www.vmware.com/css/fonts/Fonts/a3dac99c-9132-4c77-bc18-2df40293d361.woff2fonts200599 ms16.2 KB
https://www.vmware.com/css/main.styles.css?hash=0c5bc8b577bb6a216101css200597 ms210.2 KB
https://www.vmware.com/js/reactvendor.bundle.js?hash=bc3ad35033c659063e46javascript200597 ms84.5 KB
https://www.vmware.com/js/main.bundle.js?hash=53895d79b590b140c087javascript200597 ms67.7 KB
https://www.vmware.com/css/fonts/metro/woff2/Metropolis-SemiBold.woff2fonts200597 ms16.9 KB
https://www.vmware.com/vm-favicon-96x96.pngimages200597 ms3.2 KB
https://www.vmware.com/vm-favicon-48x48.pngimages200597 ms1.4 KB
https://www.vmware.com/vm-favicon.pngimages200597 ms1009 B
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.