Website review, no card needed
binalyze.com website review
Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 85 checks
This review found 39 issues worth fixing on binalyze.com, 18 of them high impact, across 85 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 125 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 114 ms |
| Oct 24, 2026 | 111 ms |
| Oct 31, 2026 | 118 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
Speed
Improve image delivery
5.2 s · 2.8 MB9 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.2 s faster on a phone.
Reduce unused JavaScript
1.7 s · 339 KiBAbout 339 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Render-blocking requests
1.6 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Use efficient cache lifetimes
1.0 s · 171 KiB8 files are served with short cache lifetimes, so returning visitors download them again (171 KiB).
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
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 876 KiB and 635 ms of main-thread time.
Google Tag Manager adds 496 ms
496 msGoogle Tag Manager costs a phone 496 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
300 ms · 42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,763 HTML elements
The page has 2,763 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 226 ms. During a long task the page ignores taps.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
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: 90 ms
90 msYour server sent the HTML in 90 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 32.9 s
32.9 sYour largest element takes 32.9 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.”.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 34.2 s
34.2 sThe page becomes fully interactive after 34.2 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
56 images without width and height
56 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 465 ms
465 msScripts block taps and scrolling for 465 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 120 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 50.6 MB in 117 requests
50.6 MBYour homepage downloads 50.6 MB in 117 requests on a phone: media 42.1 MB (11), images 7.3 MB (56) and scripts 895 KiB (21). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.0 MB3 images are downloaded at several times the size a phone draws them, for example Air-hero-thumbnail-2.png at 1,440 px wide, shown at 285 px. Resized copies would save about 1.0 MB.
9 images below the first screen load straight away
9 images further down the page (2.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (641 KiB) are 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 14.3 g of CO₂ per visit
14.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 14.34 g of CO₂e: 1720.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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 (31 elements)
All page content should be contained by landmarks: 31 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.
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
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
203 internal links, 36 external
The homepage links to 203 pages on binalyze.com 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 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://binalyze.ai/sitemap_index.xml.
AI search readiness
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,447 words), so crawlers that don't run JavaScript still read it.
Other pages
8 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 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://binalyze.ai/use-case/incident-response took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 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
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.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 970 words of copy
The homepage carries about 970 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
4Before 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
1Opening 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.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 1 open role
- Teams
- Sales (1)
- Job board
- ashby
- Careers page
- binalyze.ai/join-the-team (opens in a new tab)
Company
- Headquarters
- Syosset
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on binalyze.com, including 20 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.