Website review, no card needed
watery.ie website review
Visit site (opens in a new tab)Reviewed 5 November 202629 issues · 88 checks
This review found 29 issues worth fixing on watery.ie, 10 of them high impact, across 88 checks. The most urgent: main-thread work: 16.6 s. 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
83B- #28,583 of 125,920 reviewed websitesbeats 72%
- #18,545 of 70,305 online storesbeats 67%
- #17,950 of 63,856 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 165 ms |
| May 23, 2026 | 165 ms |
| May 30, 2026 | 165 ms |
| Jun 6, 2026 | 172 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 172 ms |
| Jun 27, 2026 | 175 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 176 ms |
| Jul 18, 2026 | 178 ms |
| Jul 25, 2026 | 177 ms |
| Aug 1, 2026 | 178 ms |
| Aug 8, 2026 | 179 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 181 ms |
| Aug 29, 2026 | 184 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 181 ms |
| Sep 26, 2026 | 182 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 187 ms |
| Oct 24, 2026 | 184 ms |
| Oct 31, 2026 | 185 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
Main-thread work: 16.6 s
A phone's processor spends 16.6 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
4,274 HTML elements
The page has 4,274 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 (Clarity, Klaviyo and Klarna and others), adding 1.4 MB and 1.1 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
550 ms · 144 KiB17 files are served with short cache lifetimes, so returning visitors download them again (144 KiB).
Clarity adds 587 ms
587 msClarity costs a phone 587 ms of main-thread work and 29 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 273 ms. During a long task the page ignores taps.
Shopify adds 37 ms
37 msShopify costs a phone 37 ms of main-thread work and 730 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.
Improve image delivery
200 ms · 186 KiB6 images could be 186 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused JavaScript
233 KiBAbout 233 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
150 ms · 27 KiBAbout 27 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.
Legacy JavaScript
50 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
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: 33 ms
33 msYour server sent the HTML in 33 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners use cookies to enhance your experience …”.
Time to Interactive: 16.5 s
16.5 sThe page becomes fully interactive after 16.5 s. Good is under 3.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 585 ms
585 msScripts block taps and scrolling for 585 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 165 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, 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).
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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 173 ms
173 msReal visitors wait 173 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.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: 409 ms
409 msReal visitors wait 409 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.054
0.054The layout barely moves while loading (CLS 0.054, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 416 requests
3.7 MBYour homepage downloads 3.7 MB in 416 requests on a phone: other files 1.8 MB (255), scripts 1.1 MB (98) and images 415 KiB (19). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
44 KiB1 image is downloaded at several times the size a phone draws it, for example Black_Month_2026_-_Mobile_1214x700_-_IE_-_new-01.png at 1,214 px wide, shown at 326 px. Resized copies would save about 44 KiB.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.2 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
Hidden but focusable
15 elements hidden from screen readers can still receive keyboard focus.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
37 images without alt text
37 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (72 elements)
All page content should be contained by landmarks: 72 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Watery.ie ⇒ Swimming equipment, swimwear & swimming goggles ⇒ Watery”.
Meta description is long (167 characters)
Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("watery.ie")”.
612 internal links, 13 external
The homepage links to 612 pages on watery.ie and 13 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Ireland's largest and most popular swim shop”.
Canonical URL set
The canonical URL is https://watery.ie/.
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://watery.ie/sitemap.xml.
AI search readiness
No llms.txt
There is no https://watery.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (3,299 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
7 checks passed
Linked pages load
8 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.
Every page has a meta description
All 8 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
54 of 56 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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,446 words of copy
The homepage carries about 1,446 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
9 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Learn more about Watery”, “Shop Black Month →” and “Contact usWe'll help you choose right”.
19 short forms
19 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, a star rating and “Over 650,000 happy customers”.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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 Meta Pixel 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.
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 watery.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
Judge Me Reviews · Klaviyo Email Marketing Sms · Microsoft Clarity · Stape Remix · webmarked.net · profitmetrics.io · trustpilot.com · amazonaws.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
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on watery.ie, including 14 speed issues, 3 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.