Website review, no card needed

ExtraHop logo

extrahop.com website review

Visit site (opens in a new tab)Reviewed 27 October 202630 issues · 81 checks

This review found 30 issues worth fixing on extrahop.com, 8 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for ExtraHop

  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
2.8 s1.5 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.6 s
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.3 s
Aug 1, 20262.1 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
148 ms115 msMay 9Oct 24134 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026126 ms
May 16, 2026126 ms
May 23, 2026132 ms
May 30, 2026130 ms
Jun 6, 2026132 ms
Jun 13, 2026135 ms
Jun 20, 2026133 ms
Jun 27, 2026142 ms
Jul 4, 2026144 ms
Jul 11, 2026142 ms
Jul 18, 2026141 ms
Jul 25, 2026123 ms
Aug 1, 2026120 ms
Aug 8, 2026121 ms
Aug 15, 2026119 ms
Aug 22, 2026128 ms
Aug 29, 2026129 ms
Sep 5, 2026133 ms
Sep 12, 2026137 ms
Sep 19, 2026127 ms
Sep 26, 2026136 ms
Oct 3, 2026131 ms
Oct 10, 2026135 ms
Oct 17, 2026136 ms
Oct 24, 2026134 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 extrahop.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. extrahop.com at 0.5 s0.5 s
  2. extrahop.com at 1.1 s1.1 s
  3. extrahop.com at 1.6 s1.6 s
  4. extrahop.com at 2.2 s2.2 s
  5. extrahop.com at 2.7 s2.7 s
  6. extrahop.com at 3.3 s3.3 s
  7. extrahop.com at 3.8 s3.8 s
  8. extrahop.com at 4.4 s4.4 s

Speed

11 to fix50
  • Reduce unused JavaScript

    7.5 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.5 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Optanon and others), adding 1.7 MB and 962 ms of main-thread time.

  • Use efficient cache lifetimes

    900 ms · 237 KiB

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

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50 (desktop: 68). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 123 KiB

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

  • Render-blocking requests

    450 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Google Tag Manager adds 379 ms

    379 ms

    Google Tag Manager costs a phone 379 ms of main-thread work and 546 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.

  • Google CDN adds 287 ms

    287 ms

    Google CDN costs a phone 287 ms of main-thread work and 736 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.

  • Main-thread work: 3.1 s

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

  • Optanon adds 179 ms

    179 ms

    Optanon costs a phone 179 ms of main-thread work and 307 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.

  • 2,028 HTML elements

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

  • Legacy JavaScript

    150 ms · 39 KiB

    Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 12 long tasks on the main thread

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

  • Improve image delivery

    52 KiB

    2 images could be 52 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

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

  • First Contentful Paint: 9.9 s

    9.9 s

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

  • Largest Contentful Paint: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ExtraHop Logo”.

  • Time to Interactive: 19.6 s

    19.6 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Total Blocking Time: 288 ms

    288 ms

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +7%

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

6 checks passed
  • Real-user INP: 134 ms

    134 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 555 ms

    555 ms

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

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

    -33%

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

  • Cumulative Layout Shift: 0.038

    0.038

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

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 123 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 123 requests on a phone: scripts 2.2 MB (45), other files 476 KiB (25) and images 193 KiB (40). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

2 to fixGoogle 9597
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 123 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8591
  • Meta description is short (66 characters)

    Your meta description is only 66 characters: “Explore cutting-edge technology solutions for your business needs.”. 70 to 160 characters is enough to sell the click.

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 155 internal links, 40 external

    The homepage links to 155 pages on extrahop.com and 40 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Is your agentic SOC running on blind confidence or ground truth?”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Network visibility for the agentic enterprise — ExtraHop”.

  • Canonical URL set

    The canonical URL is https://www.extrahop.com/.

  • Structured data in place

    Structured data found: Organization, WebPage 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.extrahop.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.extrahop.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,784 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.extrahop.com/resources, whose canonical is https://www.extrahop.com/undefined/resources. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 65 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.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 9293
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://www.redditstatic.com/ads/pixel.js' violates the following Content Security Policy directive…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    9 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

  • 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 1,540 words of copy

    The homepage carries about 1,540 words of visible text.

2 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact Us”, “Get a Demo” and “Learn more”.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks, 3 customer or partner logos and 20 trust badges.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies (measured from a US location before any click).

  • 29 other companies contacted

    Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 extrahop.com, 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
Hosting
Vercel

Hiring

Hiring
23 open roles
Teams
Engineering (6), Sales - Sales Ops (4), Customer Support (2), Marketing (2)
Job board
greenhouse

Company

Employees
585
Founded
2007
Headquarters
Seattle

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on extrahop.com, including 19 speed issues, 3 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

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