Website review, no card needed

binalyze.ai logo

binalyze.ai website review

Visit site (opens in a new tab)Reviewed 23 October 202636 issues · 81 checks

This review found 36 issues worth fixing on binalyze.ai, 17 of them high impact, across 81 checks. The most urgent: page weight: 37.3 MB in 105 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
3.6 s2.7 sAug 1Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Aug 22, 20263.4 s
Aug 29, 20263.2 s
Sep 5, 20263.1 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
127 ms110 msAug 8Oct 17114 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026120 ms
Aug 15, 2026124 ms
Aug 22, 2026112 ms
Aug 29, 2026112 ms
Sep 5, 2026113 ms
Sep 12, 2026113 ms
Sep 19, 2026125 ms
Sep 26, 2026123 ms
Oct 3, 2026113 ms
Oct 10, 2026115 ms
Oct 17, 2026114 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 binalyze.ai (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. binalyze.ai at 0.5 s0.5 s
  2. binalyze.ai at 0.9 s0.9 s
  3. binalyze.ai at 1.4 s1.4 s
  4. binalyze.ai at 1.9 s1.9 s
  5. binalyze.ai at 2.4 s2.4 s
  6. binalyze.ai at 2.8 s2.8 s
  7. binalyze.ai at 3.3 s3.3 s
  8. binalyze.ai at 3.8 s3.8 s

Speed

11 to fix34
  • Reduce unused JavaScript

    1.4 s · 284 KiB

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

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 4.2 s

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

  • Improve image delivery

    3.5 MB

    9 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Hubspot and Macropod BugHerd and others), adding 827 KiB and 889 ms of main-thread time.

  • Render-blocking requests

    900 ms

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

  • Use efficient cache lifetimes

    650 ms · 141 KiB

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

  • Google Tag Manager adds 666 ms

    666 ms

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

  • Reduce unused CSS

    450 ms · 42 KiB

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

  • 10 long tasks on the main thread

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

  • 2,973 HTML elements

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

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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: 49 ms

    49 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 33.5 s

    33.5 s

    Your largest element takes 33.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “YOUR SOC DETECTS THREATS. BINALYZE REVEALS THE TRUTH.”.

  • Time to Interactive: 35.3 s

    35.3 s

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

  • First Contentful Paint: 7.1 s

    7.1 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • 61 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

3 checks passed
  • 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 17% faster for real visitors

    -17%

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

4 to fix28
  • Page weight: 37.3 MB in 105 requests

    37.3 MB

    Your homepage downloads 37.3 MB in 105 requests on a phone: media 28.1 MB (6), images 7.9 MB (54) and scripts 843 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 4.3 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    1.9 MB

    5 images are downloaded at several times the size a phone draws them, for example hero_static.webp at 2,124 px wide, shown at 310 px. Resized copies would save about 1.9 MB.

  • 13 images below the first screen load straight away

    13 images further down the page (3.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 10.6 g of CO₂ per visit

    10.56 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8990
  • ARIA toggle fields must have an accessible name (2 elements)

    ARIA toggle fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

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

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

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 8595
  • 16 links crawlers can't follow

    16 links have no real href, so search engines can't follow them.

  • 5 links with vague text

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

  • 198 internal links, 36 external

    The homepage links to 198 pages on binalyze.ai and 36 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Extend your SOC beyond threat detection, you don't need more noise. Binalyze AIR turns complex alerts and signals into …”.

  • One H1 headline

    Your main headline reads: “Your SOC detects threats. Binalyze reveals the truth.”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Automated Cyber Investigation Platform | Binalyze AIR”.

  • Canonical URL set

    The canonical URL is https://binalyze.ai/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, Place and WebPage.

  • 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://binalyze.ai/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://binalyze.ai/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.

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 9 pages without a meta description

    https://binalyze.ai/use-case/alert-triage-investigation, https://binalyze.ai/use-case/threat-hunting-proactive-investigations, https://binalyze.ai/use-case/incident-response, https://binalyze.ai/use-case/compliance, https://binalyze.ai/use-case/ediscovery-digital-forensic-discovery and https://binalyze.ai/persona/soc-teams and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

  • 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

2 to fixGoogle 9291
  • 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”.

  • 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 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,065 words of copy

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

3 checks passed
  • 25 calls to action

    The homepage has 25 calls to action, for example “Get A Free Trial”, “Get Free Trial” and “Join The Team”.

  • Social proof on the page

    Social proof on the homepage: 19 testimonial or review blocks, 9 customer or partner logos and 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 19 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager

Hiring

Hiring
1 open role
Teams
Sales (1)
Job board
ashby

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on binalyze.ai, including 19 speed issues, 2 SEO issues and 2 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