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.
B
Image Optimization
20 images, 0 KB saveable
REVIEW
20 images, 0 KB saveable
Info::
✓
All images are well-optimized
20images332 KB
0oversized-0 KB
9legacy format
0missing dimensionsCLS risk
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW
Green Hosting
No green hosting detected
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
17 fonts (1244 KB)
PASS
17 fonts (1244 KB)
Info::
i
17 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
17
1244 KB total
Render-blocking
0
of 17
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
6xK3dSBYKcSV-LCoeQqfX1R...woff2swap
Size15 KB
Load time25 ms
Start614 ms
RiskFOUT — text flashes from fallback to web font
pxiByp8kv8JHgFVrLCz7Z1x...woff2swap
Size8 KB
Load time26 ms
Start657 ms
RiskFOUT — text flashes from fallback to web font
6xKydSBYKcSV-LCoeQqfX1R...woff2swap
Size14 KB
Load time36 ms
Start658 ms
RiskFOUT — text flashes from fallback to web font
pxiDyp8kv8JHgFVrJJLmy15...woff2swap
Size8 KB
Load time30 ms
Start658 ms
RiskFOUT — text flashes from fallback to web font
pxiEyp8kv8JHgFVrJJfecnF...woff2swap
Size8 KB
Load time28 ms
Start703 ms
RiskFOUT — text flashes from fallback to web font
neIXzD-0qpwxpaWvjeD0X88...woff2swap
Size21 KB
Load time46 ms
Start704 ms
RiskFOUT — text flashes from fallback to web font
neIQzD-0qpwxpaWvjeD0X88...woff2swap
Size20 KB
Load time45 ms
Start704 ms
RiskFOUT — text flashes from fallback to web font
pxiGyp8kv8JHgFVrJJLucHt...woff2swap
Size8 KB
Load time43 ms
Start704 ms
RiskFOUT — text flashes from fallback to web font
6xK1dSBYKcSV-LCoeQqfX1R...woff2swap
Size14 KB
Load time25 ms
Start1.2 s
RiskFOUT — text flashes from fallback to web font
fa-brands-400.woff2woff2swap
Size106 KB
Load time60 ms
Start1.3 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
fa-regular-400.woff2woff2swap
Size25 KB
Load time63 ms
Start1.3 s
RiskFOUT — text flashes from fallback to web font
fa-solid-900.woff2woff2swap
Size147 KB
Load time85 ms
Start1.3 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
fa-brands-400.woff2woff2swap
Size109 KB
Load time11 ms
Start1.4 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
fa-solid-900.woff2woff2swap
Size320 KB
Load time19 ms
Start1.4 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
fa-regular-400.woff2woff2swap
Size387 KB
Load time24 ms
Start1.4 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
KFO7CnqEu92Fr1ME7kSn66a...woff2swap
Size34 KB
Load time65 ms
Start2.0 s
RiskFOUT — text flashes from fallback to web font
KFO7CnqEu92Fr1ME7kSn66a...woff2swap
Size0 KB
Load time0 ms
Start2.7 s
RiskFOUT — text flashes from fallback to web font
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 ~535 KB and ~1070 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
2
preload—
dns-prefetch—
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
Network Waterfall
94 requests over 3976ms
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-party5771ms · 1209KB · $41/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
www.cancer.org
www.cancer.org
Other
1481ms
42 KB
—
$10/mo
Costly
www.gstatic.com
www.gstatic.com
Other
858ms
0 KB
49%
$6/mo
Costly
Unattributable
Unattributable
Other
591ms
0 KB
—
$4/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
590ms
195 KB
37%
$4/mo
Costly
www.cancer.org
www.cancer.org
Other
514ms
35 KB
—
$4/mo
Costly
www.cancer.org
www.cancer.org
Other
469ms
102 KB
53%
$3/mo
Costly
assets-donate.azureedge.net
assets-donate.azureedge.net
Other
351ms
429 KB
35%
$2/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
269ms
157 KB
53%
$2/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
262ms
152 KB
47%
$2/mo
Costly
www.cancer.org
www.cancer.org
Other
182ms
20 KB
—
$1/mo
Optional
acs.cdn-v3.conductrics.com
acs.cdn-v3.conductrics.com
Other
106ms
54 KB
55%
$1/mo
Optional
www.cancer.org
www.cancer.org
Other
97ms
21 KB
—
$1/mo
Optional
www.cancer.org
Other
Costly
Execution1481ms
Transfer42 KB
Monthly Cost$10/mo
www.gstatic.com
Other
Costly
Execution858ms
Transfer0 KB
Unused49%
Monthly Cost$6/mo
Unattributable
Other
Costly
Execution591ms
Transfer0 KB
Monthly Cost$4/mo
Google Tag Manager
Tag Manager
Costly
Execution590ms
Transfer195 KB
Unused37%
Monthly Cost$4/mo
www.cancer.org
Other
Costly
Execution514ms
Transfer35 KB
Monthly Cost$4/mo
www.cancer.org
Other
Costly
Execution469ms
Transfer102 KB
Unused53%
Monthly Cost$3/mo
assets-donate.azureedge.net
Other
Costly
Execution351ms
Transfer429 KB
Unused35%
Monthly Cost$2/mo
Google Tag Manager
Tag Manager
Costly
Execution269ms
Transfer157 KB
Unused53%
Monthly Cost$2/mo
Google Tag Manager
Tag Manager
Costly
Execution262ms
Transfer152 KB
Unused47%
Monthly Cost$2/mo
www.cancer.org
Other
Optional
Execution182ms
Transfer20 KB
Monthly Cost$1/mo
acs.cdn-v3.conductrics.com
Other
Optional
Execution106ms
Transfer54 KB
Unused55%
Monthly Cost$1/mo
www.cancer.org
Other
Optional
Execution97ms
Transfer21 KB
Monthly Cost$1/mo
These scripts may cost more than they're worth
www.cancer.org adds 1481ms and costs ~$10/month
www.gstatic.com adds 858ms and costs ~$6/month
Unattributable adds 591ms and costs ~$4/month
Google Tag Manager adds 590ms and costs ~$4/month
www.cancer.org adds 514ms and costs ~$4/month
www.cancer.org adds 469ms and costs ~$3/month
assets-donate.azureedge.net adds 351ms and costs ~$2/month
Google Tag Manager adds 269ms and costs ~$2/month
Google Tag Manager adds 262ms and costs ~$2/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.cancer.org takes 1481ms 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.gstatic.com takes 858ms 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 591ms 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 590ms 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.cancer.org takes 514ms 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.cancer.org takes 469ms 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
53% of www.cancer.org'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.
Source: web.dev
assets-donate.azureedge.net takes 351ms 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 269ms 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
53% of Google Tag Manager'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.
Source: web.dev
Google Tag Manager takes 262ms 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
55% of acs.cdn-v3.conductrics.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.