C — https://www.intercom.com

Site Health

Score: 70 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

Page weighs 13.7 MB (5.5 MB transferred)

Performance › Page Weight Budget

2 link(s) with no accessible text

Accessibility › Link & Button Quality

No <main> landmark found

Accessibility › Landmark Structure

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.intercom.com)](https://beavercheck.com/results/82a093d0-8b99-4ee0-9cc1-1a080470a241)

HTML

<a href="https://beavercheck.com/results/82a093d0-8b99-4ee0-9cc1-1a080470a241"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.intercom.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.intercom.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

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.

6.17 s

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

26.94 s

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

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

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

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

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

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

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

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

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.

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

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

	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

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.

URL	Transfer Size	Duration
/_next/static/css/676748a766d7448c.css?dpl=dpl_BqD6CWdzuS...	7.6 KiB	152 ms
/_next/static/css/249d539491eed9a1.css?dpl=dpl_BqD6CWdzuS...	27.3 KiB	998 ms
/_next/static/css/3b37341195e53b8d.css?dpl=dpl_BqD6CWdzuS...	1.6 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.

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.

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.

Estimated savings: 2.9 s 937.6 KiB

URL	Transfer Size	Est Savings
js.intercomcdn.com/app-modern.3d77ec50.js	203.2 KiB	140.4 KiB
/_next/static/chunks/5578-fcf5e3c5eebba4a4.js?dpl=dpl_BqD...	124.9 KiB	122.4 KiB
js.intercomcdn.com/frame-modern.40aacdf2.js	191.1 KiB	115.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	185.5 KiB	87.4 KiB
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js	124.3 KiB	80.5 KiB
js.intercomcdn.com/vendors~app-modern.83c11406.js	113.8 KiB	77.2 KiB
js.intercomcdn.com/vendors~app~tooltips-modern.b7912b3d.js	184.7 KiB	52.7 KiB
www.googletagmanager.com/gtag/js?id=	82.8 KiB	52.6 KiB
js.intercomcdn.com/vendor-modern.df860bed.js	143.3 KiB	52.4 KiB
/_next/static/chunks/40e8e1f4.257d373edc4c1f16.js?dpl=dpl...	76.1 KiB	42.2 KiB
js.intercomcdn.com/app~tooltips-modern.aa460ef0.js	67.1 KiB	36.2 KiB
/_next/static/chunks/312542bb-9afa27252aed1afb.js?dpl=dpl...	38.7 KiB	34.3 KiB
/_next/static/chunks/622a720c-066705fd37ae558b.js?dpl=dpl...	62.3 KiB	22.7 KiB
/_next/static/chunks/878-86f0e305bd5f22c8.js?dpl=dpl_BqD6...	37.6 KiB	21.1 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.

URL	Total CPU Time	Script Evaluation	Script Parse
/_next/static/chunks/935196fb-dc3b4a7e6b49d365.js?dpl=dpl...	2.7 s	2.7 s	17 ms
www.intercom.com/	2.2 s	468 ms	67 ms
/_next/static/chunks/26-f5042ec235252c8a.js?dpl=dpl_BqD6C...	2.1 s	1.9 s	37 ms
js.intercomcdn.com/vendor-modern.df860bed.js	1.4 s	1.1 s	81 ms
Unattributable	1.3 s	378 ms	0.0 ms
js.intercomcdn.com/app-modern.3d77ec50.js	1.2 s	1.0 s	91 ms
/_next/static/chunks/40e8e1f4.257d373edc4c1f16.js?dpl=dpl...	398 ms	294 ms	26 ms
www.googletagmanager.com/gtag/js?id=	371 ms	314 ms	34 ms
/_next/static/chunks/webpack-085f434159b2cf35.js?dpl=dpl_...	353 ms	351 ms	0.8 ms
/_next/static/chunks/622a720c-066705fd37ae558b.js?dpl=dpl...	282 ms	187 ms	27 ms
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	193 ms	109 ms	79 ms
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js	129 ms	59 ms	68 ms
js.intercomcdn.com/vendors~app~tooltips-modern.b7912b3d.js	128 ms	1.6 ms	125 ms
js.intercomcdn.com/frame-modern.40aacdf2.js	103 ms	21 ms	82 ms
/_next/static/chunks/978-1ad32b15f153809c.js?dpl=dpl_BqD6...	90 ms	15 ms	4.0 ms
js.intercomcdn.com/vendors~app-modern.83c11406.js	72 ms	2.9 ms	68 ms
widget.intercom.io/widget/tx2p130c	58 ms	53 ms	1.6 ms
js.intercomcdn.com/app~tooltips-modern.aa460ef0.js	51 ms	1.9 ms	48 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

Category	Time Spent
Script Evaluation	9.0 s
Other	1.9 s
Script Parsing & Compilation	1.1 s
Style & Layout	877 ms
Rendering	258 ms
Parse HTML & CSS	154 ms
Garbage Collection	126 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

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.

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.5 KiB
js.intercomcdn.com/app-modern.3d77ec50.js	203.9 KiB
js.intercomcdn.com/vendors~app~tooltips-modern.b7912b3d.js	194.9 KiB
js.intercomcdn.com/frame-modern.40aacdf2.js	191.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	185.5 KiB
js.intercomcdn.com/vendor-modern.df860bed.js	143.9 KiB
/ims-image?url=%2Fintercom-marketing-site%2Fimg%2Fhome-20...	138.6 KiB
/intercom-marketing-site/animations/home/hero-integrated-...	134.4 KiB
/_next/static/chunks/5578-fcf5e3c5eebba4a4.js?dpl=dpl_BqD...	125.0 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

●Font display

●Forced reflow

●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

●Avoid non-composited animations 8 animated elements found

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

●Network Requests

●Network Round Trip Times 250 ms

●Server Backend Latencies 230 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 50 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.

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.

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.

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`

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

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

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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` 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.

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

Best Practices

General

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Cookie

●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

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

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.

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

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.

744 ms

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

2.28 s

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

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

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

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

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

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.

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:36.298 source:map[column:8166 line:1 type:source-location url:https://vercel.intercom.com/_next/static/chunks/26-f5042ec235252c8a.js?dpl=dpl_BqD6CWdzuScGtq2YjdPhp6CWM6nM 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:84.572 source:map[type:text value:[unattributed]]] map[reflowTime:19.147 source:map[column:2583 line:0 type:source-location url:https://vercel.intercom.com/_next/static/chunks/app/(i2y4)/(home)/page-a560149e509a2116.js?dpl=dpl_BqD6CWdzuScGtq2YjdPhp6CWM6nM urlProvider:network]] map[reflowTime:17.151 source:map[column:4128 line:0 type:source-location url:https://vercel.intercom.com/_next/static/chunks/6238-7db67689d69addd4.js?dpl=dpl_BqD6CWdzuScGtq2YjdPhp6CWM6nM urlProvider:network]] map[reflowTime:0.644 source:map[column:16010 line:0 type:source-location url:https://vercel.intercom.com/_next/static/chunks/1130-6ccdf13dcda4fb47.js?dpl=dpl_BqD6CWdzuScGtq2YjdPhp6CWM6nM urlProvider:network]] map[reflowTime:0.68 source:map[column:7941 line:0 type:source-location url:https://vercel.intercom.com/_next/static/chunks/app/(i2y4)/layout-da6f5216df3ed2fd.js?dpl=dpl_BqD6CWdzuScGtq2YjdPhp6CWM6nM urlProvider:network]] map[reflowTime:1.123 source:map[column:44909 line:0 type:source-location url:https://vercel.intercom.com/_next/static/chunks/999-56075b297e2a8cfe.js?dpl=dpl_BqD6CWdzuScGtq2YjdPhp6CWM6nM urlProvider:network]] map[reflowTime:0.336 source:map[column:376 line:876 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-WB899HL 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.

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.

URL	Transfer Size	Duration
/_next/static/css/676748a766d7448c.css?dpl=dpl_BqD6CWdzuS...	7.4 KiB
/_next/static/css/249d539491eed9a1.css?dpl=dpl_BqD6CWdzuS...	27.5 KiB	410 ms
/_next/static/css/3b37341195e53b8d.css?dpl=dpl_BqD6CWdzuS...	1.4 KiB

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

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
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	59 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	49 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B
/a?id=GTM-WB899HL&v=3&t=t&pid=921076983&gtm=45He6411h1v79...	0.0 ms	11 B

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

	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.

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.

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.

Estimated savings: 80 ms 934.6 KiB

URL	Transfer Size	Est Savings
js.intercomcdn.com/app-modern.3d77ec50.js	203.2 KiB	140.4 KiB
/_next/static/chunks/5578-fcf5e3c5eebba4a4.js?dpl=dpl_BqD...	124.9 KiB	122.4 KiB
js.intercomcdn.com/frame-modern.40aacdf2.js	191.1 KiB	115.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	184.9 KiB	85.0 KiB
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js	124.3 KiB	80.5 KiB
js.intercomcdn.com/vendors~app-modern.83c11406.js	113.8 KiB	77.2 KiB
js.intercomcdn.com/vendors~app~tooltips-modern.b7912b3d.js	184.7 KiB	52.7 KiB
www.googletagmanager.com/gtag/js?id=	82.8 KiB	52.6 KiB
js.intercomcdn.com/vendor-modern.df860bed.js	143.3 KiB	52.4 KiB
/_next/static/chunks/40e8e1f4.257d373edc4c1f16.js?dpl=dpl...	76.1 KiB	42.2 KiB
js.intercomcdn.com/app~tooltips-modern.aa460ef0.js	67.1 KiB	36.2 KiB
/_next/static/chunks/312542bb-9afa27252aed1afb.js?dpl=dpl...	38.7 KiB	34.3 KiB
/_next/static/chunks/622a720c-066705fd37ae558b.js?dpl=dpl...	62.3 KiB	22.6 KiB
/_next/static/chunks/878-86f0e305bd5f22c8.js?dpl=dpl_BqD6...	37.6 KiB	21.1 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.

URL	Total CPU Time	Script Evaluation	Script Parse
/_next/static/chunks/40e8e1f4.257d373edc4c1f16.js?dpl=dpl...	37.0 s	36.7 s	7.6 ms
/_next/static/chunks/935196fb-dc3b4a7e6b49d365.js?dpl=dpl...	1.4 s	1.4 s	6.7 ms
/_next/static/chunks/622a720c-066705fd37ae558b.js?dpl=dpl...	749 ms	688 ms	6.7 ms
/_next/static/chunks/26-f5042ec235252c8a.js?dpl=dpl_BqD6C...	691 ms	620 ms	6.2 ms
www.intercom.com/	504 ms	166 ms	22 ms
Unattributable	458 ms	118 ms	0.0 ms
js.intercomcdn.com/frame-modern.40aacdf2.js	344 ms	296 ms	23 ms
js.intercomcdn.com/app-modern.3d77ec50.js	271 ms	239 ms	21 ms
js.intercomcdn.com/vendor-modern.df860bed.js	135 ms	81 ms	25 ms
www.googletagmanager.com/gtag/js?id=	129 ms	113 ms	8.5 ms
/_next/static/chunks/978-1ad32b15f153809c.js?dpl=dpl_BqD6...	104 ms	20 ms	0.7 ms
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	74 ms	38 ms	20 ms
/_next/static/chunks/4964-e6d1de3b1bc1e933.js?dpl=dpl_BqD...	71 ms	60 ms	4.4 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

Category	Time Spent
Script Evaluation	40.6 s
Other	836 ms
Script Parsing & Compilation	262 ms
Style & Layout	260 ms
Garbage Collection	89 ms
Rendering	83 ms
Parse HTML & CSS	60 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

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.

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.6 KiB
/ims-image?url=%2Fintercom-marketing-site%2Fimg%2Fhome-20...	242.6 KiB
js.intercomcdn.com/app-modern.3d77ec50.js	203.9 KiB
js.intercomcdn.com/vendors~app~tooltips-modern.b7912b3d.js	194.9 KiB
js.intercomcdn.com/frame-modern.40aacdf2.js	191.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-WB899HL	185.0 KiB
js.intercomcdn.com/vendor-modern.df860bed.js	143.9 KiB
www.intercom.com/contact-sales?_rsc=1r34m	134.6 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

●Document request latency

●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 250 ms

●Server Backend Latencies 170 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 50 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.

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.

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.

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.

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.

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`

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

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

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

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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` 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.

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

Best Practices

General

Issue type
Cookie

●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

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

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.

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://www.intercom.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Best practices

Best Practices

General

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

General

SEO

Content Best Practices

Crawling and Indexing

Keyboard Shortcuts