Website review, no card needed
caribbeanpools.com website review
Visit site (opens in a new tab)Reviewed 19 October 202642 issues · 93 checks
This review found 42 issues worth fixing on caribbeanpools.com, 18 of them high impact, across 93 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
72C- #91,980 of 118,362 reviewed websitesbeats 19%
- #57,181 of 67,243 online storesbeats 12%
- #1,822 of 2,712 WooCommerce storesbeats 28%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 63 ms |
| May 9, 2026 | 64 ms |
| May 16, 2026 | 63 ms |
| May 23, 2026 | 70 ms |
| May 30, 2026 | 69 ms |
| Jun 6, 2026 | 68 ms |
| Jun 13, 2026 | 70 ms |
| Jun 20, 2026 | 70 ms |
| Jun 27, 2026 | 71 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 71 ms |
| Jul 18, 2026 | 71 ms |
| Jul 25, 2026 | 70 ms |
| Aug 1, 2026 | 70 ms |
| Aug 8, 2026 | 72 ms |
| Aug 15, 2026 | 79 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 84 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 98 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
0.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
Reduce unused JavaScript
4.2 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Render-blocking requests
1.6 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Use efficient cache lifetimes
1.4 s · 242 KiB12 files are served with short cache lifetimes, so returning visitors download them again (242 KiB).
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 3.1 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 (Google Tag Manager, getjobber.com and Google CDN and others), adding 3.0 MB and 1.8 s of main-thread time.
Reduce unused CSS
760 ms · 119 KiBAbout 119 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.
Google Tag Manager adds 548 ms
548 msGoogle Tag Manager costs a phone 548 ms of main-thread work and 660 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.
getjobber.com adds 445 ms
445 msgetjobber.com costs a phone 445 ms of main-thread work and 1.1 MB 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 284 ms
284 msGoogle CDN costs a phone 284 ms of main-thread work and 733 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 289 ms. During a long task the page ignores taps.
Google Maps adds 130 ms
130 msGoogle Maps costs a phone 130 ms of main-thread work and 350 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.
Legacy JavaScript
150 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 68 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.
Improve image delivery
7 KiB1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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
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 FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.0 s
3.0 sReal visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 8.5 s
8.5 sThe first text or image appears after 8.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 17.0 s
17.0 sYour largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Create Your Paradise CONSTRUCTION SERVICE RENOVATION REQUES…”.
Time to Interactive: 29.2 s
29.2 sThe page becomes fully interactive after 29.2 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 865 ms
865 msScripts block taps and scrolling for 865 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 46% slower for real visitors
+46%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 63 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 50% slower for real visitors
+50%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 11.7 MB in 192 requests
11.7 MBYour homepage downloads 11.7 MB in 192 requests on a phone: media 7.2 MB (2), scripts 3.2 MB (99) and fonts 562 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 3.3 g of CO₂ per visit
3.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.32 g of CO₂e: 398.4 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
19 buttons without a name
19 buttons have no accessible name, so screen readers announce just “button”.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
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 (91 elements)
All page content should be contained by landmarks: 91 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.
41 links without text
41 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h1 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (94 characters)
Your title is 94 characters, so Google will cut it off around 60: “Caribbean Pools | Schererville Local Pool Installers | Local Pool Installers Near Scherer…”.
Meta description is long (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (LocalBusiness and Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.
No XML sitemap
No XML sitemap at https://caribbeanpools.com/sitemap_index.xml, so Google discovers your pages only by following links.
16 links with vague text
16 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
115 internal links, 15 external
The homepage links to 115 pages on caribbeanpools.com and 15 external pages.
4 checks passed
One H1 headline
Your main headline reads: “CUSTOM INGROUND POOLS IN ILLINOIS & INDIANA”.
Canonical URL set
The canonical URL is https://www.caribbeanpools.com/.
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.
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: 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 (1,324 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.caribbeanpools.com/llms.txt (8 KiB, 41 links), a plain-text guide to the site for AI tools.
Other pages
3 pages slow to respond
https://www.caribbeanpools.com/faqs, https://www.caribbeanpools.com/pool-equipment-upkeep and https://www.caribbeanpools.com/pool-services/pool-repairs/service-request took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
7 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.
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 15 pages that loaded have a <title>.
Best practices
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
73 of 85 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 1,355 words of copy
The homepage carries about 1,355 words of visible text.
10 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT” and “SCHEDULE SERVICE NOW”.
24 calls to action
The homepage has 24 calls to action, for example “Service Request”, “Shop All Products” and “Contact”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 16 testimonial or review blocks, 10 customer or partner logos, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 8 phone links 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.
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 Amplitude, Google Ads, Google Analytics, Google Tag Manager 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.
15 cookies set on arrival
15Opening the homepage sets 15 cookies, 2 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.
28 other companies contacted
Loading the homepage contacts 28 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 caribbeanpools.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on caribbeanpools.com, including 23 speed issues and 6 SEO issues. 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.