Website review, no card needed
annieinc.com website review
Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 82 checks
This review found 35 issues worth fixing on annieinc.com, 13 of them high impact, across 82 checks. The most urgent: fails Core Web Vitals for real visitors. 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
78C- #59,483 of 117,615 reviewed websitesbeats 44%
- #39,126 of 66,923 online storesbeats 36%
- #37,413 of 61,018 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 183 ms |
| May 9, 2026 | 183 ms |
| May 16, 2026 | 183 ms |
| May 23, 2026 | 189 ms |
| May 30, 2026 | 192 ms |
| Jun 6, 2026 | 195 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 197 ms |
| Jun 27, 2026 | 199 ms |
| Jul 4, 2026 | 214 ms |
| Jul 11, 2026 | 238 ms |
| Jul 18, 2026 | 255 ms |
| Jul 25, 2026 | 274 ms |
| Aug 1, 2026 | 269 ms |
| Aug 8, 2026 | 264 ms |
| Aug 15, 2026 | 258 ms |
| Aug 22, 2026 | 269 ms |
| Aug 29, 2026 | 278 ms |
| Sep 5, 2026 | 274 ms |
| Sep 12, 2026 | 277 ms |
| Sep 19, 2026 | 271 ms |
| Sep 26, 2026 | 262 ms |
| Oct 3, 2026 | 262 ms |
| Oct 10, 2026 | 266 ms |
| Oct 17, 2026 | 271 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
1.0 s
1.9 s
2.9 s
3.8 s
4.8 s
5.8 s
6.7 s
7.7 s
Speed
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 2.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 (Shopify, Clarity and Google CDN and others), adding 2.0 MB and 869 ms of main-thread time.
Reduce unused JavaScript
300 ms · 744 KiBAbout 744 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.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 83). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
488 KiB31 images could be 488 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,932 HTML elements
The page has 2,932 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 159 ms
159 msShopify costs a phone 159 ms of main-thread work and 833 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.
Google CDN adds 136 ms
136 msGoogle CDN costs a phone 136 ms of main-thread work and 296 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.
Render-blocking requests
250 ms15 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 129 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
126 KiB17 files are served with short cache lifetimes, so returning visitors download them again (126 KiB).
Reduce unused CSS
42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 83 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.
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 JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 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.
Time to Interactive: 27.2 s
27.2 sThe page becomes fully interactive after 27.2 s. Good is under 3.8 s.
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 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 INP: 215 ms
215 msReal visitors wait 215 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 47% slower for real visitors
+47%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 183 ms to 271 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.155
0.155The layout shifts by 0.155 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 344 ms
344 msScripts block taps and scrolling for 344 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 520 ms
520 msReal visitors wait 520 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 5.0 MB in 442 requests
5.0 MBYour homepage downloads 5.0 MB in 442 requests on a phone: scripts 2.2 MB (185), images 1.5 MB (76) and other files 868 KiB (123). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
37 KiB1 image is downloaded at several times the size a phone draws it, for example Annie_hair_Care_Brand_Image.png at 1,200 px wide, shown at 360 px. Resized copies would save about 37 KiB.
About 1.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
41 text elements with low contrast
41 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 94 images in the HTML carry an alt attribute.
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (284 characters)
Your meta description is 284 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
358 internal links, 14 external
The homepage links to 358 pages on annieinc.com and 14 external pages.
6 checks passed
Title: 47 characters
Your title is a healthy 47 characters: “Annie International – Annie International, Inc.”.
Canonical URL set
The canonical URL is https://www.annieinc.com/.
Structured data in place
Structured data found: 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.annieinc.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 (2,292 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.annieinc.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.annieinc.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.annieinc.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.annieinc.com/collections/all, https://www.annieinc.com/customer_authentication/redirect and https://www.annieinc.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.annieinc.com/customer_authentication/redirect 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 179 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.
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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97111638&tm=gtm002&Ver=2&mid=464dd7bc-b80c-455f-9e8c-afabf6978288&bo=1&sid=bd7e45b0ce2411f1a64ee52da597796b&vid=bd7e6850ce2411f1a161417dbb8f9dc9&vids=1&msclkid=N>m_t.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.
2 checks passed
Tap targets are thumb-sized
76 of 80 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.
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 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,427 words of copy
The homepage carries about 1,427 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact information”.
13 short forms
13 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Microsoft Ads 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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
36 other companies contacted
Loading the homepage contacts 36 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 annieinc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on annieinc.com, including 17 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.