Website review, no card needed
anniescatalog.com website review
Visit site (opens in a new tab)Reviewed 6 November 202647 issues · 94 checks
This review found 47 issues worth fixing on anniescatalog.com, 18 of them high impact, across 94 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
74C- #86,555 of 123,862 reviewed websitesbeats 26%
- #54,436 of 69,698 online storesbeats 18%
- #323 of 725 Magento storesbeats 51%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 170 ms |
| May 23, 2026 | 172 ms |
| May 30, 2026 | 174 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 181 ms |
| Jun 20, 2026 | 180 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 180 ms |
| Jul 18, 2026 | 181 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 183 ms |
| Aug 8, 2026 | 184 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 193 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 197 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 204 ms |
| Oct 17, 2026 | 204 ms |
| Oct 24, 2026 | 202 ms |
| Oct 31, 2026 | 202 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.9 s
1.8 s
2.7 s
3.6 s
4.4 s
5.3 s
6.2 s
7.1 s
Speed
Improve image delivery
3.3 s · 1.4 MB13 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.
audioeye.com adds 2.7 s
2.7 saudioeye.com costs a phone 2.7 s of main-thread work and 345 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.6 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.7 s
A phone's processor spends 9.7 s on main-thread work while loading, 7.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,355 HTML elements
The page has 3,355 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 (audioeye.com, Google Tag Manager and Facebook and others), adding 1.8 MB and 3.9 s of main-thread time.
Use efficient cache lifetimes
150 ms · 1.0 MB29 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Reduce unused CSS
750 ms · 138 KiBAbout 138 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Reduce unused JavaScript
847 KiBAbout 847 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 554 ms
554 msGoogle Tag Manager costs a phone 554 ms of main-thread work and 530 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 336 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 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: 10 ms
10 msYour server sent the HTML in 10 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: 19.7 s
19.7 sYour largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cozy Christmas Morning Afghan Crochet Kit - 0400701000479”.
Speed Index: 18.8 s
18.8 sVisually, the page fills in at 18.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 37.8 s
37.8 sThe page becomes fully interactive after 37.8 s. Good is under 3.8 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 529 ms
529 msScripts block taps and scrolling for 529 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 170 ms to 202 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 170 ms
170 msReal visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.032
0.032The layout barely moves while loading (CLS 0.032, good is under 0.1).
Images and page weight
Page weight: 10.1 MB in 511 requests
10.1 MBYour homepage downloads 10.1 MB in 511 requests on a phone: images 6.7 MB (84), scripts 2.7 MB (317) and fonts 270 KiB (12). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.
10 images below the first screen load straight away
10 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
15 KiB1 image is downloaded at several times the size a phone draws it, for example Lena_250circle_1.png at 250 px wide, shown at 75 px. Resized copies would save about 15 KiB.
1 image in older formats
1 image (69 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.9 g of CO₂ per visit
2.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.87 g of CO₂e: 344.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (10 elements)
Images must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.
Orphan list items
Some list items are not inside a list.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
608 internal links, 6 external
The homepage links to 608 pages on anniescatalog.com and 6 external pages.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Explore patterns, fabrics, yarns, supplies, and inspiration at Annie's Attic. Connect with crafters and kindle your pas…”.
Title: 59 characters
Your title is a healthy 59 characters: “Annie's Attic: Spark Your Creativity, Connect Through Craft”.
Canonical URL set
The canonical URL is https://www.anniesattic.com/.
Structured data in place
Structured data found: WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.anniesattic.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.anniesattic.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.
Opted out of AI training for 1 crawler
robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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 (2,786 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.anniesattic.com/shop/promos/crochet-kits and https://www.anniesattic.com/shop/promos/fabric are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages without a meta description
https://www.anniesattic.com/shop/promos/crochet-kits and https://www.anniesattic.com/shop/promos/fabric have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.anniesattic.com/shop/promos/crochet-kits and https://www.anniesattic.com/shop/promos/fabric 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 195 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.
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 a title
All 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=223003678&Ver=2&mid=5132806e-de54-4350-b870-3e1593d05f1f&bo=1&sid=88bf4b70da3711f18754c96f82a1b1db&vid=88c4e6e0da3711f1a2be75ebc2c98e53&vids=1&msclkid=N&pi=918639831&l.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://wsv3cdn.audioeye.com/static-scripts/v2/2026-11-05a/fullCSS.bundle.css' from origin…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
91 of 99 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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,236 words of copy
The homepage carries about 1,236 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
30 calls to action
The homepage has 30 calls to action, for example “Shop Now”, “How to Join a New Ball” and “SHOP NOW”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
38 cookies set on arrival
38Opening the homepage sets 38 cookies (measured from a US location before any click).
44 other companies contacted
Loading the homepage contacts 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 anniescatalog.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Magento
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on anniescatalog.com, including 22 speed issues, 3 SEO issues and 4 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.