Website review, no card needed

getastra.com logo

getastra.com website review

Visit site (opens in a new tab)Reviewed 23 October 202629 issues · 79 checks

This review found 29 issues worth fixing on getastra.com, 14 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
3.9 s2.2 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.7 s
May 9, 20263.6 s
May 16, 20263.6 s
May 23, 20263.6 s
May 30, 20263.4 s
Jun 6, 20263.3 s
Jun 13, 20263.2 s
Jun 20, 20262.9 s
Jun 27, 20262.8 s
Jul 4, 20262.7 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.6 s
Aug 1, 20262.7 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
191 ms139 msMay 2Oct 17160 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026185 ms
May 9, 2026175 ms
May 16, 2026169 ms
May 23, 2026172 ms
May 30, 2026161 ms
Jun 6, 2026159 ms
Jun 13, 2026159 ms
Jun 20, 2026164 ms
Jun 27, 2026172 ms
Jul 4, 2026173 ms
Jul 11, 2026176 ms
Jul 18, 2026166 ms
Jul 25, 2026159 ms
Aug 1, 2026157 ms
Aug 8, 2026158 ms
Aug 15, 2026154 ms
Aug 22, 2026158 ms
Aug 29, 2026152 ms
Sep 5, 2026149 ms
Sep 12, 2026151 ms
Sep 19, 2026145 ms
Sep 26, 2026152 ms
Oct 3, 2026147 ms
Oct 10, 2026154 ms
Oct 17, 2026160 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 getastra.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. getastra.com at 0.7 s0.7 s
  2. getastra.com at 1.4 s1.4 s
  3. getastra.com at 2.1 s2.1 s
  4. getastra.com at 2.8 s2.8 s
  5. getastra.com at 3.5 s3.5 s
  6. getastra.com at 4.1 s4.1 s
  7. getastra.com at 4.8 s4.8 s
  8. getastra.com at 5.5 s5.5 s

Speed

11 to fix43
  • Use efficient cache lifetimes

    2.3 s · 8.0 MB

    36 files are served with short cache lifetimes, so returning visitors download them again (8.0 MB).

  • Render-blocking requests

    5.2 s

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

  • Reduce unused JavaScript

    2.5 s · 545 KiB

    About 545 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Reduce unused CSS

    1.1 s · 225 KiB

    About 225 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 2.6 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 (website-files.com, Google Tag Manager and webability.io and others), adding 10.5 MB and 1.5 s of main-thread time.

  • website-files.com adds 699 ms

    699 ms

    website-files.com costs a phone 699 ms of main-thread work and 9.4 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 354 ms

    354 ms

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

  • Legacy JavaScript

    300 ms · 86 KiB

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

  • 1,944 HTML elements

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

  • 13 long tasks on the main thread

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

  • Improve image delivery

    215 KiB

    14 images could be 215 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.

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

    18 ms

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

Core Web Vitals

9 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: 8.5 s

    8.5 s

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

  • Largest Contentful Paint: 23.6 s

    23.6 s

    Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Security conscious companies trust Astra for continuous pen…”.

  • Time to Interactive: 24.0 s

    24.0 s

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

  • Speed Index: 12.0 s

    12.0 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 498 ms

    498 ms

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

5 checks passed
  • Real-user INP: 153 ms

    153 ms

    Real visitors wait 153 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.

  • Tap response (INP) got 13% faster for real visitors

    -13%

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

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

    -32%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.7 s to 2.4 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

2 to fix64
  • Page weight: 11.7 MB in 171 requests

    11.7 MB

    Your homepage downloads 11.7 MB in 171 requests on a phone: media 7.6 MB (4), scripts 1.9 MB (59) and images 767 KiB (45). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    675bc32c7ffd1103973014d1_STB_0951-scaled-e1728908187243-p-50 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).

  • 1 image in older formats

    1 image (30 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 3.3 g of CO₂ per visit

    3.31 g

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

1 checks passed
  • 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 9296
  • 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.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 156 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9295
  • Meta description is long (166 characters)

    Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 114 internal links, 12 external

    The homepage links to 114 pages on getastra.com and 12 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Security conscious companies trust Astra for continuous pentests.”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Astra Security - AI Powered Continuous Pentest Platform”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Corporation and VideoObject.

  • 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.getastra.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,727 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.getastra.com/llms.txt (18 KiB, 14 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 62 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

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56312869&tm=gtm002&Ver=2&mid=9996f9d5-6cbb-4b33-bbbc-239c18e5fae0&bo=1&sid=1959d270cf2511f1a6962bb91c14bd97&vid=1959ea10cf2511f19299a59650516a60&vids=1&msclkid=N&pi=91.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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,681 words of copy

    The homepage carries about 1,681 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: “Talk to us” and “Get started now”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Pricing”, “Get a personalized demo” and “Talk to us”.

  • Social proof on the page

    Social proof on the homepage: 89 testimonial or review blocks, 58 customer or partner logos and 6 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, HubSpot and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, LinkedIn Insight and Meta Pixel and 4 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.

  • 22 cookies set on arrival

    22

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

  • 59 other companies contacted

    Loading the homepage contacts 59 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 getastra.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
Webflow
Framework
jQuery
Analytics
Google Tag Manager | Segment

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 getastra.com, including 20 speed issues and 1 SEO issue. 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