Website review, no card needed

warehouse-aquatics.co.uk logo

warehouse-aquatics.co.uk website review

Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 86 checks

This review found 37 issues worth fixing on warehouse-aquatics.co.uk, 18 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.3 s1.1 sJul 4Nov 71.2 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Sep 19, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.3 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
99 ms86 msJul 4Oct 3187 ms
Show as table
DateReal-visitor tap response (INP)
Jul 4, 202696 ms
Jul 11, 202697 ms
Jul 18, 202697 ms
Jul 25, 202696 ms
Oct 10, 202695 ms
Oct 17, 202694 ms
Oct 24, 202692 ms
Oct 31, 202687 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

Full-page screenshot of warehouse-aquatics.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. warehouse-aquatics.co.uk at 0.7 s0.7 s
  2. warehouse-aquatics.co.uk at 1.3 s1.3 s
  3. warehouse-aquatics.co.uk at 2.0 s2.0 s
  4. warehouse-aquatics.co.uk at 2.6 s2.6 s
  5. warehouse-aquatics.co.uk at 3.3 s3.3 s
  6. warehouse-aquatics.co.uk at 3.9 s3.9 s
  7. warehouse-aquatics.co.uk at 4.6 s4.6 s
  8. warehouse-aquatics.co.uk at 5.2 s5.2 s

Speed

7 to fix24
  • Reduce unused JavaScript

    1.6 s · 297 KiB

    About 297 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Mobile performance score: 24

    24/100

    Your mobile performance score is 24. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 5,423 HTML elements

    The page has 5,423 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    500 ms · 264 KiB

    6 images could be 264 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Google Tag Manager adds 460 ms

    460 ms

    Google Tag Manager costs a phone 460 ms of main-thread work and 464 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.

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 260 ms. During a long task the page ignores taps.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Shopify and Google/Doubleclick Ads and others), adding 640 KiB and 497 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 18 KiB

    About 18 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.

  • Render-blocking requests

    150 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • Use efficient cache lifetimes

    5 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).

  • 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: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 46.4 s

    46.4 s

    Your largest element takes 46.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Warehouse Aquatics”.

  • Time to Interactive: 46.8 s

    46.8 s

    The page becomes fully interactive after 46.8 s. Good is under 3.8 s.

  • Speed Index: 15.3 s

    15.3 s

    Visually, the page fills in at 15.3 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 3.8 s

    3.8 s

    The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

  • Cumulative Layout Shift: 0.326

    0.326

    The layout shifts by 0.326 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 695 ms

    695 ms

    Scripts block taps and scrolling for 695 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 96 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 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.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 91 ms

    91 ms

    Real visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.7 s

    0.7 s

    Real visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 331 ms

    331 ms

    Real visitors wait 331 ms for your server to start answering (75th percentile). Good is under 800 ms.

Images and page weight

3 to fix42
  • Page weight: 9.3 MB in 204 requests

    9.3 MB

    Your homepage downloads 9.3 MB in 204 requests on a phone: images 7.1 MB (43), scripts 1.0 MB (73) and other files 616 KiB (61). Under 2 MB keeps phones on slow connections fast.

  • 15 images far larger than shown

    1.7 MB

    15 images are downloaded at several times the size a phone draws them, for example Collection_Circles_14.svg at 437 px wide, shown at 60 px. Resized copies would save about 1.7 MB.

  • An image on the first screen is lazy-loaded

    0974a7_2.jpg 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).

  • About 2.6 g of CO₂ per visit

    2.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.64 g of CO₂e: 316.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

8 to fixGoogle 8790
  • 18 text elements with low contrast

    18 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.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 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.

  • 29 links without text

    29 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (5 elements)

    Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Warehouse Aquatics Gift Card”). One clear main headline is easier for people and search engines.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 742 internal links, 1 external

    The homepage links to 742 pages on warehouse-aquatics.co.uk and 1 external page.

7 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Discover the latest in aquatics supplies for the home and garden with the best prices on aquariums, pond supplies and m…”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Warehouse Aquatics | Aquatic & Pond Supplies at the best prices”.

  • Canonical URL set

    The canonical URL is https://warehouse-aquatics.co.uk/.

  • Structured data in place

    Structured data found: Organization, ProductGroup 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://warehouse-aquatics.co.uk/sitemap.xml.

AI search readiness

100
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,242 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://warehouse-aquatics.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

6 to fix55
  • 1 page without a title

    https://warehouse-aquatics.co.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://warehouse-aquatics.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://warehouse-aquatics.co.uk/collections/marine-fish and https://warehouse-aquatics.co.uk/collections/marine-fish/Wreckfish all use the title “Marine Fish – Warehouse Aquatics”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://warehouse-aquatics.co.uk/customer_authentication/redirect, https://warehouse-aquatics.co.uk/collections/marine-fish, https://warehouse-aquatics.co.uk/collections/marine-fish/Angels, https://warehouse-aquatics.co.uk/collections/marine-fish/Dwarf-Angels, https://warehouse-aquatics.co.uk/collections/marine-fish/Tangs and https://warehouse-aquatics.co.uk/collections/marine-fish/Damsels-&-Chromis and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 links to non-canonical URLs

    Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://warehouse-aquatics.co.uk/collections/marine-fish/Angels, whose canonical is https://warehouse-aquatics.co.uk/collections/marine-fish/angels. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://warehouse-aquatics.co.uk/customer_authentication/redirect, https://warehouse-aquatics.co.uk/collections/marine-fish, https://warehouse-aquatics.co.uk/collections/marine-fish/Angels, https://warehouse-aquatics.co.uk/collections/marine-fish/Dwarf-Angels, https://warehouse-aquatics.co.uk/collections/marine-fish/Tangs and https://warehouse-aquatics.co.uk/collections/marine-fish/Damsels-&-Chromis and 9 others 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 198 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    129 of 130 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 433 words of copy

    The homepage carries about 433 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

7 checks passed
  • 21 calls to action

    The homepage has 21 calls to action, for example “Sign in/ Register”, “Shop Handpicked Corals” and “Shop Japanese Koi”.

  • 78 short forms

    78 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 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.

  • 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

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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

    16

    Opening 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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 warehouse-aquatics.co.uk, 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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blockify Fraud Filter · Region Restrictions · Boo Eu Withdrawal Button

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

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on warehouse-aquatics.co.uk, including 13 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25