Intercom.com SEO Score & Performance Report

← Back to Home

https://intercom.com

Desktop

Mobile

Score Analysis

LIVE

71OF 100

Needs Work

SEO

Perf

Page Title

The AI customer service company

Google Search Preview|How your page appears in search results

SERP Score

Good

intercom.com

https://intercom.com

The AI customer service company

Fin is the leading AI Agent for customer service delivering the highest quality answers and handling the most complex queries. Employ Fin on any helpdesk or the Intercom Suite today.

Snippet Quality

Title Length31 chars

030–60 optimal90

Description Length182 chars

070–160 optimal240

Power Word

CTA

URL Readable

HTTPS

No Truncation

Recommendations3 found

infoTitle lacks CTR-boosting power words

Consider adding words like "free", "guide", "best" to improve click-through rate

infoMeta description too long (182 chars)

Keep under 160 characters

infoMeta description lacks a call-to-action

Add action verbs like "Learn", "Discover" to encourage clicks

Performance Report|Google PageSpeed Insights

Lighthouse v13.0.1Mar 3, 2026, 05:37 PM

Status200OK

Load Time0.46sFAST

HTML Size57 KBOK

CompressionGZIPON

HTTPSSecureSECURE

Render-Block1 scriptsFOUND

Poor

LCPPOOR

19.2 s

Largest Contentful Paint

FCPNEEDS WORK

1.9 s

First Contentful Paint

TBTPOOR

1,070 ms

Total Blocking Time

CLSGOOD

0.006

Cumulative Layout Shift

SIPOOR

7.2 s

Speed Index

TTFBGOOD

Root document took 10 ms

Time to First Byte

FIDPOOR

480 ms

First Input Delay

Page Load FilmstripVisual timeline of how your page renders

0.8s

1.5s

2.3s

3.1s

3.8s

4.6s

5.4s

6.1s

Issues Found9 found

criticalLargest Contentful Paint: 19.2 s (poor)high

How to fixOptimize images, preload LCP element, reduce server response time. Target < 2.5s

What this meansLCP measures when the largest visible element finishes rendering.

SEO ImpactSlow LCP increases bounce rate and hurts Core Web Vitals ranking signal.

criticalTotal Blocking Time: 1,070 ms (poor)high

How to fixBreak up long tasks, defer non-critical JavaScript, use web workers. Target < 200ms

What this meansTBT measures total time the main thread was blocked. It's a lab proxy for INP.

SEO ImpactHigh TBT means the page feels unresponsive. This directly impacts INP, a Core Web Vital.

warningSpeed Index: 7.2 s (poor)medium

How to fixOptimize critical rendering path, reduce main-thread work. Target < 3.4s

What this meansSpeed Index measures how quickly content is visually displayed during page load.

SEO ImpactA high Speed Index means the page appears to load slowly.

warningReduce unused JavaScript - Est savings of 722 KiB (potential savings: 1380ms) / 722 KB

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

warningAvoid multiple page redirects - Est savings of 780 ms (potential savings: 780ms)

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

infoAvoid enormous network payloads - Total size was 16,957 KiB

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

infoReduce JavaScript execution time - 2.2 s

How to fixConsider 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.

infoMinimize main-thread work - 3.0 s

How to fixConsider 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

warning1 render-blocking scripts in <head>

How to fixAdd async or defer to scripts

OpportunitiesPotential savings to improve load time

Reduce unused JavaScriptEst savings of 722 KiB

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

1.4s potential savings 722 KB transferable

Avoid multiple page redirectsEst savings of 780 ms

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

0.8s potential savings

Avoid enormous network payloadsTotal size was 16,957 KiB

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

DiagnosticsAdditional performance insights

Reduce JavaScript execution time

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.

2.2 s

Minimize main-thread work

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

3.0 s

Font display

LCP breakdown

Tasks

Avoid large layout shifts

Avoid long main-thread tasks

Reduce unused CSS

Cumulative Layout Shift

Resources Summary

Final Screenshot

Screenshot Thumbnails

Optimize DOM size

User Timing marks and measures

Script Treemap Data

Initial server response time was short

Network Round Trip Times

Forced reflow

Duplicated JavaScript

Network Requests

Minify JavaScript

Layout shift culprits

Optimize viewport for mobile

Image elements have explicit `width` and `height`

Minify CSS

Metrics

Server Backend Latencies

3rd parties

Diagnostics

Heading Structure|Content hierarchy and heading tags

55 / 100

H1

ideal: 1

H2

ideal: 2+

H3

ideal: optional

H4

ideal: optional

Recommendations2

criticalMissing H1 tag

Add exactly one <h1> tag as the main heading

warningNo H2 tags found

Use H2 tags to structure your content sections

Structured Data|Schema markup, Open Graph and Twitter Cards

70 / 100

JSON-LD Schema

Not found

Open Graph

5 tags

Twitter Cards

4 tags

Microdata

Not found

Open Graph Tags

og:titleThe AI customer service company

og:descriptionFin is the leading AI Agent for customer service delivering the highest quality answers and handling the most complex queries. Employ Fin on any helpdesk or the Intercom Suite today.

og:imagehttps://www.intercom.com/intercom-marketing-site/img/social/default.jpg

og:urlhttps://www.intercom.com/

og:typewebsite

missing: og:site_namemissing: og:locale

Recommendations1

criticalNo JSON-LD structured data found

Add JSON-LD schema markup (e.g., WebPage, Organization, Article)

Image Optimization|Alt text, lazy loading and dimensions

100 / 100

Total Images

Missing Alt Text

100% have alt text

Missing Dimensions

Lazy Loaded

100%

1 of 1 images

Link Analysis|Internal, external and nofollow links

78 / 100

Total Links

Internal

8% of all links

External

92% of all links

Nofollow

Link Distribution

92% External

1 link with empty anchor text

External Links

www.intercom.comContact sales

app.intercom.comSign in

www.intercom.comView demo

app.intercom.comStart free trial

www.intercom.comContact sales

app.intercom.comSign in

www.intercom.comView demo

app.intercom.comStart free trial

www.intercom.comTerms

www.intercom.comPrivacy

+1 more

Recommendations2

warningOnly 1 internal links found

Add more internal links to improve crawlability

info1 links with empty anchor text

Add descriptive anchor text to links

Indexability|Robots, canonical and sitemap

90 / 100

Canonical URL

Set

https://www.intercom.com/

Noindex

Allowed

Robots.txt

Found

Sitemap

Found

https://intercom.com/sitemap.xml

Crawl Directives

Meta RobotsNot set

X-Robots-TagNot set

GooglebotNot set

NofollowNo — links followed

Canonicalhttps://www.intercom.com/

Page URLhttps://intercom.com

Recommendations1

warningCanonical points to a different domain

Verify this is intentional.

Content Structure|Content quality and semantic HTML

90 / 100

Word Count

4933

Paragraphs

All good length

Lists

Words per Heading

4933

Ideal: 100-300

Semantic HTML Elements1 sections

<main>

<nav>

Recommendations1

warningPoor content chunking (4933 words/heading)

Add more headings to break content into digestible chunks (aim for 150-200 words per section)

AI Readability|How easily AI models can process your content

65 / 100

Reading Level

Difficult

Moderately complex

Total Words

4933

Sentences

356

Avg Sentence Length

14 words

Vocabulary Richness

12%

584 unique words

Recommendations3

warningDifficult to read (Flesch: 49)

Break complex sentences. Aim for Flesch score 60+

infoLow vocabulary diversity

Use varied vocabulary to provide richer context for AI

infoFirst paragraph is too short for AI summarization

Make the first paragraph a comprehensive summary (30-50 words)

AI Citation Potential|How likely AI will quote your content

85 / 100

Named Entities

67% density

FAQ Patterns

No FAQ Schema

Citations

Lists & Tables

5 items, 0 tables

Top Named Entities

Intercom15Intercom Suite11Agent9Explore Intercom Suite8Explore Fin8Fin7Suite7Employ Fin6CardtextExplore4Hero Card4Suiteurlhttpswww2Finurlhttpsfin2This2FinclassNamegroupcard2Findestinationhttpsfin2SuitearialabelExplore2SuiteclassNamegroupcard2SuitedestinationsuiteselectorherocardsuitedivnullclassNamepointereventsnone2SuitedatatestidundefineddataichildtextrefnulldivnullclassNamemb2HelpdeskdivnullclassNamewfull2

Recommendations2

warningNo FAQ-style content detected

Add question-and-answer sections with heading questions (H2/H3 with "?")

infoNo source attribution detected

Add citations or "according to" attributions to increase credibility

Content Freshness|Date signals and cache headers

75 / 100

Date Signals

None

No date signals found on page

Cache Control

Not set

ETag

Not set

Date Signals

Last-Modified HeaderNot found

Published DateNot found

Modified DateNot found

Recommendations2

warningNo datePublished or dateModified in structured data

Add datePublished and dateModified to your JSON-LD schema.

infoNo date/time signals found anywhere on page

Add <time datetime="..."> elements or schema dates to help AI assess content freshness

Security Headers|HTTP security headers analysis

40 / 100

Content-Security-Policy

Prevents XSS and injection attacks

MISSING

Strict-Transport-Security

Forces HTTPS connections

max-age=63072000; includeSubDomains; preload

SET

X-Frame-Options

Prevents clickjacking attacks

MISSING

X-Content-Type-Options

Prevents MIME-type sniffing

MISSING

Referrer-Policy

Controls referrer information

MISSING

Permissions-Policy

Controls browser features

MISSING

Recommendations5

criticalMissing Content-Security-Policy header

Add Content-Security-Policy header to prevent XSS and data injection attacks

warningMissing X-Frame-Options header

Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking

warningMissing X-Content-Type-Options header

Add X-Content-Type-Options: nosniff to prevent MIME-type sniffing

infoMissing Referrer-Policy header

Add Referrer-Policy header (e.g., strict-origin-when-cross-origin)

Trust Signals|Essential trust-building pages

90 / 100

Contact Page

FOUND

A contact page builds trust with visitors and search engines

https://www.intercom.com/contact-sales

About Page

MISSING

An about page establishes credibility and expertise

FOUND

Required for compliance and builds user trust

https://www.intercom.com/legal/privacy

FOUND

Protects both the site owner and users

https://www.intercom.com/legal/terms-and-policies

Recommendations2

infoMissing trust pages: about

Consider adding links to: about

infoNo author attribution found

Add author information via schema markup or rel="author" for E-E-A-T signals

Tech Stack|5 technologies detected

75 / 100

Analytics2

💬

Intercom

Script signature

javascript

🛠️

Analytics

Script signature

javascript

Frameworks3

⚛️

React

Script signature

javascript

▲

Next.js

Script signature

javascript

📝

WordPress

Script signature

javascript

intercom.com SEO Analysis