Programmable

Website review, no card needed

adaptivesecurity.com logo

adaptivesecurity.com website review

Visit site (opens in a new tab)Reviewed 3 November 202618 issues · 95 checks

This review found 18 issues worth fixing on adaptivesecurity.com, 5 of them high impact, across 95 checks. The most urgent: 3,615 HTML elements. 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

Site score

89B

Closest competitors among SaaS websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.0 s1.7 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.7 s
Jun 6, 20262.9 s
Jun 13, 20262.7 s
Jun 20, 20262.6 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.7 s
Jul 18, 20262.6 s
Jul 25, 20262.4 s
Aug 1, 20262.1 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
330 ms106 msMay 16Oct 31304 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026159 ms
May 23, 2026155 ms
May 30, 2026155 ms
Jun 6, 2026153 ms
Jun 13, 2026150 ms
Jun 20, 2026145 ms
Jun 27, 2026143 ms
Jul 4, 2026140 ms
Jul 11, 2026143 ms
Jul 18, 2026154 ms
Jul 25, 2026162 ms
Aug 1, 2026172 ms
Aug 8, 2026132 ms
Aug 15, 2026162 ms
Aug 22, 2026193 ms
Aug 29, 2026210 ms
Sep 5, 2026288 ms
Sep 12, 2026257 ms
Sep 19, 2026233 ms
Sep 26, 2026198 ms
Oct 3, 2026210 ms
Oct 10, 2026237 ms
Oct 17, 2026268 ms
Oct 24, 2026288 ms
Oct 31, 2026304 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

www.adaptivesecurity.com (opens in a new tab)
Full-page screenshot of adaptivesecurity.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adaptivesecurity.com at 0.6 s0.6 s
  2. adaptivesecurity.com at 1.2 s1.2 s
  3. adaptivesecurity.com at 1.8 s1.8 s
  4. adaptivesecurity.com at 2.4 s2.4 s
  5. adaptivesecurity.com at 3.0 s3.0 s
  6. adaptivesecurity.com at 3.6 s3.6 s
  7. adaptivesecurity.com at 4.2 s4.2 s
  8. adaptivesecurity.com at 4.8 s4.8 s

adaptivesecurity.com does not allow embedding, so this is Google's rendering of the page.

Speed

4 to fix65

  • 3,615 HTML elements

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

  • Mobile performance score: 65

    65/100

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

  • Reduce unused JavaScript

    790 ms · 164 KiB

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

  • Improve image delivery

    200 ms · 399 KiB

    6 images could be 399 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • Render-blocking requests

    200 ms

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

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 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 third-party service on the page

    1 third-party service load with your homepage (sanity.io), adding 2 KiB and 0 ms of main-thread time.

2 checks passed

  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 715 ms of it running JavaScript. That is comfortably low.

  • Server response: 24 ms

    24 ms

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

Core Web Vitals

5 to fix100

  • Largest Contentful Paint: 8.2 s

    8.2 s

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

  • Time to Interactive: 8.4 s

    8.4 s

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

  • Speed Index: 6.3 s

    6.3 s

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

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

    +89%

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

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

9 checks passed

  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 163 ms

    163 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 728 ms

    728 ms

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

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

    -15%

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

  • Cumulative Layout Shift: 0.045

    0.045

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

  • Total Blocking Time: 87 ms

    87 ms

    Scripts block the page for only 87 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix97

  • An image on the first screen is lazy-loaded

    image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.5 g of CO₂ per visit

    0.48 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 58.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed

  • Page weight: 1.7 MB in 69 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 69 requests on a phone: images 681 KiB (24), scripts 618 KiB (29) and fonts 198 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 10096

  • 5 text elements with low contrast

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

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

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

  • 55 links without text

    55 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed

  • Every image has alt text

    All 157 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Protect Against Deepfakes and AI-Powered Attacks | Adaptive Security”.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 140 internal links, 14 external

    The homepage links to 140 pages on adaptivesecurity.com and 14 external pages.

7 checks passed

  • Meta description: 141 characters

    Your meta description is 141 characters: “Human security for the AI era. Adaptive unifies security awareness training, phishing simulations, agentic email securi…”.

  • One H1 headline

    Your main headline reads: “Protect your workforce from AI threats.”.

  • Canonical URL set

    The canonical URL is https://www.adaptivesecurity.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.adaptivesecurity.com/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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (172 KiB, 1,331 links), a plain-text guide to the site for AI tools.

Other pages

100

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.

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

  • 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

Google 100100

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    13 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

8 checks passed

  • Served over HTTPS

    The homepage is served over HTTPS (adaptivesecurity.com).

  • Valid certificate (37 days left)

    The certificate from Let's Encrypt · YR1 verifies for adaptivesecurity.com and is valid for another 37 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://adaptivesecurity.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 47 links work

    All 47 links checked from your homepage (40 internal, 7 external) answered without errors.

Domain and trust

  • DNSSEC is off

    adaptivesecurity.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

3 checks passed

  • Domain is 23 years old

    23 years

    adaptivesecurity.com was registered in Oct 2003 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only pki.goog, sectigo.com, globalsign.com and letsencrypt.org to issue certificates for adaptivesecurity.com, so a mis-issued certificate from anyone else is refused.

  • Registered until Oct 2028

    adaptivesecurity.com is registered until Oct 2028.

Content and conversion

3 to fix79

  • 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 analytics detected

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

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

  • 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 463 words of copy

    The homepage carries about 463 words of visible text.

4 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Pricing” and “Book a demo”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Pricing”, “Book a demoBook a demo” and “Book a demo”.

  • Social proof on the page

    Social proof on the homepage: 12 customer or partner logos, a star rating, 40 trust badges and “over 2,000 customers”.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Email authentication

100

  • Email authentication score: 100/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed

  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:_spf.google.com include:sendgrid.net include:241914077.spf02.hubspotemail.net include:_spf.sendergen.com…”.

  • DKIM signing found

    A DKIM key is published (selector “google” and “k2”), so receivers can verify mail really came from you.

Privacy and tracking

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 1 other company contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
Next.js
Hosting
Vercel

Hiring

Hiring
8 open roles
Teams
Customer Success (3), Sales (3), Engineering (2)
Job board
ashby
Careers page
www.adaptivesecurity.com/careers (opens in a new tab)

Company

Employees
300
Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on adaptivesecurity.com, including 9 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

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