Website review, no card needed
anomali.com website review
Visit site (opens in a new tab)Reviewed 29 October 202634 issues · 86 checks
This review found 34 issues worth fixing on anomali.com, 17 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.0 s |
| May 16, 2026 | 5.8 s |
| May 23, 2026 | 5.6 s |
| May 30, 2026 | 5.5 s |
| Jun 6, 2026 | 5.4 s |
| Jun 13, 2026 | 5.4 s |
| Jun 20, 2026 | 5.5 s |
| Jun 27, 2026 | 5.5 s |
| Jul 4, 2026 | 5.6 s |
| Jul 11, 2026 | 5.6 s |
| Jul 18, 2026 | 5.6 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.1 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.5 s |
| Oct 3, 2026 | 4.5 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.5 s |
| Oct 24, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 295 ms |
| May 16, 2026 | 303 ms |
| May 23, 2026 | 307 ms |
| May 30, 2026 | 316 ms |
| Jun 6, 2026 | 311 ms |
| Jun 13, 2026 | 313 ms |
| Jun 20, 2026 | 310 ms |
| Jun 27, 2026 | 292 ms |
| Jul 4, 2026 | 274 ms |
| Jul 11, 2026 | 269 ms |
| Jul 18, 2026 | 261 ms |
| Jul 25, 2026 | 270 ms |
| Aug 1, 2026 | 260 ms |
| Aug 8, 2026 | 256 ms |
| Aug 15, 2026 | 256 ms |
| Aug 22, 2026 | 252 ms |
| Aug 29, 2026 | 257 ms |
| Sep 5, 2026 | 260 ms |
| Sep 12, 2026 | 264 ms |
| Sep 19, 2026 | 274 ms |
| Sep 26, 2026 | 272 ms |
| Oct 3, 2026 | 275 ms |
| Oct 10, 2026 | 275 ms |
| Oct 17, 2026 | 272 ms |
| Oct 24, 2026 | 270 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
2.6 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Improve image delivery
1.6 s · 429 KiB5 images could be 429 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,754 HTML elements
The page has 3,754 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Wistia, Google Tag Manager and osano.com and others), adding 9.2 MB and 1.5 s of main-thread time.
Wistia adds 442 ms
442 msWistia costs a phone 442 ms of main-thread work and 7.7 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.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 558 KiBAbout 558 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 356 ms
356 msGoogle Tag Manager costs a phone 356 ms of main-thread work and 524 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 · 47 KiBAbout 47 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.
website-files.com adds 168 ms
168 mswebsite-files.com costs a phone 168 ms of main-thread work and 769 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 133 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
74 KiB10 files are served with short cache lifetimes, so returning visitors download them again (74 KiB).
Minify JavaScript
53 KiB53 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
38 KiB38 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 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: 23 ms
23 msYour server sent the HTML in 23 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.
Real-user LCP: 4.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AGENTIC SOC TURNS SECURITY DATA INTO GOVERNED DECISIONS”.
Time to Interactive: 18.4 s
18.4 sThe page becomes fully interactive after 18.4 s. Good is under 3.8 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
32 images without width and height
32 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 318 ms
318 msScripts block taps and scrolling for 318 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 295 ms to 270 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 165 ms
165 msReal visitors wait 165 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.
Real-user TTFB: 469 ms
469 msReal visitors wait 469 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.0 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.056
0.056The layout barely moves while loading (CLS 0.056, good is under 0.1).
Images and page weight
Page weight: 10.0 MB in 162 requests
10.0 MBYour homepage downloads 10.0 MB in 162 requests on a phone: media 7.4 MB (3), scripts 1.5 MB (44) and images 561 KiB (40). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
346 KiB1 image is downloaded at several times the size a phone draws it, for example 6ab1891a5900641b8223a150_thumbnail.png at 3,840 px wide, shown at 354 px. Resized copies would save about 346 KiB.
1 image in older formats
1 image (374 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 2.8 g of CO₂ per visit
2.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.82 g of CO₂e: 338.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 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 (34 elements)
All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
160 internal links, 10 external
The homepage links to 160 pages on anomali.com and 10 external pages.
8 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Anomali's Agentic SOC Platform unifies threat intelligence, decides with context, and takes governed action so security…”.
One H1 headline
Your main headline reads: “AGENTIC SOC TURNS SECURITY DATA INTO GOVERNED DECISIONS”.
Title: 59 characters
Your title is a healthy 59 characters: “Anomali | Agentic SOC Platform for Governed Security Action”.
Canonical URL set
The canonical URL is https://www.anomali.com/.
Structured data in place
Structured data found: Corporation.
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.anomali.com/sitemap.xml.
AI search readiness
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 (4,059 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.anomali.com/llms.txt (195 KiB, 396 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.anomali.com/old-home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.anomali.com/old-home all use the title “Anomali | Agentic SOC Platform for Governed Security Action”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without an H1
https://www.anomali.com/persona/soc has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.
4 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.
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 “Uncaught TypeError: Cannot read properties of undefined (reading 'textContent')”.
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
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.
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.
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,175 words of copy
The homepage carries about 1,175 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us” and “Join the Technology Partner Program”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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 Reddit Pixel (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
28 other companies contacted
Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) 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 anomali.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
- Analytics
- Google Tag Manager
- Hosting
- Webflow
Hiring
- Hiring
- 9 open roles
- Teams
- CSM (3), Field Sales (2), Inside Sales (1), Product Management (1)
- Job board
- lever
Company
- Employees
- 114
- Founded
- 2013
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on anomali.com, including 20 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.