Website review, no card needed
anicura.ie website review
Visit site (opens in a new tab)Reviewed 16 November 202636 issues · 88 checks
This review found 36 issues worth fixing on anicura.ie, 16 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
79C- #53,051 of 117,615 reviewed websitesbeats 49%
- #35,157 of 66,923 online storesbeats 42%
- #33,730 of 61,018 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.9 s |
| Nov 7, 2026 | 2.7 s |
| Nov 14, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 169 ms |
| Jun 20, 2026 | 160 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 160 ms |
| Jul 11, 2026 | 149 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 156 ms |
| Aug 8, 2026 | 158 ms |
| Aug 15, 2026 | 155 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 158 ms |
| Sep 12, 2026 | 166 ms |
| Sep 19, 2026 | 164 ms |
| Sep 26, 2026 | 177 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 175 ms |
| Oct 17, 2026 | 182 ms |
| Oct 24, 2026 | 178 ms |
| Oct 31, 2026 | 175 ms |
| Nov 7, 2026 | 175 ms |
| Nov 14, 2026 | 172 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
Speed
Reduce unused JavaScript
1.5 s · 3.7 MBAbout 3.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
YouTube adds 2.5 s
2.5 sYouTube costs a phone 2.5 s of main-thread work and 5.9 MB 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.
Main-thread work: 11.2 s
A phone's processor spends 11.2 s on main-thread work while loading, 5.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, rebuyengine.com and Klaviyo and others), adding 7.8 MB and 3.2 s of main-thread time.
Improve image delivery
950 ms · 429 KiB12 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 950 ms faster on a phone.
Render-blocking requests
950 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
rebuyengine.com adds 194 ms
194 msrebuyengine.com costs a phone 194 ms of main-thread work and 652 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.
2,050 HTML elements
The page has 2,050 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 160 ms
160 msKlaviyo costs a phone 160 ms of main-thread work and 314 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.
tidio.co adds 87 ms
87 mstidio.co costs a phone 87 ms of main-thread work and 517 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.
Use efficient cache lifetimes
200 ms · 27 KiB12 files are served with short cache lifetimes, so returning visitors download them again (27 KiB).
Legacy JavaScript
150 ms · 60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 197 ms. During a long task the page ignores taps.
Reduce unused CSS
128 KiBAbout 128 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 26 ms
26 msYour server sent the HTML in 26 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 20.3 s
20.3 sVisually, the page fills in at 20.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 55.7 s
55.7 sThe page becomes fully interactive after 55.7 s. Good is under 3.8 s.
Total Blocking Time: 930 ms
930 msScripts block taps and scrolling for 930 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 153 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.7 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 172 ms
172 msReal visitors wait 172 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 546 ms
546 msReal visitors wait 546 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Images and page weight
Page weight: 10.3 MB in 359 requests
10.3 MBYour homepage downloads 10.3 MB in 359 requests on a phone: scripts 7.0 MB (131), images 976 KiB (34) and other files 709 KiB (105). Under 2 MB keeps phones on slow connections fast.
About 2.9 g of CO₂ per visit
2.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.92 g of CO₂e: 350.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
[role="img"] and [role="image"] elements must have alternative text (6 elements)
[role="img"] and [role="image"] elements must have alternative text: 6 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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
24 links without text
24 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (15 characters)
Your title is only 15 characters: “Anicura Ireland”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
One H1 headline
Your <h1> is empty.
164 internal links, 9 external
The homepage links to 164 pages on anicura.ie and 9 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://anicura.ie/.
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://anicura.ie/sitemap.xml.
AI search readiness
No llms.txt
There is no https://anicura.ie/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.
3 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 (1,108 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://anicura.ie/collections/bundles, https://anicura.ie/collections/all and https://anicura.ie/collections/individual-products have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://anicura.ie/collections/bundles 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 66 found) and read each the way a search engine does.
5 checks passed
Linked pages load
4 pages of 15 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
31 small tap targets
31 of 62 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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 952 words of copy
The homepage carries about 952 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: “SHOP NOW” and “Sign Up!”.
14 calls to action
The homepage has 14 calls to action, for example “Shop”, “Contact Us” and “Learn More”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 36 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 of them by other companies (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.
37 other companies contacted
Loading the homepage contacts 37 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 anicura.ie, 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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Triplewhale · Simple Affiliate · Klaviyo Email Marketing Sms · Easylocation · Profy Announcement Bar · loox.io · rebuyengine.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
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on anicura.ie, including 16 speed issues, 4 SEO issues 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.