Website review, no card needed
anonasecurity.com website review
Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 88 checks
This review found 37 issues worth fixing on anonasecurity.com, 8 of them high impact, across 88 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
84B- #21,209 of 117,615 reviewed websitesbeats 77%
- #13,814 of 66,923 online storesbeats 73%
- #13,412 of 61,018 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 96 ms |
| May 23, 2026 | 98 ms |
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 114 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 114 ms |
| Sep 5, 2026 | 116 ms |
| Sep 12, 2026 | 118 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 116 ms |
| Oct 3, 2026 | 115 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 113 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.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.3 s
5.0 s
Speed
Render-blocking requests
1.0 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Main-thread work: 5.9 s
A phone's processor spends 5.9 s on main-thread work while loading, 3.2 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 (Google Tag Manager, reddit and cloudfront.net and others), adding 2.1 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
750 ms · 807 KiBAbout 807 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
600 ms · 216 KiB4 images could be 216 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 648 ms
648 msGoogle Tag Manager costs a phone 648 ms of main-thread work and 678 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.
reddit adds 610 ms
610 msreddit costs a phone 610 ms of main-thread work and 35 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.
cloudfront.net adds 365 ms
365 mscloudfront.net costs a phone 365 ms of main-thread work and 460 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 264 ms. During a long task the page ignores taps.
Shopify adds 219 ms
219 msShopify costs a phone 219 ms of main-thread work and 450 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.
1,763 HTML elements
The page has 1,763 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 100 KiBAbout 100 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 95 KiB14 files are served with short cache lifetimes, so returning visitors download them again (95 KiB).
Legacy JavaScript
69 KiBPolyfills for old browsers add 69 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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 22.5 s
22.5 sThe page becomes fully interactive after 22.5 s. Good is under 3.8 s.
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 940 ms
940 msScripts block taps and scrolling for 940 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 96 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 109 ms
109 msReal visitors wait 109 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 FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 583 ms
583 msReal visitors wait 583 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 327 requests
5.5 MBYour homepage downloads 5.5 MB in 327 requests on a phone: scripts 2.1 MB (92), other files 1.1 MB (176) and images 1.0 MB (31). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
4001-1500.jpg 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).
3 images far larger than shown
98 KiB3 images are downloaded at several times the size a phone draws them, for example 13_5_2x_a891d1e1-21e3-48b1-85f2-f8e8ff10df81.png at 1,300 px wide, shown at 350 px. Resized copies would save about 98 KiB.
3 images below the first screen load straight away
3 images further down the page (282 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 187.4 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
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 96 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
100 internal links, 13 external
The homepage links to 100 pages on anonasecurity.com and 13 external pages.
8 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Save up to 45% during the Anona Fall Sale. Shop security cameras, video doorbells and home security systems with local …”.
One H1 headline
Your main headline reads: “Anona Security”.
Title: 51 characters
Your title is a healthy 51 characters: “Anona Fall Sale | Home Security Deals Up to 45% Off”.
Canonical URL set
The canonical URL is https://www.anonasecurity.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization 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.anonasecurity.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,335 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.anonasecurity.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share 2 titles
https://www.anonasecurity.com/products/4k-solar-home-security-system and https://www.anonasecurity.com/products/4k-solar-home-security-system-with-24-7-recording-4-cam-kit all use the title “Anona Aurora + SmartBase|4K Solar Home Security System with 24/7 Reco…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://www.anonasecurity.com/pages/anona-app, https://www.anonasecurity.com/pages/contact, https://www.anonasecurity.com/pages/support, https://www.anonasecurity.com/apps/17TRACK and https://www.anonasecurity.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.anonasecurity.com/products/4k-solar-home-security-system and https://www.anonasecurity.com/products/4k-solar-home-security-system-with-24-7-recording-4-cam-kit use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.anonasecurity.com/apps/17TRACK, whose canonical is https://www.anonasecurity.com/apps/17track. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://www.anonasecurity.com/pages/anona-app, https://www.anonasecurity.com/pages/contact, https://www.anonasecurity.com/pages/support, https://www.anonasecurity.com/collections/all and https://www.anonasecurity.com/pages/outdoor-security-cameras have 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 27 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
10 small tap targets
10 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.anonasecurity.com/cdn/shop/t/97/assets/press-review-section.css?v=12901' becau…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 472 words of copy
The homepage carries about 472 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “Learn More”.
21 calls to action
The homepage has 21 calls to action, for example “App Download”, “Contact Us” and “Track Your Order”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 15 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
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.
31 other companies contacted
Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 anonasecurity.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Cartsee Email Marketing Sms · Klaviyo Email Marketing Sms · Judge Me Reviews · Ecomposer Builder · Zoorix Cross Sell · Intercom · Spin Wheel Ea · Page Speed Optimizer · Kickbooster · pandect.es · goaffpro.com · cloudfront.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on anonasecurity.com, including 17 speed issues, 1 SEO issue and 1 conversion gap. 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.