Website review, no card needed
athomerecreation.com website review
Visit site (opens in a new tab)Reviewed 5 November 202657 issues · 91 checks
This review found 57 issues worth fixing on athomerecreation.com, 22 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 138 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 142 ms |
| Jun 13, 2026 | 143 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 148 ms |
| Jul 18, 2026 | 150 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 186 ms |
| Aug 15, 2026 | 205 ms |
| Aug 22, 2026 | 212 ms |
| Aug 29, 2026 | 227 ms |
| Sep 5, 2026 | 219 ms |
| Sep 12, 2026 | 219 ms |
| Sep 19, 2026 | 218 ms |
| Sep 26, 2026 | 219 ms |
| Oct 3, 2026 | 229 ms |
| Oct 10, 2026 | 233 ms |
| Oct 17, 2026 | 237 ms |
| Oct 24, 2026 | 237 ms |
| Oct 31, 2026 | 213 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.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.7 s
4.3 s
Speed
Use efficient cache lifetimes
8.8 s · 3.8 MB66 files are served with short cache lifetimes, so returning visitors download them again (3.8 MB).
Reduce unused JavaScript
6.3 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.
Improve image delivery
1.8 s · 1.7 MB22 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
2.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Reduce unused CSS
1.2 s · 254 KiBAbout 254 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40. 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 (Google Tag Manager, Olark and Accessibe Accessibility Overlay and others), adding 2.0 MB and 1.3 s of main-thread time.
Google Tag Manager adds 572 ms
572 msGoogle Tag Manager costs a phone 572 ms of main-thread work and 1.0 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.
Minify JavaScript
450 ms · 82 KiB82 KiB could be saved by minifying JavaScript.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Olark adds 289 ms
289 msOlark costs a phone 289 ms of main-thread work and 437 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 228 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 13 ms
13 msYour server sent the HTML in 13 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 CLS: 1.14
1.14For real visitors the layout shifts by 1.14 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 19.8 s
19.8 sYour largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pool covers”.
Time to Interactive: 26.2 s
26.2 sThe page becomes fully interactive after 26.2 s. Good is under 3.8 s.
First Contentful Paint: 5.6 s
5.6 sThe first text or image appears after 5.6 s on a phone. Good is under 1.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 654 ms
654 msScripts block taps and scrolling for 654 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 204 ms
204 msReal visitors wait 204 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 64% slower for real visitors
+64%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 138 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
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.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 8.1 MB in 119 requests
8.1 MBYour homepage downloads 8.1 MB in 119 requests on a phone: images 4.4 MB (47), scripts 2.8 MB (36) and other files 315 KiB (26). Under 2 MB keeps phones on slow connections fast.
15 images in older formats
15 images (1.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
An image on the first screen is lazy-loaded
Quatum_Pools-1200px.webp 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).
11 images far larger than shown
473 KiB11 images are downloaded at several times the size a phone draws them, for example media.nl at 1,920 px wide, shown at 360 px. Resized copies would save about 473 KiB.
About 2.3 g of CO₂ per visit
2.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.29 g of CO₂e: 274.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Interactive controls must not be nested (19 elements)
Interactive controls must not be nested: 19 elements on the page fail this check, rated serious by axe-core.
Links must have discernible text (18 elements)
Links must have discernible text: 18 elements on the page fail this check, rated serious by axe-core.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
7 form fields without a label
7 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (40 characters)
Your meta description is only 40 characters: “Above Ground Pools and supplies for sale”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
325 internal links, 5 external
The homepage links to 325 pages on athomerecreation.com and 5 external pages.
4 checks passed
Title: 65 characters
Your title is a healthy 65 characters: “At Home Recreation - Above Ground Pools, Spas and Patio Furniture”.
Canonical URL set
The canonical URL is https://www.athomerecreation.com/.
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.athomerecreation.com/sitemap.xml.
AI search readiness
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.athomerecreation.com/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 (1,385 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a title
https://www.athomerecreation.com/pools and https://www.athomerecreation.com/pools/above-ground-pools/above-ground-round-pools-for-sale have no <title>, so Google invents the link text in results.
2 pages without a meta description
https://www.athomerecreation.com/pools and https://www.athomerecreation.com/pools/above-ground-pools/above-ground-round-pools-for-sale have no meta description, so Google writes the search snippet from whatever text it finds.
10 links to non-canonical URLs
Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://www.athomerecreation.com/pools/above-ground-pools/above-ground-round-pools-for-sale/12ft-above-ground-round-pools-for-sale, whose canonical is https://www.athomerecreation.com/pools/above-ground-pools/above-ground-round-pools-for-sale/12ft-above-ground-round-pools-for-sale?page=1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.athomerecreation.com/pools and https://www.athomerecreation.com/pools/above-ground-pools/above-ground-round-pools-for-sale have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.athomerecreation.com/pools, https://www.athomerecreation.com/pools/above-ground-pools/above-ground-round-pools-for-sale and https://www.athomerecreation.com/pools/above-ground-pools/above-ground-round-pools-for-sale/15ft-above-ground-round-pools-for-sale took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
3 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
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.
Best practices
8 small tap targets
8 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: fbq is not defined”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
A 18-field form
Your longest form asks for 18 fields (0 required). Every extra field lowers completion.
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 769 words of copy
The homepage carries about 769 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call Us 732-955-8288” and “Shop swimming pool packages”.
11 calls to action
The homepage has 11 calls to action, for example “Call Us 732-955-8288”, “Shop swimming pool packages” and “Shop Now”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Xandr (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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
19 other companies contacted
Loading the homepage contacts 19 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 athomerecreation.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Company
- Headquarters
- Hazlet
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on athomerecreation.com, including 24 speed issues, 6 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.