Website review, no card needed

poolwerx.com.au logo

poolwerx.com.au website review

Visit site (opens in a new tab)Reviewed 4 November 202637 issues · 84 checks

This review found 37 issues worth fixing on poolwerx.com.au, 12 of them high impact, across 84 checks. The most urgent: fails Core Web Vitals for real visitors. 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
4.6 s3.2 sMay 16Oct 313.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.4 s
May 23, 20264.3 s
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.1 s
Jun 20, 20264.1 s
Jun 27, 20264.1 s
Jul 4, 20264.1 s
Jul 11, 20264.2 s
Jul 18, 20264.1 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.1 s
Aug 15, 20264.0 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.7 s
Oct 17, 20263.6 s
Oct 24, 20263.4 s
Oct 31, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
383 ms181 msMay 16Oct 31204 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026212 ms
May 23, 2026209 ms
May 30, 2026204 ms
Jun 6, 2026205 ms
Jun 13, 2026215 ms
Jun 20, 2026233 ms
Jun 27, 2026257 ms
Jul 4, 2026275 ms
Jul 11, 2026290 ms
Jul 18, 2026297 ms
Jul 25, 2026311 ms
Aug 1, 2026312 ms
Aug 8, 2026327 ms
Aug 15, 2026333 ms
Aug 22, 2026335 ms
Aug 29, 2026340 ms
Sep 5, 2026344 ms
Sep 12, 2026346 ms
Sep 19, 2026350 ms
Sep 26, 2026358 ms
Oct 3, 2026360 ms
Oct 10, 2026344 ms
Oct 17, 2026295 ms
Oct 24, 2026236 ms
Oct 31, 2026204 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 poolwerx.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. poolwerx.com.au at 0.9 s0.9 s
  2. poolwerx.com.au at 1.9 s1.9 s
  3. poolwerx.com.au at 2.8 s2.8 s
  4. poolwerx.com.au at 3.8 s3.8 s
  5. poolwerx.com.au at 4.7 s4.7 s
  6. poolwerx.com.au at 5.6 s5.6 s
  7. poolwerx.com.au at 6.6 s6.6 s
  8. poolwerx.com.au at 7.5 s7.5 s

Speed

11 to fix52
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Adobe TypeKit and others), adding 1.4 MB and 1.6 s of main-thread time.

  • Google Tag Manager adds 959 ms

    959 ms

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

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    650 ms · 122 KiB

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

  • Use efficient cache lifetimes

    300 ms · 356 KiB

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

  • Render-blocking requests

    650 ms

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

  • Reduce unused JavaScript

    497 KiB

    About 497 KiB of JavaScript is downloaded but never used on this page.

  • 14 long tasks on the main thread

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

  • Main-thread work: 3.4 s

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

  • Facebook adds 264 ms

    264 ms

    Facebook costs a phone 264 ms of main-thread work and 310 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,668 HTML elements

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

  • Legacy JavaScript

    39 KiB

    Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page.

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

1 checks passed
  • Server response: 568 ms

    568 ms

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

Core Web Vitals

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Speed Index: 12.1 s

    12.1 s

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

  • Time to Interactive: 16.5 s

    16.5 s

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

  • Total Blocking Time: 914 ms

    914 ms

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

  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (3.1 s).

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 189 ms

    189 ms

    Real visitors wait 189 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: 1.6 s

    1.6 s

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

  • Largest content (LCP) got 22% faster for real visitors

    -22%

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

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 142 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 142 requests on a phone: scripts 1.6 MB (72), images 294 KiB (18) and HTML 196 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.62 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.5 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

8 to fixGoogle 7689
  • 32 buttons without a name

    32 buttons have no accessible name, so screen readers announce just “button”.

  • 17 text elements with low contrast

    17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 17 tap targets too small

    17 tap targets are too small or too close together to hit reliably with a finger.

  • 5 images without alt text

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h5), 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8589
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 H1 headlines

    There are 3 <h1> headlines (“It's A Summer Staycation!”, “Meet The Chosen Ones” and “Australia's Pool Care Experts”). One clear main headline is easier for people and search engines.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 215 internal links, 9 external

    The homepage links to 215 pages on poolwerx.com.au and 9 external pages.

6 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Poolwerx is Australia's largest pool and spa maintenance network, offering pool services and supplies. Contact your loc…”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Pool Cleaning, Supplies and Maintenance | Poolwerx AU”.

  • Canonical URL set

    The canonical URL is http://www.poolwerx.com.au/.

  • 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.poolwerx.com.au/sitemap.xml.

AI search readiness

1 to fix88
  • 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.poolwerx.com.au/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.

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

Other pages

2 to fix90
  • 2 pages share a title

    https://www.poolwerx.com.au/shop/pool-cleaners and https://www.poolwerx.com.au/shop/robotic-pool-cleaners all use the title “Pool Cleaners | Robotic Pool Cleaners, Pool Vacuums & More”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.poolwerx.com.au/shop/pool-cleaners and https://www.poolwerx.com.au/shop/robotic-pool-cleaners use the same meta description. A description written for each page earns more clicks.

  • 15 pages slow to respond

    https://www.poolwerx.com.au/shop, https://www.poolwerx.com.au/shop/pool-cleaners, https://www.poolwerx.com.au/shop/pool-filters, https://www.poolwerx.com.au/shop/pool-heaters, https://www.poolwerx.com.au/shop/pool-chemicals and https://www.poolwerx.com.au/shop/pool-pumps and 9 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 119 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56001962&tm=gtm002&Ver=2&mid=e6027956-0f5b-4363-a7cb-223bbc7554fb&bo=1&sid=5f5324c0d7e611f1bc105126f0633e7a&vid=5f5353a0d7e611f182ab57b3909dc5ff&vids=1&msclkid=N&pi=91.

  • 9 small tap targets

    9 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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,297 words of copy

    The homepage carries about 1,297 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop the New Range”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Learn More”, “Learn more” and “Download Brochure”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 33 other companies contacted

    Loading the homepage contacts 33 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 poolwerx.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Astro
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
CloudFront

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 poolwerx.com.au, including 18 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

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