C — https://intercom.io | BeaverCheck Audit

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Room to improve — your 35.2s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Contentful sites average 73

At average

Better than 43% of Contentful sites See full Contentful benchmark →

Amazon Route 53 sites average 72

At average

Better than 59% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

Page weighs 14.9 MB (5.9 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

2 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fintercom.io)](https://beavercheck.com/results/22a34d7e-4cd8-4ff7-b1cc-29c83b32bcd1)

HTML

<a href="https://beavercheck.com/results/22a34d7e-4cd8-4ff7-b1cc-29c83b32bcd1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fintercom.io" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fintercom.io

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 35.2s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.

Your LCP is 35.2s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

2 accessibility issues exclude users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~29%.

Speed (2)

Page takes 35.2s to load

+12% bounce

Users abandon at ~3s — you're 32.7s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 4.1s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (3)

22 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€510 investment → €1.37/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -97%

Investment

€510

6h · 5 findings

Monthly returns

€1.37 /mo

~€16 / year

Bandwidth savings €1.37

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
GDPR EUR 20,000,000
EAA EUR 500,000

€85 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€510

6.0 developer hours at €85/hr

Based on Ireland rates (€85/hr)

Quick wins

€85 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,668 / month at risk

~€120,500,016 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA

No privacy policy link detected
GDPR: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
GDPR: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
GDPR: EUR 10,000 – EUR 20,000,000

+5 more

Bandwidth Waste

€1.37 /mo

18470.8 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~1.8 MB per page load
Saves €1.37/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

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

7.75 s

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

35.25 s

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

4.10 s

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

0.000

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

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

35.66 s

Detailed Report

Audit breakdown by category with detailed findings.

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Request	Cache TTL	Transfer Size
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js	86400.0 s	124.4 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
widget.intercom.io/widget/tx2p130c	300.0 s	3.6 KiB
cdn.cookielaw.org/logos/static/ot_close.svg	86400.0 s	643 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:37.74 source:map[type:text value:[unattributed]]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:161.842 label:Time to first byte subpart:timeToFirstByte] map[duration:2584.204 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: This site uses cookies and similar technologies ("cookies") as strictly necessa…

path: 2,HTML,1,BODY,102,DIV,1,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV

selector: div.ot-sdk-row > div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text

snippet: <div id="onetrust-policy-text">

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.

URL	Transfer Size	Duration
/_next/static/css/3b37341195e53b8d.css?dpl=dpl_4hgrx9hLZK...	1.3 KiB
/_next/static/css/676748a766d7448c.css?dpl=dpl_4hgrx9hLZK...	7.4 KiB
/_next/static/css/6ccacb2259aa3818.css?dpl=dpl_4hgrx9hLZK...	2.3 KiB
/_next/static/css/2540b53a6f511ad2.css?dpl=dpl_4hgrx9hLZK...	30.8 KiB	1.1 s

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.

	URL	Resource Size	Est Savings
Black ink illustration of a flower `section.mt-16.5 > div.pt-8 > div.-mx-4 > img.min-w-[127px]`	/ims-image?url=%2Fintercom-marketing-site%2Fimg%2Fhome-20...	55.2 KiB	51.4 KiB
Silhouettes of two people cast in shadow on a gridded surface `section.mt-16.5 > div.pt-8 > div.-mx-4 > img.min-w-[127px]`	/ims-image?url=%2Fintercom-marketing-site%2Fimg%2Fhome-20...	37.9 KiB	26.8 KiB

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

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

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 801 ms

URL	Time Spent
intercom.io/	801 ms
www.intercom.com/	0.0 ms

Diagnostics

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 6.5 s 1.2 MiB

URL	Transfer Size	Est Savings
/_next/static/chunks/a0c1906b-d1fc95ae49ea5003.js?dpl=dpl...	156.0 KiB	149.7 KiB
js.intercomcdn.com/app-modern.ba2ed0b4.js	208.2 KiB	144.2 KiB
/_next/static/chunks/2629-88fb6c703b46561f.js?dpl=dpl_4hg...	127.9 KiB	125.1 KiB
js.intercomcdn.com/frame-modern.b7b766ac.js	192.3 KiB	116.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	186.6 KiB	88.1 KiB
js.intercomcdn.com/vendors~app-modern.f9e006dc.js	113.8 KiB	77.0 KiB
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js	124.3 KiB	75.8 KiB
www.googletagmanager.com/gtag/js?id=	84.6 KiB	54.4 KiB
js.intercomcdn.com/vendors~app~tooltips-modern.8ad896ec.js	185.4 KiB	53.2 KiB
js.intercomcdn.com/vendor-modern.df860bed.js	143.3 KiB	52.3 KiB
/_next/static/chunks/8381-6cef058388d564a4.js?dpl=dpl_4hg...	66.2 KiB	51.4 KiB
/_next/static/chunks/436-3cb885c89d4d7376.js?dpl=dpl_4hgr...	84.5 KiB	46.7 KiB
/_next/static/chunks/40e8e1f4.65772bd12f3f4050.js?dpl=dpl...	74.9 KiB	41.2 KiB
js.intercomcdn.com/app~tooltips-modern.d729f345.js	67.6 KiB	36.5 KiB
/_next/static/chunks/312542bb-ee3d55ecc01e248e.js?dpl=dpl...	38.8 KiB	34.4 KiB
/_next/static/chunks/5046-3a4711d75fc19354.js?dpl=dpl_4hg...	64.5 KiB	31.7 KiB
/_next/static/chunks/622a720c-808383e10886e4e4.js?dpl=dpl...	62.5 KiB	22.5 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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.intercom.com/	2.0 s	341 ms	99 ms
/_next/static/chunks/26-dc2cc545b9d48e03.js?dpl=dpl_4hgrx...	1.7 s	1.5 s	22 ms
/_next/static/chunks/935196fb-c39d7447d9ebc951.js?dpl=dpl...	1.6 s	1.6 s	15 ms
Unattributable	1.3 s	356 ms	0.0 ms
js.intercomcdn.com/app-modern.ba2ed0b4.js	753 ms	686 ms	51 ms
js.intercomcdn.com/frame-modern.b7b766ac.js	656 ms	515 ms	56 ms
/_next/static/chunks/436-3cb885c89d4d7376.js?dpl=dpl_4hgr...	367 ms	331 ms	29 ms
js.intercomcdn.com/vendor-modern.df860bed.js	358 ms	221 ms	39 ms
/_next/static/chunks/40e8e1f4.65772bd12f3f4050.js?dpl=dpl...	331 ms	265 ms	18 ms
www.googletagmanager.com/gtag/js?id=	288 ms	248 ms	22 ms
/_next/static/chunks/622a720c-808383e10886e4e4.js?dpl=dpl...	235 ms	148 ms	26 ms
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	149 ms	90 ms	56 ms
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js	136 ms	56 ms	41 ms
/_next/static/chunks/2594-b827ba79ef1eda0d.js?dpl=dpl_4hg...	98 ms	88 ms	9.9 ms
/_next/static/chunks/978-d9b67ed1ef8b2d87.js?dpl=dpl_4hgr...	80 ms	37 ms	2.9 ms
js.intercomcdn.com/vendors~app~tooltips-modern.8ad896ec.js	72 ms	1.1 ms	70 ms
/_next/static/chunks/8381-6cef058388d564a4.js?dpl=dpl_4hg...	60 ms	28 ms	29 ms
/_next/static/chunks/a0c1906b-d1fc95ae49ea5003.js?dpl=dpl...	57 ms	1.2 ms	55 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.

Category	Time Spent
Script Evaluation	6.7 s
Other	1.8 s
Style & Layout	827 ms
Script Parsing & Compilation	808 ms
Rendering	246 ms
Parse HTML & CSS	146 ms
Garbage Collection	116 ms

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 reason	Failure type
Pages with WebSocket cannot enter back/forward cache.	Pending browser support

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/intercom-marketing-site/animations/home/hero-fully-featu...	990.1 KiB
unpkg.com/@rive-app/webgl2@2.30.4/rive.wasm	601.7 KiB
js.intercomcdn.com/app-modern.ba2ed0b4.js	208.8 KiB
js.intercomcdn.com/vendors~app~tooltips-modern.8ad896ec.js	195.6 KiB
js.intercomcdn.com/frame-modern.b7b766ac.js	193.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	186.7 KiB
/_next/static/chunks/a0c1906b-d1fc95ae49ea5003.js?dpl=dpl...	156.2 KiB
js.intercomcdn.com/vendor-modern.df860bed.js	143.9 KiB
/ims-image?url=%2Fintercom-marketing-site%2Fimg%2Fhome-20...	138.9 KiB
/intercom-marketing-site/animations/home/hero-integrated-...	134.4 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 2 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 8 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 60 ms

○INP breakdown

○LCP request discovery

○Avoid large layout shifts

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Discord `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
API `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Email `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Facebook Messenger `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Instagram `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Messenger `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Slack `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Voice `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
WhatsApp `div.overflow-hidden > div.flex > div.flex > div.shrink-0`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
A fully-featured `div.col-span-full > div.col-span-12 > h2.text-heading-2 > span.text-current/40`
to resolve queries faster, deliver personalized service, engage proactively, an… `div.col-span-full > div.col-span-12 > p.text-callout > span.text-current/40`
Convert any conversation into a ticket with one click, automatically categorize… `h3.group > button#base-ui-_R_ajb5fiv6budbH2_ > div.text-current/70 > p.text-body`
Build powerful automations to route conversations, manage SLAs, and configure e… `h3.group > button#base-ui-_R_ejb5fiv6budbH2_ > div.text-current/70 > p.text-body`
Deliver tailored experiences `div.col-span-full > div.col-span-full > h3.text-heading-3 > span.text-current/40`
at the right moment `div.col-span-full > div > h3.text-heading-3 > span.text-current/40`
Keep customers informed about new features, known issues, and policy changes wi… `h3.group > button#base-ui-_R_1adb5fiv6budbH2_ > div.text-current/70 > p.text-body`
Build omnichannel message journeys with a no-code visual builder, targeting cus… `h3.group > button#base-ui-_R_1qdb5fiv6budbH2_ > div.text-current/70 > p.text-body`
every interaction `div.col-span-full > div > h3.text-heading-3 > span.text-current/40`
Monitor every AI and human conversation in real time, with AI-powered scoring a… `h3.group > button#base-ui-_R_1alb5fiv6budbH2_ > div.text-current/70 > p.text-body`
Access pre-built reports covering every support use case, and a fully customiza… `h3.group > button#base-ui-_R_1qlb5fiv6budbH2_ > div.text-current/70 > p.text-body`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more `div.border-linen > div#base-ui-_R_6jb5fiv6budbH1_ > div > a.font-sans!`
Learn more `div.border-linen > div#base-ui-_R_qdb5fiv6budbH1_ > div > a.font-sans!`
Learn more `div.border-linen > div#base-ui-_R_qlb5fiv6budbH1_ > div > a.font-sans!`
Terms `div#footer-terms-and-conditions > div.flex > div.flex > a.text-base`
Privacy `div#footer-terms-and-conditions > div.flex > div.flex > a.text-base`
Security `div#footer-terms-and-conditions > div.flex > div.flex > a.text-base`

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-*]` 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

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

●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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[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

○`<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.

