Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
C
Page Weight Budget
Action
2.0 MB transferred, 91 requests
REVIEW
2.0 MB transferred, 91 requests
Info::
i
Page weighs 4.8 MB (2.0 MB transferred)
Warning::
!
JavaScript is 937 KB — consider code splitting or lazy loading
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Got: 937 KB
Info::
i
Fonts are 312 KB — consider subsetting or using system fonts
Subset fonts to include only used characters, or switch to system font stacks.
Got: 312 KB
Info::
i
91 HTTP requests
Info::
i
Estimated 0.42 g CO2 per page load
2.0 MBtransferred
91 requests
0.42 g CO2 per page load
JavaScript937.2 KiB46%
Images621.7 KiB31%
Fonts311.8 KiB15%
CSS107.0 KiB5%
HTML39.3 KiB2%
Other11.1 KiB1%
Other1.4 KiB0%
Other847 B0%
Other547 B0%
Other0 B0%
02.4 MB4.9 MB
Approaching limit
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Why this matters
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
Subset fonts to include only used characters, or switch to system font stacks.
Why this matters
Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).
Source: web.dev font loading
B
Image Optimization
18 images, 0 KB saveable
REVIEW
18 images, 0 KB saveable
Warning::
!
https://www.pair.com/wp-content/uploads/2025/12/Ar... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
18images622 KB
0oversized-0 KB
12legacy format
1missing dimensionsCLS risk
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
A+
Text Compression
All text resources are compressed
PASS
All text resources are compressed
Info::
✓
All text resources are compressed
All text resources are properly compressed.
A+
Font Loading
7 fonts (312 KB)
PASS
7 fonts (312 KB)
Info::
i
7 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
7
312 KB total
Render-blocking
0
of 7
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
inter-normal-latin-500....woff2swap
Size24 KB
Load time26 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
modules.woffwoffswap
Size37 KB
Load time39 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
Convert to woff2 for ~30% smaller file size
inter-normal-latin-600....woff2swap
Size24 KB
Load time37 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
inter-normal-latin-700....woff2swap
Size24 KB
Load time27 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
inter-normal-latin-400....woff2swap
Size23 KB
Load time28 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
fa-regular-400.woff2woff2swap
Size25 KB
Load time41 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
fa-solid-900.woff2woff2swap
Size154 KB
Load time93 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
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 ~88 KB and ~176 ms
A+
Resource Caching
All resources properly cached
PASS
All resources properly cached
Info::
✓
No caching issues found
All static resources have appropriate caching headers.
A+
Critical Rendering Path
No render-blocking resources
PASS
No render-blocking resources
Info::
✓
No render-blocking resources detected
A+
Resource Hints
2 hints, 0 missing preconnects
PASS
2 hints, 0 missing preconnects
Info::
✓
Page uses 2 resource hint(s)
Current Resource Hints
preconnect—
preload
1
dns-prefetch
1
prefetch—
2 resource hints configured
A+
Render-Blocking Resources
No render-blocking resources detected
PASS
No render-blocking resources detected
Info::
✓
No render-blocking resources detected in <head>
A+
Third-Party Resources
No third-party resources detected
PASS
No third-party resources detected
A+
Green Hosting
Whether the site is served from green-energy infrastructure
PASS
Green Hosting
This site is hosted on green energy infrastructure
Provider: Cloudflare
Network Waterfall
91 requests over 2233ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
100%of JavaScript execution is third-party
First-party Third-party3424ms · 915KB · $20/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
www.pair.com
www.pair.com
Other
647ms
39 KB
—
$4/mo
Costly
Unattributable
Unattributable
Other
463ms
0 KB
—
$3/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
389ms
153 KB
42%
$2/mo
Costly
www.pair.com
www.pair.com
Other
386ms
30 KB
—
$2/mo
Costly
script.crazyegg.com
script.crazyegg.com
Other
366ms
55 KB
47%
$2/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
299ms
177 KB
38%
$2/mo
Costly
Facebook Pixel
connect.facebook.net
Advertising
260ms
125 KB
28%
$1/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
186ms
137 KB
44%
$1/mo
Optional
www.pair.com
www.pair.com
Other
157ms
69 KB
62%
$1/mo
Optional
Facebook Pixel
connect.facebook.net
Advertising
117ms
97 KB
33%
$1/mo
Optional
www.pair.com
www.pair.com
Other
97ms
11 KB
—
$1/mo
Optional
script.crazyegg.com
script.crazyegg.com
Other
57ms
23 KB
—
$0/mo
Optional
www.pair.com
Other
Costly
Execution647ms
Transfer39 KB
Monthly Cost$4/mo
Unattributable
Other
Costly
Execution463ms
Transfer0 KB
Monthly Cost$3/mo
Google Tag Manager
Tag Manager
Costly
Execution389ms
Transfer153 KB
Unused42%
Monthly Cost$2/mo
www.pair.com
Other
Costly
Execution386ms
Transfer30 KB
Monthly Cost$2/mo
script.crazyegg.com
Other
Costly
Execution366ms
Transfer55 KB
Unused47%
Monthly Cost$2/mo
Google Tag Manager
Tag Manager
Costly
Execution299ms
Transfer177 KB
Unused38%
Monthly Cost$2/mo
Facebook Pixel
Advertising
Costly
Execution260ms
Transfer125 KB
Unused28%
Monthly Cost$1/mo
Google Tag Manager
Tag Manager
Optional
Execution186ms
Transfer137 KB
Unused44%
Monthly Cost$1/mo
www.pair.com
Other
Optional
Execution157ms
Transfer69 KB
Unused62%
Monthly Cost$1/mo
Facebook Pixel
Advertising
Optional
Execution117ms
Transfer97 KB
Unused33%
Monthly Cost$1/mo
www.pair.com
Other
Optional
Execution97ms
Transfer11 KB
Monthly Cost$1/mo
script.crazyegg.com
Other
Optional
Execution57ms
Transfer23 KB
Monthly Cost$0/mo
These scripts may cost more than they're worth
www.pair.com adds 647ms and costs ~$4/month
Unattributable adds 463ms and costs ~$3/month
Google Tag Manager adds 389ms and costs ~$2/month
www.pair.com adds 386ms and costs ~$2/month
script.crazyegg.com adds 366ms and costs ~$2/month
Google Tag Manager adds 299ms and costs ~$2/month
Facebook Pixel adds 260ms and costs ~$1/month
100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
Why this matters
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.pair.com takes 647ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Unattributable takes 463ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Google Tag Manager takes 389ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
www.pair.com takes 386ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
script.crazyegg.com takes 366ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Google Tag Manager takes 299ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Facebook Pixel takes 260ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
62% of www.pair.com's code is unused. The script may be loading features you don't use.
Why this matters
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.