data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABHsA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABJEA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://iacesport.com/wp-content/uploads/2023/12/%... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABJIA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://iacesport.com/wp-content/uploads/2025/11/I... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://iacesport.com/wp-content/uploads/2025/11/I... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABJIA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://iacesport.com/wp-content/uploads/2025/11/I... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
17images505 KB
0oversized-0 KB
1legacy format
8missing 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
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
B
JS Execution Cost
866ms total JS execution
REVIEW
866ms total JS execution
Warning::
!
https://iacesport.com/: 785ms CPU time
Info::
i
Unattributable: 81ms CPU time
Main Thread Breakdown
Style & Layout 61% Other 20% Parse HTML & CSS 7% Script Evaluation 6% Rendering 5%
Script
Total
Scripting
Parse/Compile
Party
https://iacesport.com/
785ms
46ms
3ms
1st
Unattributable
81ms
2ms
0ms
1st
B
Document Compression
Document response uses gzip; brotli would be ~20% smaller
REVIEW
Document response uses gzip; brotli would be ~20% smaller
Info::
i
Main HTML response uses gzip (brotli would be ~20% smaller)
All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.
B
Server-Timing Observability
No Server-Timing header found
REVIEW
No Server-Timing header found
Info::
i
No Server-Timing header found
Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.
A
Page Weight Budget
796 KB transferred, 32 requests
PASS
796 KB transferred, 32 requests
Info::
✓
Page weighs 2.0 MB (796 KB transferred)
Info::
✓
32 HTTP requests
Info::
i
Estimated 0.16 g CO2 per page load
796 KBtransferred
32 requests
0.16 g CO2 per page load
Images505.0 KiB63%
HTML186.2 KiB23%
Fonts89.7 KiB11%
JavaScript9.7 KiB1%
CSS3.7 KiB0%
Other2.1 KiB0%
02.4 MB4.9 MB
Under budget
A+
Third-Party Impact
11% third-party, 0 ms blocking
PASS
11% third-party, 0 ms blocking
Info::
i
Third-party code accounts for 11% of page weight (90.1 KiB of 796.5 KiB)
Info::
✓
Third-party blocking time is low (0 ms)
89%
First-party Third-party
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
9 fonts (90 KB)
PASS
9 fonts (90 KB)
Info::
i
9 font(s) use font-display: swap (FOUT risk but functional)
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
No optimization needed
PASS
No optimization needed
Info::
✓
No resource hint issues
A+
HTTP/3 (QUIC)
HTTP/3 advertised via Alt-Svc
PASS
HTTP/3 advertised via Alt-Svc
Info::
✓
HTTP/3 (QUIC) is supported
First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss.
A+
Asset Compression
All 1 asset host use brotli
PASS
All 1 asset host use brotli
Info::
✓
www.googletagmanager.com serves assets with brotli (assets: 5)
The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
Info::
✓
Both `ETag` and `Last-Modified` present -- efficient revalidation supported
The page returns both `ETag` (content hash) and `Last-Modified` (timestamp) headers. Browsers can issue conditional GETs with `If-None-Match` or `If-Modified-Since`; the server returns 304 Not Modified for unchanged content, saving bandwidth. ETag is the more reliable of the two (timestamps fail in DST transitions and clock skew).
375 ms
750 ms
1.1 s