Public audit / not a customer

Discover What the Audit Engine Found on hubspot.com

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

Score

7/10

Grade

B

Findings

5

Audited

August 4, 2026

Same engine, public URL

Disclosure: HubSpot 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. HubSpot may update their page at any time; this reflects a snapshot taken August 4, 2026.

Page snapshot · August 4, 2026

hubspot.com
HubSpot landing page snapshot - August 4, 2026

Five 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

H1 / Title Misalignment

Priority 2/10Quick Win

H1 and title tag share no significant keywords - messaging misalignment. The title is "HubSpot | Software & Tools for your Business - Homepage" - the "- Homepage" suffix is a template placeholder that shipped to production. The static H1 reads "Where go-to-market teams go to grow scale close retain grow" - keyword-stacked, with "grow" appearing twice.

Evidence

title: "HubSpot | Software & Tools for your Business - Homepage" (55 chars) | meta desc: 129 chars | h1: "Where go-to-market teams go to grow scale close retain grow" (69 chars) | h1 count: 1. Snapshot timestamp: 2026-08-04T13:02:44Z.

Recommended Fix

Write a 30-60 char title without the template suffix, and one descriptive H1 that shares its primary keyword with the title. Example title: "HubSpot - CRM, Marketing, Sales & Service Software".

Finding 2

Static H1 Differs From Rendered H1

Priority 3.5/10Major Project

The static HTML H1 ("Where go-to-market teams go to grow scale close retain grow") is not the headline rendered in a browser ("Where go-to-market teams go to scale."). Search engines and non-JS crawlers index the keyword-stacked static version; human visitors see a different message. The page is effectively running two headlines for two audiences.

Evidence

Rendered hero H1 (Playwright screenshot, 2026-08-04): "Where go-to-market teams go to scale." Static source H1: "Where go-to-market teams go to grow scale close retain grow". Both served on the same URL.

Recommended Fix

Serve one H1 in the initial HTML that matches the rendered headline. If this is an A/B test, move it to server-side or edge-level testing so Googlebot receives the same variant as visitors.

Finding 3

Page Payload

Priority 2.5/10Major Project

HTML payload is 608.5 KiB - 5x the 120KB heuristic for a marketing page. Excessive HTML inflates parse time and delays first paint for every visitor, including the millions of paid visits HubSpot runs to this URL.

Evidence

Fetched HTML payload: 608.5 KiB. Heuristic max: ~120 KiB. Delta: +488.5 KiB above ceiling. Snapshot timestamp: 2026-08-04T13:02:44Z.

Recommended Fix

Audit server-rendered blocks. Defer below-fold content, move inline JSON data to lazy-loaded API calls, and target Lighthouse mobile performance >= 70.

Finding 4

Above-Fold Source Proxy

Priority 2.5/10Quick Win

Early source proxy has a headline but no clickable control in the first 3,000 characters. Rendered hero does show CTAs ("Get a demo", "Get started free") - but the source order does not reflect the visual hierarchy.

Evidence

Early HTML proxy missing: H1 headline, primary CTA, price/offer signal together in first 3,000 source chars. Rendered hero (Playwright): headline + 2 CTAs present. Snapshot timestamp: 2026-08-04T13:02:44Z.

Recommended Fix

Ensure the first 3,000 source characters contain the H1, primary CTA, and a value signal so crawlers and non-JS readers see the same hierarchy as rendered visitors.

Finding 5

Ad Tracking Not Observed in Static Source

Priority 4/10Major Project

No recognized ad-tracking artifact observed in fetched source HTML; runtime/server-side tracking remains unverified. For a page running massive paid campaigns, the static source provides no evidence that conversion events are configured on the public document.

Evidence

Not observed: Facebook Pixel initializer, GA4 initializer or measurement ID, UTM-bearing link, explicit conversion call. Snapshot timestamp: 2026-08-04T13:02:44Z.

Recommended Fix

Run consent-aware browser/network validation and confirm the paid click-to-landing-to-conversion event path. Add only tracking artifacts proven absent.

What This Demonstrates

HubSpot sells marketing, sales, and service software - to teams whose job is making pages like this convert. The engine scores the page 7.0/B: strong trust signals, clear CTAs. What the source reveals is maintenance debt at the top of the funnel: the <title> ends in "- Homepage" (a template placeholder), the H1 and title share no significant keyword, and the static H1 that search engines index ("Where go-to-market teams go to grow scale close retain grow") differs from the rendered headline human visitors see ("Where go-to-market teams go to scale."). For a company that markets growth software, the page that receives millions of paid visits a month does not tell search engines and visitors the same story.

Work at HubSpot? 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.