aedshop.ca website review

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

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

27 images could be 556 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

8 third-party services load with your homepage (Shopify, Google Tag Manager and Google CDN and others), adding 968 KiB and 524 ms of main-thread time.

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

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

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

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

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

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

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

6 KiB could be saved by minifying CSS.

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.

3 KiB could be saved by minifying JavaScript.

2 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

Your homepage downloads 3.0 MB in 305 requests on a phone: scripts 958 KiB (132), images 934 KiB (48) and other files 697 KiB (99). Under 2 MB keeps phones on slow connections fast.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

Your title is 68 characters, so Google will cut it off around 60: “AEDShop: AEDs (Defibrillators), Pads, Batteries & Cabinets in Canada”.

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

The homepage links to 343 pages on aedshop.ca and 5 external pages.

https://aedshop.ca/fr, https://aedshop.ca/collections/aed-units, https://aedshop.ca/pages/manufacturer, https://aedshop.ca/collections/zoll-aed-units, https://aedshop.ca/collections/philips-aed-units and https://aedshop.ca/collections/cardiac-science-aed-units and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The homepage has only about 57 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.