Website review, no card needed
amazinglycat.com website review
Visit site (opens in a new tab)Reviewed 12 November 202618 issues · 55 checks
This review found 18 issues worth fixing on amazinglycat.com, 7 of them high impact, across 55 checks. The most urgent: use efficient cache lifetimes. 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
76C- #66,754 of 108,829 reviewed websitesbeats 34%
- #42,924 of 61,762 online storesbeats 26%
- #40,745 of 56,362 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideOne 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
Use efficient cache lifetimes
2.0 s · 616 KiB47 files are served with short cache lifetimes, so returning visitors download them again (616 KiB).
Improve image delivery
1.6 s · 625 KiB4 images could be 625 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.
Mobile performance score: 75
75/100Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
350 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Render-blocking requests
300 ms21 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Reduce unused JavaScript
150 ms · 25 KiBAbout 25 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Cloudflare and Hexton), adding 11 KiB and 12 ms of main-thread time.
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.
2 checks passed
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 57 ms of it running JavaScript. That is comfortably low.
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 6.6 s
6.6 sThe page becomes fully interactive after 6.6 s. Good is under 3.8 s.
Speed Index: 3.6 s
3.6 sVisually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 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).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
Untitled_design_47_v-1693834234-width-550.png 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 in older formats
3 images (414 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 0.3 g of CO₂ per visit
0.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.26 g of CO₂e: 31.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 945 KiB in 67 requests
945 KiBYour homepage downloads 945 KiB in 67 requests on a phone: images 756 KiB (5), scripts 108 KiB (25) and stylesheets 51 KiB (26). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://amazinglycat.com/sitemap.xml, so Google discovers your pages only by following links.
19 internal links, 1 external
The homepage links to 19 pages on amazinglycat.com and 1 external page.
6 checks passed
Meta description: 116 characters
Your meta description is 116 characters: “Discover the most amazingly interactive cat toys that will help entertain and exercise your cat for hours every day!”.
One H1 headline
Your main headline reads: “AmazinglyCat”.
Title: 51 characters
Your title is a healthy 51 characters: “Amazingly Cat - Interactive Cat Toys – AmazinglyCat”.
Canonical URL set
The canonical URL is https://www.amazinglycat.com/.
Structured data in place
Structured data found: Organization and WebSite.
robots.txt in place
robots.txt is in place.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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://amazinglycat.com/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 (994 words), so crawlers that don't run JavaScript still read it.
Other pages
9 linked pages are broken
Your homepage links to https://amazinglycat.com/collections/all, https://amazinglycat.com/pages/cat-blog, https://amazinglycat.com/pages/meet-the-team, https://amazinglycat.com/pages/contact, https://amazinglycat.com/pages/amazinglycat-quiz and https://amazinglycat.com/pages/ugc-creator-program and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.amazinglycat.com/cdn/fonts/questrial/questrial_n4.66abac5d8209a647b4bf8089b0451928ef144c…”.
2 checks passed
Tap targets are thumb-sized
8 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 368 words of copy
The homepage carries about 368 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Shop”, “Contact” and “Start Quiz Now →”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 amazinglycat.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
cookihq.com
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
- The footer still says © 2025.
Stack
- E-commerce
- Shopify
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on amazinglycat.com, including 8 speed issues, 2 SEO 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.