Website review, no card needed

c-m-p.com logo

c-m-p.com website review

Visit site (opens in a new tab)Reviewed 20 November 202639 issues · 84 checks

This review found 39 issues worth fixing on c-m-p.com, 14 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
2.4 s1.8 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.4 s
Oct 31, 20262.3 s
Nov 7, 20262.3 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
77 ms69 msMay 30Nov 1471 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202671 ms
Jun 6, 202671 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202671 ms
Jul 4, 202671 ms
Jul 11, 202673 ms
Jul 18, 202675 ms
Jul 25, 202672 ms
Aug 1, 202672 ms
Aug 8, 202671 ms
Aug 15, 202670 ms
Aug 22, 202672 ms
Aug 29, 202674 ms
Sep 5, 202674 ms
Sep 12, 202676 ms
Sep 19, 202671 ms
Sep 26, 202671 ms
Oct 3, 202671 ms
Oct 10, 202670 ms
Oct 17, 202671 ms
Oct 24, 202671 ms
Oct 31, 202673 ms
Nov 7, 202675 ms
Nov 14, 202671 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 c-m-p.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix48
  • Improve image delivery

    2.7 s · 741 KiB

    10 images could be 741 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

  • Render-blocking requests

    3.0 s

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

  • Reduce unused JavaScript

    1.6 s · 388 KiB

    About 388 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: 48

    48/100

    Your mobile performance score is 48. 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, Hello Bar and Google CDN and others), adding 904 KiB and 590 ms of main-thread time.

  • Reduce unused CSS

    400 ms · 99 KiB

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

  • Google Tag Manager adds 300 ms

    300 ms

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

  • Use efficient cache lifetimes

    150 ms · 211 KiB

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

  • 4 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 533 ms of it running JavaScript. That is comfortably low.

  • Server response: 42 ms

    42 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 13.6 s

    13.6 s

    Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “YOU DON'T HAVE TO FEAR A CHLORINE SHORTAGE MAKE THE SWITCH”.

  • Time to Interactive: 14.5 s

    14.5 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Cumulative Layout Shift: 0.28

    0.28

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

  • Largest content (LCP) got 21% slower for real visitors

    +21%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 73 ms

    73 ms

    Real visitors wait 73 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.

  • Total Blocking Time: 190 ms

    190 ms

    Scripts block the page for only 190 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix65
  • Page weight: 2.4 MB in 88 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 88 requests on a phone: images 1.2 MB (28), scripts 826 KiB (28) and fonts 223 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (764 KiB) 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.

  • 4 images far larger than shown

    209 KiB

    4 images are downloaded at several times the size a phone draws them, for example hot-tub-woman-spa-overlay.jpg at 1,000 px wide, shown at 249 px. Resized copies would save about 209 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (223 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.68 g

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

Accessibility

7 to fixGoogle 7390
  • 8 text elements with low contrast

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

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

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

  • Zoom is disabled

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

  • 6 links without text

    6 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 should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

3 to fixGoogle 7779
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 7 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 88 internal links, 10 external

    The homepage links to 88 pages on c-m-p.com and 10 external pages.

6 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “CMP - Pool Products, Spa and Hot Tub Products - CMP”.

  • Canonical URL set

    The canonical URL is https://c-m-p.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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.c-m-p.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.c-m-p.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 (679 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 2 linked pages hidden from search

    https://www.c-m-p.com/tech and https://www.c-m-p.com/resource-center are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 12 pages without a meta description

    https://www.c-m-p.com/tech, https://www.c-m-p.com/resource-center, https://www.c-m-p.com/find-a-representative, https://www.c-m-p.com/es, https://www.c-m-p.com/pool-products/led-pool-products and https://www.c-m-p.com/pool-products/water-features and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.c-m-p.com/pool-products/pool-sanitizers, whose canonical is https://www.c-m-p.com/pool-spa-sanitizers-under-construction. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://www.c-m-p.com/tech, https://www.c-m-p.com/resource-center, https://www.c-m-p.com/find-a-representative, https://www.c-m-p.com/company-info, https://www.c-m-p.com/pool-products and https://www.c-m-p.com/pool-products/water-features and 5 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 50 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 510 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: “REQUEST INFO” and “WHERE TO BUY”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “REQUEST INFO”, “WHERE TO BUY” and “Learn More”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

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.

  • 8 cookies set on arrival

    8

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 c-m-p.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 Analytics | Google Tag Manager
Hosting
Liquid Web, L.L.C

Company

Headquarters
Tyrone

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on c-m-p.com, including 17 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