Performance
· 15 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.Performance-focused optimization plan with CWV assessment, top offenders, and time estimates
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.49 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.72 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
534 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.093
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.33 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
3.09 s
Page Load Progression
FPage Weight BudgetAction2.7 MB transferred, 78 requestsFIX
Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.
CSS bundle is large — purge unused styles (PurgeCSS, Tailwind JIT) to reduce CSS payload.
Source: web.dev
Subset fonts to include only used characters, or switch to system font stacks.
Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).
Source: web.dev font loading
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
DPage Weight InventoryAction78 resources · 2.7 MB · 292 KB savings availableFIX
~291.7 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 78 resources | 2.7 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization16 images, 0 KB saveableREVIEW
CJS Execution CostAction1535ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.vmware.com/js/reactvendor.bundle.js?hash=ac801d0e85057d01cd98 | 770ms | 9ms | 6ms | 3rd |
| https://www.vmware.com/ | 164ms | 3ms | 1ms | 3rd |
| https://www.vmware.com/js/vendor.bundle.js?hash=b5fbdb84d775db0f7be9 | 163ms | 125ms | 6ms | 3rd |
| Unattributable | 142ms | 6ms | 0ms | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-KFH48ZHP | 124ms | 98ms | 13ms | 3rd |
| https://cdn.cookielaw.org/scripttemplates/202603.1.0/otBannerSdk.js | 108ms | 54ms | 15ms | 3rd |
| https://www.vmware.com/js/main.bundle.js?hash=523e5e8748839f1d7a3f | 65ms | 57ms | 8ms | 3rd |
CJS BundlesAction18 scripts, 292 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtm.js?id=GTM-KFH48ZHP | 173 KB | 77 KB (45%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-53L4WGZN>m=4e64h1 | 120 KB | 69 KB (58%) | ✓ | 3rd |
| https://cdn.cookielaw.org/scripttemplates/202603.1.0/otBannerSdk.js | 130 KB | 69 KB (53%) | ✓ | 3rd |
| https://www.vmware.com/js/main.bundle.js?hash=523e5e8748839f1d7a3f | 57 KB | 31 KB (55%) | ✓ | 3rd |
| https://www.vmware.com/js/reactvendor.bundle.js?hash=ac801d0e85057d01cd98 | 71 KB | 23 KB (33%) | ✓ | 3rd |
| https://www.vmware.com/js/vendor.bundle.js?hash=b5fbdb84d775db0f7be9 | 41 KB | 21 KB (51%) | ✓ | 3rd |
| https://www.vmware.com/js/7237.bundle.js?hash=fcf8f68647a38f29a863 | 3 KB | — | ✓ | 3rd |
| https://www.vmware.com/js/1177.bundle.js?hash=e208da21b14235fb9e6c | 0 KB | — | ✓ | 3rd |
| https://cdn.cookielaw.org/scripttemplates/otSDKStub.js | 9 KB | — | ✓ | 3rd |
| https://www.vmware.com/js/1013.bundle.js?hash=6c6bf8f33851b0ff6a1b | 5 KB | — | ✓ | 3rd |
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+Font Loading12 fonts (718 KB)PASS
Web fonts
12
718 KB total
Render-blocking
0
of 12
Dominant font-display
swap
Most common across fonts
Font loading timeline
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
Optimization checklist
- Preload critical fonts (priority=high)
- Use woff2 format for all fonts
- Set font-display to swap, optional, or fallback
- Subset large fonts (≤100 KB each)
Fixing the unchecked items could save ~306 KB and ~612 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
Network Waterfall78 requests over 2197msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.vmware.com www.vmware.com | Other | 770ms | 71 KB | 33% | $10/mo | Costly |
www.vmware.com www.vmware.com | Other | 164ms | 3 KB | — | $2/mo | Optional |
www.vmware.com www.vmware.com | Other | 163ms | 41 KB | 51% | $2/mo | Optional |
Unattributable Unattributable | Other | 142ms | 0 KB | — | $2/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 124ms | 173 KB | 45% | $2/mo | Optional |
OneTrust cdn.cookielaw.org | Consent | 108ms | 130 KB | 53% | $1/mo | Essential |
www.vmware.com www.vmware.com | Other | 65ms | 57 KB | 55% | $1/mo | Optional |
These scripts may cost more than they're worth
- www.vmware.com adds 770ms and costs ~$10/month
100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
When third-party JS execution time exceeds your own, performance gains from frontend work are capped by code you don't own.
Learn more ▾ ▴
Every millisecond of third-party JS competes with your own for main-thread time. If their share is bigger than yours, optimization on your code base barely moves the needle. Audit, defer, or remove third-parties before further frontend optimization. Use Lighthouse's third-party audit to identify the worst offenders.
Source: web.dev
www.vmware.com takes 770ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
51% of www.vmware.com's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
53% of OneTrust's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
55% of www.vmware.com's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev