Website review, no card needed

apollo.io logo

apollo.io website review

Visit site (opens in a new tab)Reviewed 18 November 202629 issues · 83 checks

This review found 29 issues worth fixing on apollo.io, 8 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.9 s2.0 sMay 30Nov 142.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.4 s
Jun 6, 20264.6 s
Jun 13, 20264.6 s
Jun 20, 20264.5 s
Jun 27, 20264.1 s
Jul 4, 20263.8 s
Jul 11, 20263.7 s
Jul 18, 20263.6 s
Jul 25, 20263.7 s
Aug 1, 20264.3 s
Aug 8, 20264.7 s
Aug 15, 20264.9 s
Aug 22, 20265.1 s
Aug 29, 20265.2 s
Sep 5, 20265.3 s
Sep 12, 20265.4 s
Sep 19, 20265.4 s
Sep 26, 20265.4 s
Oct 3, 20265.4 s
Oct 10, 20264.8 s
Oct 17, 20264.3 s
Oct 24, 20263.8 s
Oct 31, 20262.7 s
Nov 7, 20262.6 s
Nov 14, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
415 ms270 msMay 30Nov 14398 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026314 ms
Jun 6, 2026326 ms
Jun 13, 2026340 ms
Jun 20, 2026339 ms
Jun 27, 2026317 ms
Jul 4, 2026305 ms
Jul 11, 2026304 ms
Jul 18, 2026296 ms
Jul 25, 2026287 ms
Aug 1, 2026288 ms
Aug 8, 2026300 ms
Aug 15, 2026328 ms
Aug 22, 2026372 ms
Aug 29, 2026381 ms
Sep 5, 2026380 ms
Sep 12, 2026379 ms
Sep 19, 2026377 ms
Sep 26, 2026371 ms
Oct 3, 2026369 ms
Oct 10, 2026372 ms
Oct 17, 2026383 ms
Oct 24, 2026378 ms
Oct 31, 2026387 ms
Nov 7, 2026395 ms
Nov 14, 2026398 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

Full-page screenshot of apollo.io (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apollo.io at 0.4 s0.4 s
  2. apollo.io at 0.8 s0.8 s
  3. apollo.io at 1.1 s1.1 s
  4. apollo.io at 1.5 s1.5 s
  5. apollo.io at 1.9 s1.9 s
  6. apollo.io at 2.3 s2.3 s
  7. apollo.io at 2.6 s2.6 s
  8. apollo.io at 3.0 s3.0 s

Speed

6 to fix74
  • Render-blocking requests

    1.1 s

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    150 ms · 814 KiB

    About 814 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    450 ms · 272 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (272 KiB).

  • Main-thread work: 3.9 s

    A phone's processor spends 3.9 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 2,053 HTML elements

    The page has 2,053 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 7 third-party services on the page

    7 third-party services load with your homepage (transcend-cdn.com, Intercom and Hubspot and others), adding 751 KiB and 435 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

  • 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: 54 ms

    54 ms

    Your server sent the HTML in 54 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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.

  • Time to Interactive: 19.3 s

    19.3 s

    The page becomes fully interactive after 19.3 s. Good is under 3.8 s.

  • Speed Index: 8.2 s

    8.2 s

    Visually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.

  • Real-user INP: 402 ms

    402 ms

    Real visitors wait 402 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 24% slower for real visitors

    +24%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 314 ms to 398 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 895 ms

    895 ms

    Real visitors wait 895 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.8 s

    2.8 s

    The first text or image appears after 2.8 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 393 ms

    393 ms

    Scripts block taps and scrolling for 393 ms in total while the page loads. Good is under 200 ms.

  • Largest Contentful Paint: 2.8 s

    2.8 s

    Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Grow revenue with one connected GTM system”. Most of its time is element render delay (2.3 s).

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 43% faster for real visitors

    -43%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.4 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 4.1 MB in 148 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 148 requests on a phone: scripts 2.2 MB (76), media 759 KiB (1) and fonts 656 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.16 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.16 g of CO₂e: 138.7 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

7 to fixGoogle 7990
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (66 elements)

    All page content should be contained by landmarks: 66 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Headings skip levels

    Headings skip levels (h1 → h6, h4 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 195 internal links, 19 external

    The homepage links to 195 pages on apollo.io and 19 external pages.

8 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Apollo is the AI sales platform rebuilt as one connected AI GTM system: data, intelligence, and execution for the entir…”.

  • One H1 headline

    Your main headline reads: “Grow revenue with one connected GTM system”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “The AI GTM System for Go-to-Market Teams | Apollo”.

  • Canonical URL set

    The canonical URL is https://www.apollo.io/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.apollo.io/sitemap.xml.

AI search readiness

100
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 (1,391 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.apollo.io/llms.txt (37 KiB, 206 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 2 pages without an H1

    https://www.apollo.io/product/integrations and https://www.apollo.io/ai/assistant have 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 75 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    67 of 76 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,147 words of copy

    The homepage carries about 1,147 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: “Sign up for free” and “Get a front row seat, from anywhere.”.

  • 38 calls to action

    The homepage has 38 calls to action, for example “Get a front row seat, from anywhere.”, “Join the Community” and “Pricing”.

  • Social proof on the page

    Social proof on the homepage: a star rating, 2 trust badges and “30M companies”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Amplitude.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 11 trackers load before any consent

    11

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 6 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.

  • 32 cookies set on arrival

    32

    Opening the homepage sets 32 cookies, 3 of them by other companies (measured from a US location before any click).

  • 48 other companies contacted

    Loading the homepage contacts 48 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 apollo.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager | Amplitude
Hosting
Netlify

Hiring

Hiring
46 open roles
Teams
All GH (46)
Job board
ashby

Company

Founded
2015
Headquarters
San Francisco

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on apollo.io, including 16 speed 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25