○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

●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

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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 destination	Link Text
fin.ai/insights	Learn more
fin.ai/customers	more
fin.ai/customers	Learn more
www.intercom.com/helpdesk/copilot	Learn more
www.intercom.com/helpdesk/tickets	Learn more
www.intercom.com/helpdesk/copilot	Learn more
www.intercom.com/helpdesk/omnichannel	Learn more
www.intercom.com/app-store	Learn more
www.intercom.com/helpdesk/outbound	Learn more
www.intercom.com/helpdesk/outbound	Learn more
www.intercom.com/helpdesk/outbound	Learn more
www.intercom.com/helpdesk/outbound	Learn more
fin.ai/insights	Learn more
fin.ai/insights	Learn more
www.intercom.com/helpdesk/reporting	Learn more
fin.ai/insights	Learn more
trust.intercom.com/	Learn more
fin.ai/professional-services	Learn more
fin.ai/blueprint/introducing-ai-agents	Learn more
www.intercom.com/pricing	Learn more

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

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 #	Content	Error
8	`LLMs: https://www.intercom.com/llms.txt`	`Unknown directive`

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 are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

1.04 s

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

2.74 s

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

32.14 s

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

0.034

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

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

40.42 s

Detailed Report

Audit breakdown by category with detailed findings.

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:31.505 source:map[column:8514 line:1 type:source-location url:https://vercel.intercom.com/_next/static/chunks/26-dc2cc545b9d48e03.js?dpl=dpl_4hgrx9hLZKRgStzoxwX8T6FKyved 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:57.467 source:map[type:text value:[unattributed]]] map[reflowTime:17.556 source:map[column:2650 line:0 type:source-location url:https://vercel.intercom.com/_next/static/chunks/app/(i2y4)/(home)/page-16c4e9204266aeb5.js?dpl=dpl_4hgrx9hLZKRgStzoxwX8T6FKyved urlProvider:network]] map[reflowTime:13.949 source:map[column:31061 line:8 type:source-location url:https://vercel.intercom.com/_next/static/chunks/8381-6cef058388d564a4.js?dpl=dpl_4hgrx9hLZKRgStzoxwX8T6FKyved urlProvider:network]] map[reflowTime:0.608 source:map[column:11725 line:0 type:source-location url:https://vercel.intercom.com/_next/static/chunks/app/(i2y4)/layout-6939d62862f906d0.js?dpl=dpl_4hgrx9hLZKRgStzoxwX8T6FKyved urlProvider:network]] map[reflowTime:0.283 source:map[column:35717 line:0 type:source-location url:https://vercel.intercom.com/_next/static/chunks/5235-d78c98f39b171712.js?dpl=dpl_4hgrx9hLZKRgStzoxwX8T6FKyved urlProvider:network]] map[reflowTime:0.245 source:map[column:297513 line:0 type:source-location url:https://vercel.intercom.com/_next/static/chunks/436-3cb885c89d4d7376.js?dpl=dpl_4hgrx9hLZKRgStzoxwX8T6FKyved urlProvider:network]]]

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.

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

value: No additional origins are good candidates for preconnecting

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.

URL	Transfer Size	Duration
/_next/static/css/676748a766d7448c.css?dpl=dpl_4hgrx9hLZK...	7.4 KiB
/_next/static/css/2540b53a6f511ad2.css?dpl=dpl_4hgrx9hLZK...	30.5 KiB	453 ms
/_next/static/css/3b37341195e53b8d.css?dpl=dpl_4hgrx9hLZK...	1.3 KiB
/_next/static/css/6ccacb2259aa3818.css?dpl=dpl_4hgrx9hLZK...	2.3 KiB

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.

Request	Cache TTL	Transfer Size
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js	86400.0 s	124.4 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
widget.intercom.io/widget/tx2p130c	300.0 s	3.6 KiB
cdn.cookielaw.org/logos/static/ot_close.svg	86400.0 s	643 B

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.

	URL	Resource Size	Est Savings
	/ims-image?url=%2Fintercom-marketing-site%2Fimg%2Fhome-20...	39.8 KiB	26.7 KiB
Decorative background image `div.col-span-full > div.flex > div.bg-chalk > img.z-0`	/ims-image?url=%2Fintercom-marketing-site%2Fimg%2Fhome-20...	36.2 KiB	17.5 KiB
Silhouettes of two people cast in shadow on a gridded surface `section.mt-16.5 > div.pt-8 > div.-mx-4 > img.min-w-[127px]`	/ims-image?url=%2Fintercom-marketing-site%2Fimg%2Fhome-20...	17.4 KiB	13.8 KiB

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

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

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 247 ms

URL	Time Spent
intercom.io/	247 ms
www.intercom.com/	0.0 ms

Diagnostics

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 170 ms 1.2 MiB

URL	Transfer Size	Est Savings
/_next/static/chunks/a0c1906b-d1fc95ae49ea5003.js?dpl=dpl...	156.0 KiB	149.7 KiB
js.intercomcdn.com/app-modern.ba2ed0b4.js	208.2 KiB	144.2 KiB
/_next/static/chunks/2629-88fb6c703b46561f.js?dpl=dpl_4hg...	127.9 KiB	125.1 KiB
js.intercomcdn.com/frame-modern.b7b766ac.js	192.3 KiB	115.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	186.6 KiB	88.0 KiB
js.intercomcdn.com/vendors~app-modern.f9e006dc.js	113.8 KiB	77.0 KiB
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js	124.3 KiB	75.8 KiB
www.googletagmanager.com/gtag/js?id=	84.6 KiB	54.4 KiB
js.intercomcdn.com/vendors~app~tooltips-modern.8ad896ec.js	185.4 KiB	53.2 KiB
js.intercomcdn.com/vendor-modern.df860bed.js	143.3 KiB	52.3 KiB
/_next/static/chunks/8381-6cef058388d564a4.js?dpl=dpl_4hg...	66.2 KiB	50.9 KiB
/_next/static/chunks/436-3cb885c89d4d7376.js?dpl=dpl_4hgr...	84.5 KiB	46.4 KiB
/_next/static/chunks/40e8e1f4.65772bd12f3f4050.js?dpl=dpl...	74.9 KiB	41.2 KiB
js.intercomcdn.com/app~tooltips-modern.d729f345.js	67.6 KiB	36.4 KiB
/_next/static/chunks/312542bb-ee3d55ecc01e248e.js?dpl=dpl...	38.8 KiB	34.4 KiB
/_next/static/chunks/5046-3a4711d75fc19354.js?dpl=dpl_4hg...	64.5 KiB	31.7 KiB
/_next/static/chunks/622a720c-808383e10886e4e4.js?dpl=dpl...	62.5 KiB	22.5 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.

URL	Total CPU Time	Script Evaluation	Script Parse
/_next/static/chunks/40e8e1f4.65772bd12f3f4050.js?dpl=dpl...	37.0 s	36.7 s	5.9 ms
/_next/static/chunks/935196fb-c39d7447d9ebc951.js?dpl=dpl...	904 ms	890 ms	2.9 ms
/_next/static/chunks/26-dc2cc545b9d48e03.js?dpl=dpl_4hgrx...	567 ms	482 ms	4.1 ms
/_next/static/chunks/622a720c-808383e10886e4e4.js?dpl=dpl...	517 ms	466 ms	4.8 ms
Unattributable	369 ms	85 ms	0.0 ms
www.intercom.com/	366 ms	98 ms	14 ms
js.intercomcdn.com/frame-modern.b7b766ac.js	249 ms	218 ms	13 ms
js.intercomcdn.com/app-modern.ba2ed0b4.js	199 ms	183 ms	16 ms
js.intercomcdn.com/vendor-modern.df860bed.js	103 ms	68 ms	9.4 ms
/_next/static/chunks/a0c1906b-d1fc95ae49ea5003.js?dpl=dpl...	99 ms	86 ms	14 ms
/_next/static/chunks/978-d9b67ed1ef8b2d87.js?dpl=dpl_4hgr...	94 ms	8.6 ms	0.7 ms
www.googletagmanager.com/gtag/js?id=	80 ms	70 ms	7.2 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.

Category	Time Spent
Script Evaluation	39.6 s
Other	723 ms
Style & Layout	221 ms
Script Parsing & Compilation	206 ms
Rendering	79 ms
Garbage Collection	58 ms
Parse HTML & CSS	49 ms

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 reason	Failure type
Pages with WebSocket cannot enter back/forward cache.	Pending browser support

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/intercom-marketing-site/animations/home/hero-fully-featu...	990.0 KiB
unpkg.com/@rive-app/webgl2@2.30.4/rive.wasm	601.8 KiB
/ims-image?url=%2Fintercom-marketing-site%2Fimg%2Fhome-20...	242.9 KiB
js.intercomcdn.com/app-modern.ba2ed0b4.js	208.8 KiB
js.intercomcdn.com/vendors~app~tooltips-modern.8ad896ec.js	195.6 KiB
js.intercomcdn.com/frame-modern.b7b766ac.js	193.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	186.7 KiB
/_next/static/chunks/a0c1906b-d1fc95ae49ea5003.js?dpl=dpl...	156.2 KiB
js.intercomcdn.com/vendor-modern.df860bed.js	143.9 KiB
www.intercom.com/contact-sales?_rsc=1r34m	134.6 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 2 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 180 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 60 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Product Customers Resources Pricing `div.wsc:px-3 > nav > div.wsc:items-center > ul.wsc:flex`
Contact sales View demo Start free trial `div.wsc:px-3 > nav > div.wsc:items-center > ul.wsc:ml-auto`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Discord `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
API `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Email `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Facebook Messenger `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Instagram `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Messenger `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Slack `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
Voice `div.overflow-hidden > div.flex > div.flex > div.shrink-0`
WhatsApp `div.overflow-hidden > div.flex > div.flex > div.shrink-0`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Fully-featured helpdesk `div.flex > div.flex-1 > button.relative > span.text-body-lg-desktop`
Natively integrated AI Agent `div.flex > div.flex-1 > button.relative > span.text-body-lg-desktop`
Self-improving system `div.flex > div.flex-1 > button.relative > span.text-body-lg-desktop`
Convert any conversation into a ticket with one click, automatically categorize… `button.focus-visible:outline-2 > div.flex > div.text-body > p`
Build powerful automations to route conversations, manage SLAs, and configure e… `button.focus-visible:outline-2 > div.flex > div.text-body > p`
Keep customers informed about new features, known issues, and policy changes wi… `button.focus-visible:outline-2 > div.flex > div.text-body > p`
Build omnichannel message journeys with a no-code visual builder, targeting cus… `button.focus-visible:outline-2 > div.flex > div.text-body > p`
Monitor every AI and human conversation in real time, with AI-powered scoring a… `button.overflow-hidden > div.flex > div.text-body > p`
Access pre-built reports covering every support use case, and a fully customiza… `button.overflow-hidden > div.flex > div.text-body > p`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.wsc:ml-auto > li > span.wsc:relative > a.wsc:items-center `ul.wsc:ml-auto > li > span.wsc:relative > a.wsc:items-center`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more `div.flex > div.group/thumb > div.peer-data-selected:opacity-100 > a.text-inline-link`
Learn more `div.flex > div.group/thumb > div.peer-data-selected:opacity-100 > a.text-inline-link`
Learn more `div.flex > div.group/thumb > div.peer-data-selected:opacity-100 > a.text-inline-link`
Learn more `div.flex > div.group/thumb > div.peer-data-selected:opacity-100 > a.text-inline-link`
Learn more `div.flex > div.group/thumb > div.peer-data-selected:opacity-100 > a.text-inline-link`
Learn more `div.flex > div.group/thumb > div.peer-data-selected:opacity-100 > a.text-inline-link`
Learn more `div.flex > div.group/thumb > div.peer-data-selected:opacity-100 > a.text-inline-link`
Learn more `div.flex > div.group/thumb > div.peer-data-selected:opacity-100 > a.text-inline-link`

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>`

●`[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

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

●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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[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

○`<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.

○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

●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

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

SEO

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 destination	Link Text
fin.ai/insights	Learn more
fin.ai/customers	more
fin.ai/customers	Learn more
www.intercom.com/helpdesk/copilot	Learn more
www.intercom.com/helpdesk/tickets	Learn more
www.intercom.com/helpdesk/copilot	Learn more
www.intercom.com/helpdesk/omnichannel	Learn more
www.intercom.com/app-store	Learn more
www.intercom.com/helpdesk/outbound	Learn more
www.intercom.com/helpdesk/outbound	Learn more
www.intercom.com/helpdesk/outbound	Learn more
www.intercom.com/helpdesk/outbound	Learn more
fin.ai/insights	Learn more
fin.ai/insights	Learn more
www.intercom.com/helpdesk/reporting	Learn more
fin.ai/insights	Learn more
trust.intercom.com/	Learn more
fin.ai/professional-services	Learn more
fin.ai/blueprint/introducing-ai-agents	Learn more
www.intercom.com/pricing	Learn more

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

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 #	Content	Error
8	`LLMs: https://www.intercom.com/llms.txt`	`Unknown directive`

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 are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://intercom.io

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (1)

Content (1)

Navigation (3)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Best practices

Best Practices

SEO

Content Best Practices

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Names and labels

Best practices

Best Practices

SEO

Content Best Practices

Crawling and Indexing

Keyboard Shortcuts