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
Image Optimization
Action
50 images, 0 KB saveable
REVIEW
50 images, 0 KB saveable
Warning::
!
https://static.themoscowtimes.com/image/320/88/7pE... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://static.themoscowtimes.com/image/original/c... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://www.themoscowtimes.com/image/320/ed/euract... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://static.themoscowtimes.com/image/320/b9/9XF... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://static.themoscowtimes.com/img/contribute/p... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://static.themoscowtimes.com/img/logo_tmt_30_... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
50images5.0 MB
0oversized-0 KB
47legacy format
6missing 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
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
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
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
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
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
5 fonts (412 KB)
PASS
5 fonts (412 KB)
Info::
i
5 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
5
412 KB total
Render-blocking
0
of 5
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
u-4e0qyriQwlOrhSvowK_l5...woff2swap
Size95 KB
Load time43 ms
Start323 ms
RiskFOUT — text flashes from fallback to web font
KFO7CnqEu92Fr1ME7kSn66a...woff2swap
Size37 KB
Load time58 ms
Start323 ms
RiskFOUT — text flashes from fallback to web font
fa-solid-900.woff2woff2swap
Size147 KB
Load time50 ms
Start324 ms
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 time54 ms
Start326 ms
RiskFOUT — text flashes from fallback to web font
fa-brands-400.woff2woff2swap
Size108 KB
Load time21 ms
Start456 ms
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 ~128 KB and ~256 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
1 hints, 0 missing preconnects
PASS
1 hints, 0 missing preconnects
Info::
✓
Page uses 1 resource hint(s)
Current Resource Hints
preconnect—
preload—
dns-prefetch
1
prefetch—
1 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
76 requests over 1391ms
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-party3641ms · 647KB · €40/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
www.themoscowtimes.com
www.themoscowtimes.com
Other
1018ms
18 KB
—
€11/mo
Costly
Unattributable
Unattributable
Other
640ms
0 KB
—
€7/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
427ms
160 KB
40%
€5/mo
Costly
static.themoscowtimes.com
static.themoscowtimes.com
Other
408ms
8 KB
—
€4/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
379ms
128 KB
49%
€4/mo
Costly
Facebook Pixel
connect.facebook.net
Advertising
276ms
48 KB
—
€3/mo
Costly
Facebook Pixel
connect.facebook.net
Advertising
219ms
97 KB
28%
€2/mo
Costly
code.jquery.com
code.jquery.com
Other
157ms
30 KB
—
€2/mo
Optional
Google Tag Manager
www.googletagmanager.com
Tag Manager
116ms
160 KB
68%
€1/mo
Optional
www.themoscowtimes.com
Other
Costly
Execution1018ms
Transfer18 KB
Monthly Cost€11/mo
Unattributable
Other
Costly
Execution640ms
Transfer0 KB
Monthly Cost€7/mo
Google Tag Manager
Tag Manager
Costly
Execution427ms
Transfer160 KB
Unused40%
Monthly Cost€5/mo
static.themoscowtimes.com
Other
Costly
Execution408ms
Transfer8 KB
Monthly Cost€4/mo
Google Tag Manager
Tag Manager
Costly
Execution379ms
Transfer128 KB
Unused49%
Monthly Cost€4/mo
Facebook Pixel
Advertising
Costly
Execution276ms
Transfer48 KB
Monthly Cost€3/mo
Facebook Pixel
Advertising
Costly
Execution219ms
Transfer97 KB
Unused28%
Monthly Cost€2/mo
code.jquery.com
Other
Optional
Execution157ms
Transfer30 KB
Monthly Cost€2/mo
Google Tag Manager
Tag Manager
Optional
Execution116ms
Transfer160 KB
Unused68%
Monthly Cost€1/mo
These scripts may cost more than they're worth
www.themoscowtimes.com adds 1018ms and costs ~€11/month
Unattributable adds 640ms and costs ~€7/month
Google Tag Manager adds 427ms and costs ~€5/month
static.themoscowtimes.com adds 408ms and costs ~€4/month
Google Tag Manager adds 379ms and costs ~€4/month
Facebook Pixel adds 276ms and costs ~€3/month
Facebook Pixel adds 219ms 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.themoscowtimes.com takes 1018ms 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 640ms 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 427ms 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
static.themoscowtimes.com takes 408ms 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 379ms 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 276ms 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 219ms 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
68% 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.