Website review, no card needed

activationproducts.com logo

activationproducts.com website review

Visit site (opens in a new tab)Reviewed 18 November 202650 issues · 94 checks

This review found 50 issues worth fixing on activationproducts.com, 21 of them high impact, across 94 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
3.2 s2.1 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.6 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Nov 7, 20262.5 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
255 ms154 msMay 30Nov 14193 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026215 ms
Jun 6, 2026201 ms
Jun 13, 2026212 ms
Jun 20, 2026220 ms
Jun 27, 2026217 ms
Jul 4, 2026236 ms
Jul 11, 2026236 ms
Jul 18, 2026221 ms
Jul 25, 2026197 ms
Aug 1, 2026171 ms
Aug 8, 2026166 ms
Aug 15, 2026179 ms
Aug 22, 2026205 ms
Aug 29, 2026220 ms
Sep 5, 2026203 ms
Sep 12, 2026189 ms
Sep 19, 2026188 ms
Sep 26, 2026186 ms
Oct 3, 2026196 ms
Oct 10, 2026203 ms
Oct 17, 2026230 ms
Oct 24, 2026243 ms
Oct 31, 2026239 ms
Nov 7, 2026237 ms
Nov 14, 2026193 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 activationproducts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. activationproducts.com at 1.3 s1.3 s
  2. activationproducts.com at 2.6 s2.6 s
  3. activationproducts.com at 3.9 s3.9 s
  4. activationproducts.com at 5.2 s5.2 s
  5. activationproducts.com at 6.5 s6.5 s
  6. activationproducts.com at 7.8 s7.8 s
  7. activationproducts.com at 9.1 s9.1 s
  8. activationproducts.com at 10.4 s10.4 s

Speed

15 to fix40
  • Improve image delivery

    5.7 s · 1.2 MB

    5 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.7 s faster on a phone.

  • Reduce unused JavaScript

    5.5 s · 1,001 KiB

    About 1,001 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.

  • Use efficient cache lifetimes

    1.8 s · 366 KiB

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

  • Main-thread work: 17.2 s

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

  • negate.io adds 1.0 s

    1.0 s

    negate.io costs a phone 1.0 s of main-thread work and 40 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 4,095 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (negate.io, Google Tag Manager and Clarity and others), adding 1.6 MB and 2.2 s of main-thread time.

  • Reduce unused CSS

    610 ms · 73 KiB

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

  • Render-blocking requests

    650 ms

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

  • Google Tag Manager adds 283 ms

    283 ms

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

  • Clarity adds 250 ms

    250 ms

    Clarity costs a phone 250 ms of main-thread work and 57 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 250 ms. During a long task the page ignores taps.

  • Klaviyo adds 196 ms

    196 ms

    Klaviyo costs a phone 196 ms of main-thread work and 313 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.

  • azurefd.net adds 84 ms

    84 ms

    azurefd.net costs a phone 84 ms of main-thread work and 334 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

    200 ms · 38 KiB

    Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • Minify JavaScript

    220 ms · 18 KiB

    18 KiB could be saved by minifying JavaScript.

  • 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: 22 ms

    22 ms

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

Core Web Vitals

10 to fix33
  • 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: 39.0 s

    39.0 s

    Your largest element takes 39.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WOULD YOU LIKE 10% OFF ON YOUR FIRST ORDER? YES PLEASE! NO …”.

  • Time to Interactive: 39.3 s

    39.3 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Total Blocking Time: 857 ms

    857 ms

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 246 ms

    246 ms

    Real visitors wait 246 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.3 s

    2.3 s

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

  • 1 image without width and height

    1 image 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 215 ms to 193 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 745 ms

    745 ms

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

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

    -14%

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

  • Cumulative Layout Shift: 0.017

    0.017

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

Images and page weight

3 to fix53
  • Page weight: 37.6 MB in 520 requests

    37.6 MB

    Your homepage downloads 37.6 MB in 520 requests on a phone: media 30.6 MB (1), scripts 2.4 MB (123) and images 2.4 MB (56). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Frame_1618873450.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).

  • 8 images in older formats

    8 images (869 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.

  • About 10.6 g of CO₂ per visit

    10.65 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 8088
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 27 tap targets too small

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

  • Elements must only use permitted ARIA attributes (11 elements)

    Elements must only use permitted ARIA attributes: 11 elements on the page fail this check, rated serious by axe-core.

  • 3 text elements with low contrast

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

  • 10 images without alt text

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

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

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

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

  • ARIA progressbar elements do not have accessible names.

    ARIA progressbar elements do not have accessible names. (1 element).

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 8583
  • No H1 headline

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

  • Meta description is long (308 characters)

    Your meta description is 308 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 3 links with vague text

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

  • 201 internal links, 19 external

    The homepage links to 201 pages on activationproducts.com and 19 external pages.

6 checks passed
  • Title: 33 characters

    Your title is a healthy 33 characters: “Activation Products (US & Canada)”.

  • Canonical URL set

    The canonical URL is https://activationproducts.com/.

  • Structured data in place

    Structured data found: 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://activationproducts.com/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 2 AI crawlers

    Your robots.txt lets ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,226 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://activationproducts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 2 linked pages hidden from search

    https://activationproducts.com/pages/spring-detox and https://activationproducts.com/pages/perfect-detox-bundle-lp are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 1 page without a meta description

    https://activationproducts.com/collections/hormones has no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages share a meta description

    https://activationproducts.com/collections/all, https://activationproducts.com/collections/best-sellers, https://activationproducts.com/collections/perfect-press, https://activationproducts.com/collections/oceans-alive, https://activationproducts.com/collections/perfect-elements and https://activationproducts.com/collections/brain and 7 others use the same meta description. A description written for each page earns more clicks.

  • 11 pages without an H1

    https://activationproducts.com/collections/all, https://activationproducts.com/collections/best-sellers, https://activationproducts.com/collections/perfect-press, https://activationproducts.com/collections/oceans-alive, https://activationproducts.com/collections/perfect-elements and https://activationproducts.com/collections/brain 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 54 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8876
  • 1 broken image

    1 image failed to load on a phone, for example https://vip.activationproducts.com/img/activation-wordmark-white.png.

  • 4 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

  • 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

    30 of 36 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 1,634 words of copy

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

6 checks passed
  • Clear next step on the first screen

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

  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop”, “Shop All” and “Contact”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 191 testimonial or review blocks, 10 customer or partner logos, a star rating, 8 trust badges and “215,000+ Customers”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • 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

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity (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.

  • 33 cookies set on arrival

    33

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

  • 53 other companies contacted

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

Apps on your store

Your storefront loads 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Intelligems A B Testing · Wyllo Formerly Nofraud · Klaviyo Email Marketing Sms · Impact Com · Gorgias Live Chat Helpdesk · Microsoft Clarity · Easylocation · Bixgrow Affiliate · rechargecdn.com · trustpilot.com · amazonaws.com · retention.com · convex.site

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Cobourg

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on activationproducts.com, including 25 speed issues and 3 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

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