Website review, no card needed
hubspot.com website review
Visit site (opens in a new tab)Reviewed 18 November 202635 issues · 85 checks
This review found 35 issues worth fixing on hubspot.com, 11 of them high impact, across 85 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for HubSpot
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.9 s |
| Nov 7, 2026 | 2.7 s |
| Nov 14, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 278 ms |
| Jun 6, 2026 | 283 ms |
| Jun 13, 2026 | 287 ms |
| Jun 20, 2026 | 289 ms |
| Jun 27, 2026 | 294 ms |
| Jul 4, 2026 | 298 ms |
| Jul 11, 2026 | 300 ms |
| Jul 18, 2026 | 297 ms |
| Jul 25, 2026 | 296 ms |
| Aug 1, 2026 | 298 ms |
| Aug 8, 2026 | 308 ms |
| Aug 15, 2026 | 311 ms |
| Aug 22, 2026 | 312 ms |
| Aug 29, 2026 | 315 ms |
| Sep 5, 2026 | 318 ms |
| Sep 12, 2026 | 322 ms |
| Sep 19, 2026 | 323 ms |
| Sep 26, 2026 | 325 ms |
| Oct 3, 2026 | 325 ms |
| Oct 10, 2026 | 313 ms |
| Oct 17, 2026 | 308 ms |
| Oct 24, 2026 | 306 ms |
| Oct 31, 2026 | 307 ms |
| Nov 7, 2026 | 306 ms |
| Nov 14, 2026 | 311 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
4.2 s
8.4 s
12.5 s
16.7 s
20.9 s
25.1 s
29.3 s
33.4 s
Speed
Render-blocking requests
1.2 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 9.9 s
A phone's processor spends 9.9 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and greencolumnart.com and others), adding 2.2 MB and 1.6 s of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
767 KiBAbout 767 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
150 ms · 581 KiB112 files are served with short cache lifetimes, so returning visitors download them again (581 KiB).
hsappstatic.net adds 561 ms
561 mshsappstatic.net costs a phone 561 ms of main-thread work and 1.2 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Google Tag Manager adds 552 ms
552 msGoogle Tag Manager costs a phone 552 ms of main-thread work and 644 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 350 ms. During a long task the page ignores taps.
2,910 HTML elements
The page has 2,910 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need.
Reduce unused CSS
17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 26.1 s
26.1 sThe page becomes fully interactive after 26.1 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 329 ms
329 msReal visitors wait 329 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.24
0.24For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.201
0.201The layout shifts by 0.201 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AI knows the world. HubSpot knows your world. We bring the …”. Most of its time is element render delay (1.6 s).
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 278 ms to 311 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user TTFB: 717 ms
717 msReal visitors wait 717 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.8 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 4.6 MB in 285 requests
4.6 MBYour homepage downloads 4.6 MB in 285 requests on a phone: scripts 2.6 MB (82), media 743 KiB (6) and fonts 539 KiB (17). Under 2 MB keeps phones on slow connections fast.
About 1.3 g of CO₂ per visit
1.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.30 g of CO₂e: 155.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 94 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization, Product, WebPage and WebSite) but with 1 problem, for example “Product: no offers (price) block”.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
161 internal links, 66 external
The homepage links to 161 pages on hubspot.com and 66 external pages.
7 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “HubSpot's customer platform includes all the marketing, sales, customer service, and CRM software you need to grow your…”.
One H1 headline
Your main headline reads: “Introducing the Customer Relationship Harness”.
Title: 55 characters
Your title is a healthy 55 characters: “HubSpot | Software & Tools for your Business - Homepage”.
Canonical URL set
The canonical URL is https://www.hubspot.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.hubspot.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,159 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.hubspot.com/llms.txt (35 KiB, 225 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.hubspot.com/company/contact has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.hubspot.com/company/management has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://sca-1113-adswizz.attribution.adswizz.com/fire?pixelId=8000fe70-c5b5-41f6-adb3-32183985eb54&type=sitevisit&subtype=Sitewide&aw_0_req.gdpr=true.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
32 of 34 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 977 words of copy
The homepage carries about 977 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get a demo of HubSpot's premium software”.
25 calls to action
The homepage has 25 calls to action, for example “Contact Sales”, “Contact Us” and “Get a demo of HubSpot's premium software”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 90 testimonial or review blocks, 1 customer or partner logo, a star rating, 9 trust badges and “TRUSTED BY 311,000+ CUSTOMERS”.
Analytics in place
Analytics detected: Google Tag Manager, HubSpot and Cloudflare Web Analytics.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
34 cookies set on arrival
34Opening the homepage sets 34 cookies, 11 of them by other companies (measured from a US location before any click).
51 other companies contacted
Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at hubspot.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- HubSpot CMS
- Analytics
- Google Tag Manager
Company
- Employees
- 8,246
- Founded
- 2006
- Headquarters
- Cambridge
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on hubspot.com, including 20 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.