Website review, no card needed

arcticspas.com logo

arcticspas.com website review

Visit site (opens in a new tab)Reviewed 21 November 202637 issues · 92 checks

This review found 37 issues worth fixing on arcticspas.com, 10 of them high impact, across 92 checks. The most urgent: render-blocking requests. 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.9 s2.3 sMay 30Nov 142.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Jun 20, 20263.7 s
Jun 27, 20263.8 s
Jul 4, 20263.4 s
Jul 11, 20263.5 s
Jul 18, 20263.8 s
Jul 25, 20264.1 s
Aug 1, 20264.6 s
Aug 8, 20264.6 s
Aug 15, 20264.3 s
Aug 22, 20264.2 s
Aug 29, 20263.9 s
Sep 5, 20263.5 s
Sep 12, 20263.3 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.8 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Oct 31, 20262.7 s
Nov 7, 20262.6 s
Nov 14, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
98 ms92 msMay 30Nov 1493 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 202697 ms
Jun 20, 202696 ms
Jun 27, 202696 ms
Jul 4, 202697 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202695 ms
Aug 1, 202694 ms
Aug 8, 202694 ms
Aug 15, 202695 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202694 ms
Sep 12, 202693 ms
Sep 19, 202694 ms
Sep 26, 202695 ms
Oct 3, 202695 ms
Oct 10, 202695 ms
Oct 17, 202695 ms
Oct 24, 202696 ms
Oct 31, 202696 ms
Nov 7, 202695 ms
Nov 14, 202693 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 arcticspas.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. arcticspas.com at 0.4 s0.4 s
  2. arcticspas.com at 0.8 s0.8 s
  3. arcticspas.com at 1.1 s1.1 s
  4. arcticspas.com at 1.5 s1.5 s
  5. arcticspas.com at 1.9 s1.9 s
  6. arcticspas.com at 2.3 s2.3 s
  7. arcticspas.com at 2.6 s2.6 s
  8. arcticspas.com at 3.0 s3.0 s

Speed

10 to fix84
  • Render-blocking requests

    2.1 s

    24 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.

  • Mobile performance score: 84

    84/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, userway.org and Other Google APIs/SDKs and others), adding 2.8 MB and 303 ms of main-thread time.

  • Reduce unused CSS

    380 ms · 122 KiB

    About 122 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 380 ms faster on a phone.

  • Reduce unused JavaScript

    387 KiB

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

  • Improve image delivery

    337 KiB

    10 images could be 337 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google CDN adds 244 ms

    244 ms

    Google CDN costs a phone 244 ms of main-thread work and 386 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: 2.6 s

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

  • Vimeo adds 0 ms

    0 ms

    Vimeo costs a phone 0 ms of main-thread work and 1.7 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 Fonts adds 2 ms

    2 ms

    Google Fonts costs a phone 2 ms of main-thread work and 619 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.

  • 6 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    18 KiB

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

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

  • Use efficient cache lifetimes

    3 KiB

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

1 checks passed
  • Server response: 68 ms

    68 ms

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

Core Web Vitals

7 to fix67
  • 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: 0.65

    0.65

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

  • Time to Interactive: 13.6 s

    13.6 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 242 ms

    242 ms

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

  • 9 images without width and height

    9 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -2%

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

7 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

    Real visitors wait 1.4 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 FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 511 ms

    511 ms

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

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

    -23%

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

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “We use essential cookies to make this website work. With yo…”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.3 MB in 141 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 141 requests on a phone: images 1.7 MB (24), media 1.7 MB (2) and fonts 860 KiB (46). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.49 g

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

11 to fixGoogle 7887
  • ARIA roles used must conform to valid values (10 elements)

    ARIA roles used must conform to valid values: 10 elements on the page fail this check, rated critical by axe-core.

  • 5 text elements with low contrast

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

  • 5 tap targets too small

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

  • Main landmark should not be contained in another landmark (17 elements)

    Main landmark should not be contained in another landmark: 17 elements on the page fail this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (9 elements)

    All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (8 elements)

    Banner landmark should not be contained in another landmark: 8 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 (4 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 4 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 11 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), 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. (8 elements).

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9289
  • 4 H1 headlines

    There are 4 <h1> headlines (“Hot Tubs”, “Nova” and “Whistler”). One clear main headline is easier for people and search engines.

  • No XML sitemap

    No XML sitemap at https://www.arcticspas.ca/sitemap, so Google discovers your pages only by following links.

  • 6 links with vague text

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

  • 86 internal links, 22 external

    The homepage links to 86 pages on arcticspas.com and 22 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Luxury Hot Tubs & All Weather Pools for the USA. Built for comfort, efficiency, durability, and easy maintenance for th…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Luxury Hot Tubs & All Weather Pools | Arctic Spas | USA”.

  • Canonical URL set

    The canonical URL is https://www.arcticspas.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.

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

  • llms.txt published

    The site publishes https://www.arcticspas.com/llms.txt (4 KiB, 9 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.arcticspas.com/blog, https://www.arcticspas.com/blog/meet-the-redesigned-arctic-spas-app and https://www.arcticspas.com/hot-tubs/whistler have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.arcticspas.com/in/change-store.php has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.arcticspas.com/in/change-store.php has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 7 pages slow to respond

    https://www.arcticspas.com/all-weather-pools, https://www.arcticspas.com/features, https://www.arcticspas.com/in/change-store.php, https://www.arcticspas.com/contact, https://www.arcticspas.com/hot-tubs/nova and https://www.arcticspas.com/hot-tubs/whistler and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 3 JavaScript errors while loading

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

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    16 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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,242 words of copy

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

3 checks passed
  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop”, “Contact” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 8 other companies contacted

    Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 arcticspas.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
Analytics
Google Tag Manager
Hosting
OVHcloud

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 arcticspas.com, including 17 speed issues, 3 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

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