getproactiv.ca website review

Signyfyd costs a phone 1.2 s of main-thread work and 263 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.

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

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

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

8 third-party services load with your homepage (Signyfyd, Yotpo and rebuyengine.com and others), adding 2.7 MB and 2.2 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

Yotpo costs a phone 353 ms of main-thread work and 482 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.

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

rebuyengine.com costs a phone 153 ms of main-thread work and 712 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.

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

Shopify costs a phone 88 ms of main-thread work and 438 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.

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

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

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

18 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

Your homepage downloads 8.9 MB in 456 requests on a phone: images 3.1 MB (120), scripts 3.0 MB (160) and media 1.2 MB (1). Under 2 MB keeps phones on slow connections fast.

26 images (2.8 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.

CR_2650_CA_Perks_Mobile.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 further down the page (741 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example CA-Gentle3-stepCarousel1_5943dc75-5b6c-4989-b3a4-8f005de4bc7 at 2,000 px wide, shown at 126 px. Resized copies would save about 336 KiB.

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

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 element has a tabindex above 0, which scrambles the keyboard order.

1 image has no alt text, which hurts accessibility and image search.

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

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

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your page has no <title>, so Google has to invent the blue link in search results.

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

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 215 pages on getproactiv.ca and 10 external pages.

https://getproactiv.ca/collections/best-sellers, https://getproactiv.ca/pages/perks, https://getproactiv.ca/customer_authentication/redirect, https://getproactiv.ca/collections/all, https://getproactiv.ca/collections/shop-all and https://getproactiv.ca/collections/exclusive-bundles and 9 others have no <title>, so Google invents the link text in results.

https://getproactiv.ca/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://getproactiv.ca/collections/best-sellers, https://getproactiv.ca/pages/perks, https://getproactiv.ca/customer_authentication/redirect, https://getproactiv.ca/collections/all, https://getproactiv.ca/collections/shop-all and https://getproactiv.ca/collections/exclusive-bundles and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://getproactiv.ca/pages/perks, https://getproactiv.ca/customer_authentication/redirect, https://getproactiv.ca/collections/all and https://getproactiv.ca/pages/quiz have no <h1> headline, so visitors and search engines get no clear main topic.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 877 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 32 cookies, 1 of them by other companies (measured from a US location before any click).

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