Skip to content
https://intensedebate.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

99

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
IntenseDebate Screenshot div.id__home > div.id__home-feature > div.id__home-feature-split > img.id__home-feature-screenshot
intensedebate.com/images/screenshots/intensedebate-screenshot.jpg93.5 KiB83.2 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: IntenseDebate Screenshot
path: 1,HTML,1,BODY,1,DIV,2,DIV,0,DIV,1,IMG
selector: div.id__home > div.id__home-feature > div.id__home-feature-split > img.id__home-feature-screenshot
snippet: <img class="id__home-feature-screenshot" src="https://intensedebate.com/images/screenshots/intensedebate-screenshot.jpg" alt="IntenseDebate Screenshot">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 19.2 KiB
URLTransfer SizeEst Savings
intensedebate.com/css/sys.css?v=10719.4 KiB19.2 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.4 KiB
URLTransfer SizeEst Savings
intensedebate.com/css/sys.css?v=10719.6 KiB6.4 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 17.8 KiB
URLTransfer SizeEst Savings
intensedebate.com/js/idm-combined.js?v=255.1 KiB17.8 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 45.5 KiB
URLTransfer SizeEst Savings
intensedebate.com/js/idm-combined.js?v=255.1 KiB45.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
IntenseDebate Screenshot div.id__home > div.id__home-feature > div.id__home-feature-split > img.id__home-feature-screenshot
intensedebate.com/images/screenshots/intensedebate-screenshot.jpg
IntenseDebate logo div.id__home > nav > a.id__home-logo > img
intensedebate.com/images/svg/intensedebate-logo.svg
Automattic logo div.footer > div.wrap > a.automattic_joint > img
intensedebate.com/images/svg/automattic-logo.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 0.8 s
Max Potential First Input Delay 20 ms
Avoids enormous network payloads Total size was 258 KiB
Minimizes main-thread work 0.1 s
Network Requests
Network Round Trip Times 0 ms
Server Backend Latencies 160 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 160 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
JavaScript execution time
Avoid long main-thread tasks
Avoid non-composited animations
78

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sign in div.id__home > nav > div.id__home-sign-in > a
Explore the features div.id__home > div.id__home-hero > p > a.home-featureslink
Sign Up div.id__home > div.id__home-hero > div.id__home-hero-button > a
feature-rich div.id__home-feature-split > div > p > a
discussion tools ul > li > p > a
Akismet ul > li > p > a
Gravatar ul > li > p > a
Install Now div.id__home > div.id__home-feature > div.id__home-hero-button > a
AN MEDLEY body > div.footer > div.wrap > a.automattic_joint
Home div.wrap > p.footer-menu > a > span.r
Features div.wrap > p.footer-menu > a > span.r
About div.wrap > p.footer-menu > a > span.r
Press div.wrap > p.footer-menu > a > span.r
Developers div.wrap > p.footer-menu > a > span.r
Help div.wrap > p.footer-menu > a > span.r
TOS div.footer > div.wrap > p.footer-a8c > a
Privacy Policy div.footer > div.wrap > p.footer-a8c > a
Privacy Notice for California Users div.footer > div.wrap > p.footer-a8c > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Supercharge Your Community div > ul > li > h3

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Document has a `<title>` element
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1 <!DOCTYPE html>Syntax not understood
2 <html>Syntax not understood
3 <head>Syntax not understood
4 <meta charset="UTF-8">Syntax not understood
5 <link rel="icon" type="image/x-icon" href="/images/svg/intensedebate-logo-compact.svg"><link rel="stylesheet" type="text/css" href="/css/sys.css?v=107" />Syntax not understood
6<link rel="stylesheet" type="text/css" href="/css/base.css?v=107" />Syntax not understood
7<script defer id="bilmur" data-provider="intensedebate" data-service="admin" src="https://s0.wp.com/wp-content/js/bilmur.min.js?i=8&m=202617"></script><script type='text/javascript' src='//wordpress.com/remote-login.php?action=js&#038;id=5116184&#038;host=intensedebate.com&#038;back=https%3A%2F%2Fwww.intensedebate.com%2Frobots.txt'></script><title>IntenseDebate comments enhance and encourage conversation on your blog or website</title><meta name="description" content="IntenseDebate's comment system enhances and encourages conversation on your blog or website." /><meta name="keywords" content="intensedebate, intense debate, intense, debate, comments, comment, commenting, threaded, reply by email, commenter, comment system, commenting system, plugin, widget" /></head><body><style id="antiClickjack">body{display:none !important;}</style>Unknown directive
8 <script type="text/javascript">Syntax not understood
9 if (self === top) {Syntax not understood
10 var antiClickjack = document.getElementById("antiClickjack");Syntax not understood
11 antiClickjack.parentNode.removeChild(antiClickjack);Syntax not understood
12 } else {Syntax not understood
13 top.location = self.location;Syntax not understood
14 }Syntax not understood
15 </script> <div class="header">Syntax not understood
16 <div class="wrap">Syntax not understood
17 <div class="logo">Syntax not understood
18 <h1>Syntax not understood
19 <a href="/home" class="intensedebate-logo">IntenseDebate Comment System</a>Syntax not understood
20 </h1>Syntax not understood
21 </div>Syntax not understood
22 <ul class="menu">Syntax not understood
23 </ul>Syntax not understood
24 <div class="userbox">Syntax not understood
25 <ul class="userbox-menu">Syntax not understood
26 <li class="loggedout">Syntax not understood
27 <div class="userbox-avatar">Syntax not understood
28 <span></span>Syntax not understood
29 <img src="/images/avatar26.png" alt="[Avatar]" />Syntax not understood
30 </div>Syntax not understood
32 <a href="/logmein">Sign In</a>&nbsp;or&nbsp;<a href="/signup">Create an account</a>Syntax not understood
33 </li>Syntax not understood
34 </ul>Syntax not understood
35 </div>Syntax not understood
36 </div><!--/ wrap -->Syntax not understood
37 </div><!--/ header -->Syntax not understood
38 <div class="wrap"><div class="main"><div class="main-inner"><div id="wrapx"><div id="id-container"><div class="id-m">Syntax not understood
39<div class="columns single">Syntax not understood
40 <div class="main">Syntax not understood
41 <div class="id-main-t"><div></div></div>Syntax not understood
42 <div class="id-main-m">Syntax not understood
43 <div>Syntax not understood
44 <div>Syntax not understood
45 <h4>Error 404: Page not found</h4>Unknown directive
46 <p>We're sorry, but the page you tried to access simply doesn't exist. Please check for typing errors.</p>Syntax not understood
47 <p><a href="/">Go to the home page</a></p>Syntax not understood
48 </div>Syntax not understood
49 </div>Syntax not understood
50 </div>Syntax not understood
51 <div class="id-main-b"><div></div></div>Syntax not understood
52 </div> Syntax not understood
54</div></div></div></div></div> </div>Syntax not understood
55 </div><!--/ wrap-->Syntax not understood
56 <div class="footer">Syntax not understood
57 <div class="wrap">Syntax not understood
58 <span class="clear"></span>Syntax not understood
59 <a href='https://automattic.com' class="automattic_joint" style='text-decoration: none'>an <img src="/images/svg/automattic-logo.svg" alt="Automattic logo"/> Company</a>Unknown directive
60 <span class="clear"></span>Syntax not understood
61 <p class="footer-menu">Syntax not understood
62 <a href="/home"><span class="r">Home</span></a>Syntax not understood
63 <a href="/features"><span class="r">Features</span></a>Syntax not understood
64 <a href="/aboutus"><span class="r">About</span></a>Syntax not understood
65 <a href="https://automattic.com/press"><span class="r">Press</span></a>Unknown directive
66 <!--<a href="/contactus"><span class="r">Contact</span></a>-->Syntax not understood
67 <a href="https://support.intensedebate.com/category/developers/"><span class="r">Developers</span></a>Unknown directive
68 <a href="/help"><span class="r">Help</span></a>Syntax not understood
69 </p><!--/ footer-menu -->Syntax not understood
70 <p class="footer-a8c">Syntax not understood
71 &copy; 2026 Automattic Inc. <a href="/tos">TOS</a>Syntax not understood
72 | <a href="https://automattic.com/privacy/">Privacy Policy</a>Unknown directive
73 | <a href="https://automattic.com/privacy/#california-consumer-privacy-act-ccpa">Privacy Notice for California Users</a>Unknown directive
74 <span id="ccpa-donotsell" style="display:none">Unknown directive
75 | <a href="#">Do Not Sell or Share My Personal Information</a>Syntax not understood
76 </span>Syntax not understood
77 </p>Syntax not understood
78 <div class="clear"></div>Syntax not understood
79 </div><!--/ wrap -->Syntax not understood
80 </div><!--/ footer -->Syntax not understood
81 <script src="/js/idm-combined.js?v=2" type="text/javascript"></script>Syntax not understood
82 <script type="text/javascript" src="/wpfiles/jquery.js?ver=1.2.3"></script>Syntax not understood
83 <script type="text/javascript" src="/js/footer-ccpa.js"></script>Syntax not understood
84 <script type="text/javascript">Syntax not understood
85 window.a8cAnalyticsConfig = {"cookieBanner":{"skipBanner":false,"version":"2","cookieDomain":"intensedebate.com","v2CookieName":"eu_cb","v2Text":"We and our partners process your personal data (such as browsing data, IP addresses, cookie information, and other unique identifiers) based on your consent and\/or our legitimate interest to optimize our website, marketing activities, and your user experience.","v2OptionsText":"Your privacy is critically important to us. We and our partners use, store, and process your personal data to optimize: our <strong>website<\/strong> such as by improving security or conducting analytics, <strong>marketing activities<\/strong> to help deliver relevant marketing or content, and your <strong>user experience<\/strong> such as by remembering your account name, language settings, or cart information, where applicable. You can customize your cookie settings below. Learn more in our <a href=\"https:\/\/automattic.com\/privacy\/\" target=\"_blank\">Privacy Policy<\/a> and <a href=\"https:\/\/automattic.com\/cookies\/\" target=\"_blank\">Cookie Policy<\/a>.","v2EssentialOptionHeading":"Required","v2EssentialOptionText":"<strong>Required:<\/strong> These cookies are essential for our websites and services to perform basic functions and are necessary for us to operate certain features. These include those required to allow registered users to authenticate and perform account-related functions, store preferences set by users such as account name, language, and location, and ensure our services are operating properly.","v2AnalyticsOptionHeading":"Analytics","v2AnalyticsOptionText":"<strong>Analytics:<\/strong> These cookies allow us to optimize performance by collecting information on how users interact with our websites, including which pages are visited most, as well as other analytical data. We use these details to improve how our websites function and to understand how users interact with them. You can opt-out by logging into your account and changing your privacy settings at <a target=\"_blank\" href=\"https:\/\/wordpress.com\/me\/privacy\">https:\/\/wordpress.com\/me\/privacy<\/a>.","v2AdvertisingOptionHeading":"Advertising","v2AdvertisingOptionText":"<strong>Advertising:<\/strong> These cookies are set by us and our advertising partners to provide you with relevant content and to understand that content\u2019s effectiveness. They may be used to collect information about your online activities over time and across different websites to predict your preferences and to display more relevant advertisements to you. These cookies also allow a profile to be built about you and your interests, and enable personalized ads to be shown to you based on your profile.","v2CustomizeButtonText":"Customize","v2AcceptAllButtonText":"Accept All","v2AcceptSelectionButtonText":"Accept Selection"}};Unknown directive
86</script>Syntax not understood
87<script type="text/javascript" src="//s0.wp.com/wp-content/mu-plugins/a8c-analytics/a8c-analytics.js?v=20251218" charset="utf-8" async crossorigin="anonymous"></script></body></html>Syntax not understood

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback