Skip to content
https://intensedebate.com

Performance

· 17 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.
SCORE
95
GRADE
A
FIX
1
REVIEW
2
PASS
12
INFO
2

Performance-focused optimization plan with CWV assessment, top offenders, and time estimates

Mobile Desktop
97
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
78
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.11 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.11 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.002

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.65 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.

2.11 s

Page Load Progression

375 ms
750 ms
1.1 s
1.5 s
1.9 s
2.2 s
2.6 s
3.0 s
Checks
17
12 PASS 2 REVIEW 1 FIX
F
HTTP Caching
Action
No cache headers
FIX
No cache headers
Warning::
No Cache-Control header found
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
3 images, 0 KB saveable
REVIEW
3 images, 0 KB saveable
Warning::
https://intensedebate.com/images/svg/intensedebate... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
https://intensedebate.com/images/screenshots/inten... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
https://intensedebate.com/images/svg/automattic-lo... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
3 images 98 KB
0 oversized -0 KB
3 legacy format
3 missing dimensions CLS 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

C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW

Green Hosting

No green hosting detected

A+
Page Weight Budget
258 KB transferred, 19 requests
PASS
258 KB transferred, 19 requests
Info::
Page weighs 591 KB (258 KB transferred)
Info::
19 HTTP requests
Info::
Estimated 0.05 g CO2 per page load
258 KB / 2.4 MB budget
258 KB transferred
19 requests
0.05 g CO2 per page load
JavaScript 99.6 KiB 39%
Images 98.2 KiB 38%
Fonts 33.2 KiB 13%
CSS 21.5 KiB 8%
HTML 3.8 KiB 1%
Other 1.0 KiB 0%
Other 520 B 0%
0 2.4 MB 4.9 MB
Under budget
A
Third-Party Impact
23% third-party, 0 ms blocking
PASS
23% third-party, 0 ms blocking
Info::
Third-party code accounts for 23% of page weight (59.4 KiB of 258.0 KiB)
Info::
Third-party blocking time is low (0 ms)
77%
23%
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+
JS Execution Cost
297ms total JS execution
PASS
297ms total JS execution
Info::
Unattributable: 151ms CPU time
Info::
https://intensedebate.com/: 145ms CPU time
Warning::
Third-party scripts: 151ms (51% of total)

Main Thread Breakdown

Other 38% Script Evaluation 25% Style & Layout 23% Script Parsing & Compilation 7% Rendering 4% Parse HTML & CSS 3%
ScriptTotalScriptingParse/CompileParty
Unattributable151ms5ms0ms3rd
https://intensedebate.com/145ms4ms2ms1st
A+
Font Loading
1 fonts (33 KB)
PASS
1 fonts (33 KB)
Info::
1 font(s) use font-display: swap (FOUT risk but functional)

Web fonts

1

33 KB total

Render-blocking

0

of 1

Dominant font-display

swap

Most common across fonts

Font loading timeline
Transfer FOIT (block) FOUT (swap)
0 ms 500 ms 1.0 s 1.5 s 2.0 s FCP 2.1 s LCP 2.1 shttps://s1.wp.com/i/fonts/recoleta/400.woff2400.woff2 https://s1.wp.com/i/fonts/recoleta/400.woff2 — 33.2 KiB — 7 ms — font-display: swap
400.woff2 woff2 swap
Size 33 KB
Load time 7 ms
Start 949 ms
Risk FOUT — 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)
A
JS Bundles
9 scripts, 48 KB unused
PASS
9 scripts, 48 KB unused
Warning::
https://intensedebate.com/js/idm-combined.js?v=2: 48 KB unused (86%)
Consider code splitting or tree shaking to reduce unused code.
Warning::
https://intensedebate.com/js/idm-combined.js?v=2: unminified — 18 KB could be saved
Info::
Total unused JavaScript: 48 KB
48 KB unused JavaScript

Downloaded but never executed on this page.

ScriptSizeUnusedMinifiedParty
https://intensedebate.com/js/idm-combined.js?v=255 KB48 KB (86%)✗1st
https://wordpress.com/remote-login.php?action=js&id=5116184&host=intensedebate.com&back=https%3A%2F%2Fwww.intensedebate.com%2F0 KB—✓3rd
https://intensedebate.com/wpfiles/jquery.js?ver=1.2.316 KB—✓1st
https://intensedebate.com/js/footer-ccpa.js3 KB—✓1st
https://s0.wp.com/wp-content/js/bilmur.min.js?i=8&m=2026176 KB—✓3rd
https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/a8c-analytics.js?v=202512182 KB—✓3rd
https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/965.a8c-analytics.js7 KB—✓3rd
https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/235.a8c-analytics.js7 KB—✓3rd
https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/126.a8c-analytics.js4 KB—✓3rd

Consider code splitting or tree shaking to reduce unused code.

Why this matters

This bundle has high unused code — code-split or tree-shake to ship only what executes.

Source: web.dev / Lighthouse coverage

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
No optimization needed
PASS
No optimization needed
Info::
No resource hint issues
A+
Page Weight Inventory
19 resources · 258 KB · 48 KB savings available
PASS
19 resources · 258 KB · 48 KB savings available
Info::
Within 1MB page-weight target
Got: 258 KB
Info::
9 third-party resources (23% of weight)
19 resources · 258.0 KiB · 9 third-party Within 1MB page-weight target
JavaScript 39% · 99.6 KiB
Image 38% · 99.3 KiB
Font 13% · 33.2 KiB
CSS 8% · 21.5 KiB
Document 1% · 3.8 KiB
Other 0% · 520 B

