Skip to content
https://disqus.com

Lighthouse Mobile

· 0 checks — Mobile 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.

55

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.

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.

RequestCache TTLTransfer Size
/next/current/marketing/assets/img/home/homepage-image-1-...300.0 s413.5 KiB
/next/current/marketing/assets/img/home/homepage-image-2-...300.0 s272.9 KiB
c.disquscdn.com/next/current/marketing/assets/img/home/homepage-hero.webp300.0 s72.9 KiB
c.disquscdn.com/next/current/marketing/assets/img/home/homepage-hero.avif300.0 s39.1 KiB
c.disquscdn.com/next/current/marketing/css/main.css300.0 s33.4 KiB
/next/current/marketing/assets/img/logos/nationalFootball...300.0 s25.4 KiB
c.disquscdn.com/next/current/marketing/js/entry.js300.0 s12.5 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/ziffDavis.png300.0 s11.7 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/bloomberg.png300.0 s11.3 KiB
c.disquscdn.com/next/current/marketing/assets/fonts/icons.woff2300.0 s10.6 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/pbs.png300.0 s9.4 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/rawStory.png300.0 s8.6 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/prisa.png300.0 s7.2 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/rogerEbert.png300.0 s6.8 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/fansided.png300.0 s5.3 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/immediateMedia.png300.0 s5.1 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/spectator.png300.0 s4.9 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/nytWirecutter.png300.0 s4.5 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/downDetector.png300.0 s3.6 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/peopleInc.png300.0 s3.3 KiB
c.disquscdn.com/next/current/marketing/assets/img/brand/disqus-logo-light.svg300.0 s3.1 KiB
c.disquscdn.com/next/current/marketing/assets/img/brand/disqus-logo-blue.svg300.0 s3.1 KiB
/next/current/marketing/assets/img/brand/disqus-logo-blue...300.0 s3.0 KiB
c.disquscdn.com/next/current/marketing/assets/img/home/revenue-streams.png300.0 s2.8 KiB
c.disquscdn.com/next/current/marketing/assets/img/home/protect.png300.0 s2.6 KiB
c.disquscdn.com/next/current/marketing/assets/img/logos/tmz.png300.0 s2.6 KiB
c.disquscdn.com/next/current/marketing/assets/img/home/known-users.png300.0 s2.6 KiB
c.disquscdn.com/next/current/marketing/assets/img/home/grow.png300.0 s2.5 KiB
js.hs-scripts.com/429754.js90.0 s1.0 KiB
/juggler/event.js?experiment=default&variant=control&page...0.0 ms322 B

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:91.181 source:map[column:146736 line:1 type:source-location url:https://c.disquscdn.com/next/marketing/js/1.3c02d41b51a282a0c728.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:12.357 source:map[column:100638 line:0 type:source-location url:https://c.disquscdn.com/next/marketing/js/2.4b34012ad5ab502f940f.js urlProvider:network]] map[reflowTime:154.01 source:map[column:708 line:0 type:source-location url:https://c.disquscdn.com/next/marketing/js/2.4b34012ad5ab502f940f.js urlProvider:network]]]

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-DIV
nodeLabel: div.home__wrapper > section.homepage-hero > div.homepage-hero__image-container > div.homepage-hero__image
path: 1,HTML,1,BODY,7,DIV,0,DIV,2,DIV,0,SECTION,3,DIV,0,DIV
selector: div.home__wrapper > section.homepage-hero > div.homepage-hero__image-container > div.homepage-hero__image
snippet: <div class="homepage-hero__image">

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.

URLTransfer SizeDuration
cmp.osano.com/AzqNQLSp9XcSy1Nx4/3863bb16-7170-4494-8eab-2f8e7a8ef10b/osano.js100.8 KiB1.3 s

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
c.disquscdn.com/next/current/marketing/assets/fonts/icons.woff25.0 ms

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
div.home__wrapper > section.panel > div.panel__content > div.img__container div.home__wrapper > section.panel > div.panel__content > div.img__container
/next/current/marketing/assets/img/home/homepage-image-1-...412.5 KiB166.7 KiB
div.home__wrapper > section.panel > div.panel__content > div.stats-img div.home__wrapper > section.panel > div.panel__content > div.stats-img
/next/current/marketing/assets/img/home/homepage-image-2-...272.1 KiB161.3 KiB
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
/next/current/marketing/assets/img/logos/nationalFootball...24.8 KiB24.6 KiB
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
c.disquscdn.com/next/current/marketing/assets/img/logos/ziffDavis.png11.2 KiB10.6 KiB
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
c.disquscdn.com/next/current/marketing/assets/img/logos/bloomberg.png10.8 KiB9.5 KiB
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
c.disquscdn.com/next/current/marketing/assets/img/logos/pbs.png8.9 KiB8.4 KiB
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
c.disquscdn.com/next/current/marketing/assets/img/logos/rawStory.png8.1 KiB6.9 KiB
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
c.disquscdn.com/next/current/marketing/assets/img/logos/rogerEbert.png6.3 KiB4.4 KiB

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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: 150 ms 29.8 KiB
URLTransfer SizeEst Savings
c.disquscdn.com/next/current/marketing/css/main.css32.9 KiB29.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: 450 ms 113.1 KiB
URLTransfer SizeEst Savings
c.disquscdn.com/next/marketing/js/1.3c02d41b51a282a0c728.js116.7 KiB59.9 KiB
c.disquscdn.com/next/marketing/js/2.4b34012ad5ab502f940f.js111.8 KiB28.0 KiB
cmp.osano.com/AzqNQLSp9XcSy1Nx4/3863bb16-7170-4494-8eab-2f8e7a8ef10b/osano.js100.3 KiB25.2 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
c.disquscdn.com/next/marketing/js/1.3c02d41b51a282a0c728.js976 ms261 ms39 ms
cmp.osano.com/AzqNQLSp9XcSy1Nx4/3863bb16-7170-4494-8eab-2f8e7a8ef10b/osano.js798 ms695 ms50 ms
disqus.com/437 ms18 ms1.8 ms
Unattributable409 ms5.9 ms0.0 ms
c.disquscdn.com/next/marketing/js/2.4b34012ad5ab502f940f.js272 ms213 ms55 ms
c.disquscdn.com/next/current/marketing/js/entry.js129 ms113 ms8.1 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.4 s
Style & Layout841 ms
Other628 ms
Script Parsing & Compilation157 ms
Rendering69 ms
Parse HTML & CSS41 ms
Garbage Collection12 ms

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 5.9 KiB
URLTransfer SizeEst Savings
c.disquscdn.com/next/current/marketing/css/main.css33.4 KiB5.9 KiB

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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,486 KiB
●Avoid long main-thread tasks 9 long tasks found
●Avoid non-composited animations 6 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 60 ms
●Server Backend Latencies 360 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 0 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○User Timing marks and measures
86

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
Cookie Policy div.osano-cm-window > div#efc1395e-8f06-4392-b2de-b0e9ef84b9c0 > div.osano-cm-dialog__content > a.osano-cm-storage-policy
Accept div.osano-cm-window > div#efc1395e-8f06-4392-b2de-b0e9ef84b9c0 > div.osano-cm-dialog__buttons > button.osano-cm-accept
Deny Non-Essential div.osano-cm-window > div#efc1395e-8f06-4392-b2de-b0e9ef84b9c0 > div.osano-cm-dialog__buttons > button.osano-cm-deny
Get started div.bg--light > div.home__wrapper > section.homepage-hero > a.homepage-hero__button
50M+ div.panel__content > ul.list > li > div.number
2.5B+ div.panel__content > ul.list > li > div.number
20M+ div.panel__content > ul.list > li > div.number
200+ div.panel__content > ul.list > li > div.number
Engage now » div.home__wrapper > section.panel > div.panel__content > a.link
Moderate now » div.home__wrapper > section.panel > div.panel__content > a.link
Analyze now » div.home__wrapper > section.panel > div.panel__content > a.link
Monetize now » div.home__wrapper > section.panel > div.panel__content > a.link
Platform Overview nav.site-footer__nav > ul.nav-list > li > a
Engagement nav.site-footer__nav > ul.nav-list > li > a
Moderation & Safety nav.site-footer__nav > ul.nav-list > li > a
Audience nav.site-footer__nav > ul.nav-list > li > a
Monetization nav.site-footer__nav > ul.nav-list > li > a
Pricing nav.site-footer__nav > ul.nav-list > li > a
Disqus Pro nav.site-footer__nav > ul.nav-list > li > a
Disqus for Business nav.site-footer__nav > ul.nav-list > li > a
Blog nav.site-footer__nav > ul.nav-list > li > a
Support nav.site-footer__nav > ul.nav-list > li > a
Knowledge Base nav.site-footer__nav > ul.nav-list > li > a
Disqus 101 nav.site-footer__nav > ul.nav-list > li > a
Discuss Disqus nav.site-footer__nav > ul.nav-list > li > a
Case Studies nav.site-footer__nav > ul.nav-list > li > a
API nav.site-footer__nav > ul.nav-list > li > a
Logos nav.site-footer__nav > ul.nav-list > li > a
History nav.site-footer__nav > ul.nav-list > li > a
Mission nav.site-footer__nav > ul.nav-list > li > a
Culture nav.site-footer__nav > ul.nav-list > li > a
How Does Disqus Work? nav.site-footer__nav > ul.nav-list > li > a
Community Tips nav.site-footer__nav > ul.nav-list > li > a
Increase Engagement & Retention nav.site-footer__nav > ul.nav-list > li > a
Moderating 101 nav.site-footer__nav > ul.nav-list > li > a
Developers nav.site-footer__nav > ul.nav-list > li > a
Other Integrations nav.site-footer__nav > ul.nav-list > li > 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
With the deprecation of third-party cookies, the rise of the walled gardens, an… section.panel > div.panel__content > div.trust-text > h4.trust-subheader
Disqus div.site-footer__container > nav.site-footer__nav > ul.nav-list > h3.list-header

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.home__wrapper > section.panel > div.panel__content > img.action-icon div.home__wrapper > section.panel > div.panel__content > img.action-icon
div.home__wrapper > section.panel > div.panel__content > img.action-icon div.home__wrapper > section.panel > div.panel__content > img.action-icon
div.home__wrapper > section.panel > div.panel__content > img.action-icon div.home__wrapper > section.panel > div.panel__content > img.action-icon
div.home__wrapper > section.panel > div.panel__content > img.action-icon div.home__wrapper > section.panel > div.panel__content > img.action-icon
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Disqus Platform Overview Engagement Moderation & Safety Audience Monetization P… footer.site-footer > div.site-footer__container > nav.site-footer__nav > ul.nav-list
Resources Blog Support Knowledge Base Disqus 101 Discuss Disqus Case Studies AP… footer.site-footer > div.site-footer__container > nav.site-footer__nav > ul.nav-list
About Us History Mission Culture footer.site-footer > div.site-footer__container > nav.site-footer__nav > ul.nav-list
Learn How Does Disqus Work? Community Tips Increase Engagement & Retention Mode… footer.site-footer > div.site-footer__container > nav.site-footer__nav > ul.nav-list

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○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 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.
○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.
○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.
100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLMap URL
c.disquscdn.com/next/marketing/js/2.4b34012ad5ab502f940f.js
cmp.osano.com/AzqNQLSp9XcSy1Nx4/3863bb16-7170-4494-8eab-2f8e7a8ef10b/osano.js/AzqNQLSp9XcSy1Nx4/3863bb16-7170-4494-8eab-2f8e7a8ef10b/o...
●Uses HTTPS
●Avoids deprecated APIs
●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
83

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
blog.disqus.com/introducing-the-disqus-sdk-bring-your-community-to-mobileLearn More

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.home__wrapper > section.panel > div.panel__content > img.action-icon div.home__wrapper > section.panel > div.panel__content > img.action-icon
div.home__wrapper > section.panel > div.panel__content > img.action-icon div.home__wrapper > section.panel > div.panel__content > img.action-icon
div.home__wrapper > section.panel > div.panel__content > img.action-icon div.home__wrapper > section.panel > div.panel__content > img.action-icon
div.home__wrapper > section.panel > div.panel__content > img.action-icon div.home__wrapper > section.panel > div.panel__content > img.action-icon
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo
div.panel__content > div.logos-container > div.img__container > img.logo div.panel__content > div.logos-container > div.img__container > img.logo

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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 are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback