perfectshaker.ca website review

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

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

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

8 third-party services load with your homepage (Shopify, gemcommerce.com and Klaviyo and others), adding 3.0 MB and 402 ms of main-thread time.

About 199 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 430 ms faster on a phone.

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

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

About 32 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.

1 long task block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.

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

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

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.

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

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

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

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

1 image 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' tap response (inp) went from 100 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 173 requests on a phone: images 2.5 MB (13), other files 685 KiB (74) and scripts 597 KiB (68). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

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

[aria-*] attributes do not have valid values (1 element).

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Elements use prohibited ARIA attributes (5 elements).

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“PerfectShaker”, “LUMA Stainless Steel Shaker with Straw, Insulated…” and “ACTIV Shaker Cup, Stainless Steel, Insulated 24hr…”). One clear main headline is easier for people and search engines.

The homepage links to 88 pages on perfectshaker.ca and 4 external pages.

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.

https://www.perfectshaker.com/en-ca/collections/custom and https://www.perfectshaker.com/collections/custom all use the title “Custom Shaker Bottles, Cups & Protein Shakers | PerfectShaker”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.perfectshaker.com/en-ca/collections/clearance, https://www.perfectshaker.com/en-ca/pages/why-perfectshaker and https://www.perfectshaker.com/en-ca/pages/reorder have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.perfectshaker.com/en-ca/collections/custom and https://www.perfectshaker.com/collections/custom use the same meta description. A description written for each page earns more clicks.

https://www.perfectshaker.com/en-ca/collections/custom-stainless-steel-shaker-cups and https://www.perfectshaker.com/en-ca/pages/reorder have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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 has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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