~47.6 KiB of savings available

Remove unused JavaScript: 47.6 KiB
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
19 requests over 1598ms
INFO
0 ms 500 ms 1.0 s 1.5 s 2.0 s FCP 2.1 s LCP 2.1 shttps://intensedebate.com// https://intensedebate.com/ — 200 — 3.8 KiB — 471 ms — h2https://intensedebate.com/css/sys.css?v=107/css/sys.css?v=107 https://intensedebate.com/css/sys.css?v=107 — 200 — 19.6 KiB — 438 ms — h2https://intensedebate.com/css/splash.css?v=107/css/splash.css?v=107 https://intensedebate.com/css/splash.css?v=107 — 200 — 1.2 KiB — 158 ms — h2https://s1.wp.com/i/fonts/recoleta/css/400.min.css?v=107s1.wp.com/i/fonts/recoleta/css/400.... https://s1.wp.com/i/fonts/recoleta/css/400.min.css?v=107 — 200 — 761 B — 27 ms — h2https://wordpress.com/remote-login.php?action=js&id=5116184&host=intensedebate.com&back=https%3A%2F%2Fwww.intensedebate.com%2Fwordpress.com/remote-login.php?acti... https://wordpress.com/remote-login.php?action=js&id=5116184&host=intensedebate.com&back=https%3A%2F%2Fwww.intensedebate.com%2F — 200 — 252 B — 189 ms — h2https://intensedebate.com/images/svg/intensedebate-logo.svg/images/svg/intensedebate-logo.svg https://intensedebate.com/images/svg/intensedebate-logo.svg — 200 — 3.5 KiB — 354 ms — h2https://intensedebate.com/images/screenshots/intensedebate-screenshot.jpg/images/screenshots/intensedebate-s... https://intensedebate.com/images/screenshots/intensedebate-screenshot.jpg — 200 — 93.9 KiB — 545 ms — h2https://intensedebate.com/images/svg/automattic-logo.svg/images/svg/automattic-logo.svg https://intensedebate.com/images/svg/automattic-logo.svg — 200 — 862 B — 156 ms — h3https://intensedebate.com/js/idm-combined.js?v=2/js/idm-combined.js?v=2 https://intensedebate.com/js/idm-combined.js?v=2 — 200 — 55.4 KiB — 468 ms — h3https://intensedebate.com/wpfiles/jquery.js?ver=1.2.3/wpfiles/jquery.js?ver=1.2.3 https://intensedebate.com/wpfiles/jquery.js?ver=1.2.3 — 200 — 16.4 KiB — 312 ms — h3https://intensedebate.com/js/footer-ccpa.js/js/footer-ccpa.js https://intensedebate.com/js/footer-ccpa.js — 200 — 3.0 KiB — 159 ms — h3https://s0.wp.com/wp-content/js/bilmur.min.js?i=8&m=202617s0.wp.com/wp-content/js/bilmur.min.... https://s0.wp.com/wp-content/js/bilmur.min.js?i=8&m=202617 — 200 — 5.5 KiB — 23 ms — h2https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/a8c-analytics.js?v=20251218s0.wp.com/wp-content/mu-plugins/a8c... https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/a8c-analytics.js?v=20251218 — 200 — 2.0 KiB — 29 ms — h2https://s1.wp.com/i/fonts/recoleta/400.woff2s1.wp.com/i/fonts/recoleta/400.woff... https://s1.wp.com/i/fonts/recoleta/400.woff2 — 200 — 33.2 KiB — 7 ms — h3https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/965.a8c-analytics.jss0.wp.com/wp-content/mu-plugins/a8c... https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/965.a8c-analytics.js — 200 — 6.5 KiB — 3 ms — h2https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/235.a8c-analytics.jss0.wp.com/wp-content/mu-plugins/a8c... https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/235.a8c-analytics.js — 200 — 6.6 KiB — 3 ms — h3https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/126.a8c-analytics.jss0.wp.com/wp-content/mu-plugins/a8c... https://s0.wp.com/wp-content/mu-plugins/a8c-analytics/126.a8c-analytics.js — 200 — 4.1 KiB — 2 ms — h3https://public-api.wordpress.com/geo/?_=1776810844524public-api.wordpress.com/geo/?_=177... https://public-api.wordpress.com/geo/?_=1776810844524 — 200 — 520 B — 128 ms — h2https://intensedebate.com/images/svg/intensedebate-logo-compact.svg/images/svg/intensedebate-logo-comp... https://intensedebate.com/images/svg/intensedebate-logo-compact.svg — 200 — 1.0 KiB — 157 ms — h3
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
51% of JavaScript execution is third-party
First-party Third-party 151ms · 0KB · $2/mo
Unattributable
Other
Optional
Execution 151ms
Transfer 0 KB
Monthly Cost $2/mo

51% of JavaScript execution time comes from third-party scripts.

Why this matters

Third-party scripts (analytics, ads, social, A/B testing) often dominate execution time — every one is a perf-and-privacy tax.

Learn more ▾

Each third-party script is a black box: you don't control when it loads, what it executes, or how much it grows. They often account for a major share of total blocking time on average sites (HTTP Archive's Web Almanac documents the trend). Audit which ones you actually need, defer the rest, and use facade patterns (lite-youtube, lite-vimeo) for embedded media.

Source: web.dev / HTTP Archive Web Almanac

How third-party costs are calculated

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback