Public audit / not a customer

Discover What the Audit Engine Found on intercom.com

Nebula ran its evidence-backed audit on intercom.com on August 5, 2026. Intercom is not a Nebula customer. This page shows the raw output of the same engine every free scan uses - 3 findings, evidence included.

Get your free audit →Explore $97 Repair Sprint

Score

6.9/10

Grade

Findings

Audited

August 5, 2026

Same engine, public URL

Disclosure: Intercom did not request this audit and is not affiliated with Nebula Components. This teardown is published to demonstrate what the audit engine produces on a real, well-known page - not to imply any commercial relationship. All findings are evidence-backed; source, selector, and confidence are included per finding. Intercom may update their page at any time; this reflects a snapshot taken August 5, 2026.

Page snapshot · August 5, 2026

intercom.com

Three Findings

Ranked by observable priority. Each finding includes the evidence Nebula used - no opinion, no estimation. Priority scores are rule-based heuristics for fix order, not predicted conversion loss.

Finding 1

Page Payload

Priority 2.5/10Major Project

HTML payload is 1,528.4 KiB - 12.7x the 120KB heuristic and the second-heaviest in our dataset. First paint waits on a megabyte and a half of markup.

Evidence

Fetched HTML payload: 1528.4 KiB. Heuristic max: ~120 KiB. Snapshot timestamp: 2026-08-05T09:40Z.

Recommended Fix

Stream above-fold HTML first; split server components; move inline state to lazy API calls. Target Lighthouse mobile >= 70.

Finding 2

No Tracking Artifacts in Static Source

Priority 4/10Major Project

No recognized ad-tracking artifact observed in the fetched source at all - no GA4, no pixel, no UTM links, no conversion call. For a company selling measurement-heavy CX software, the static document carries nothing measurable.

Evidence

Static artifacts present: none. Not observed: Facebook Pixel initializer, GA4 initializer or measurement ID, UTM-bearing link, explicit conversion call. Snapshot timestamp: 2026-08-05T09:40Z.

Recommended Fix

Confirm the real tracking path via consent-aware network validation; ensure at minimum the analytics initializer exists in the served document.

Finding 3

Above-Fold Source Proxy

Priority 4/10Quick Win

Early source proxy lacks a headline, clickable control, or offer term in its first 3,000 characters - the entire hero is client-rendered.

Evidence

Early HTML proxy missing: H1 headline, primary CTA, price/offer signal in first 3,000 source chars. Snapshot timestamp: 2026-08-05T09:40Z.

Recommended Fix

Server-render H1 + primary CTA + offer signal into the first 3,000 characters.

What This Demonstrates

Intercom sells customer service AI - a product whose buyers measure everything. Its own homepage ships 1,528.4 KiB of HTML (12.7x the heuristic ceiling, second only to Figma in our dataset) and the static source contains no recognized ad-tracking artifact at all: no GA4, no pixel, no UTM-bearing link, no conversion call. The measurement company's page is unmeasurable from the outside. The engine scores it 6.9/B - the above-fold hierarchy is entirely client-rendered, invisible to any client that does not execute the app bundle.

Work at Intercom? Verify ownership to manage this teardown in your workspace.

Claim this teardown

See what it finds on your page

Same engine, your URL. Free, no signup. Results in under two minutes.

Find the Leak →

Already know your page has issues? Skip the audit.

Fix one leak now, $97 →

One finding. 48h delivery. No call, no retainer.