shopatshowcasecanada.com website review

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

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

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

18 images could be 1.3 MB 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, Klevu Search and Noibu and others), adding 1.2 MB and 882 ms of main-thread time.

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

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

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

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

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

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

3 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.0 MB in 339 requests on a phone: images 2.4 MB (34), scripts 1.5 MB (130) and other files 809 KiB (116). Under 2 MB keeps phones on slow connections fast.

rainbowdumpling_170x.gif weighs 601 KiB. On a phone connection a single image that size takes seconds.

W44-MobileHeroSpots-10263.jpg 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).

1 image (601 KiB) is 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.

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

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

10 elements hidden from screen readers can still receive keyboard focus.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 1,826 pages on shopatshowcasecanada.com and 18 external pages.

Your Organization JSON-LD is missing logo, 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.

Your homepage links to https://ca.shopatshowcase.com/collections/black-friday-2025, which answers with an error. Visitors hit a dead end and search engines drop it.

https://ca.shopatshowcase.com/products/orb-curiosities-smushers-toy-bling-bag-1pc-ships-assorted-order-online-free-shipping-or-shop-in-store declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://ca.shopatshowcase.com/products/orb-curiosities-smushers-toy-bling-bag-1pc-ships-assorted-order-online-free-shipping-or-shop-in-store all use the title “Showcase - Home Of The Hottest Trends”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ca.shopatshowcase.com/pages/flash-sales, https://ca.shopatshowcase.com/pages/flyer and https://ca.shopatshowcase.com/collections/all-new-arrivals have no meta description, so Google writes the search snippet from whatever text it finds.

https://ca.shopatshowcase.com/pages/squishies, https://ca.shopatshowcase.com/products/crunch-squish-candy-series-crunchy-squishy-stress-ball-fidget-toy-1pc-color-ships-assorted-order-online-free-shipping-or-shop-in-store, https://ca.shopatshowcase.com/products/glitter-mystery-bao-bun-big-7in-dumpling-squishy-fidget-toy-1pc-order-online-free-shipping-or-shop-in-store, https://ca.shopatshowcase.com/products/mystery-dumpling-bao-bun-fidget-squishy-24-day-countdown-calendar-24pc, https://ca.shopatshowcase.com/products/sugar-squishies-mini-maltose-fidget-toys-24-day-advent-countdown-calendar-24pc-order-online-free-shipping-or-shop-in-store and https://ca.shopatshowcase.com/products/taba-squishies-fidget-toys-24-day-countdown-calendar-24pc-order-online-free-shipping-or-shop-in-store and 1 other use the same meta description. A description written for each page earns more clicks.

https://ca.shopatshowcase.com/pages/store-locator, https://ca.shopatshowcase.com/pages/flash-sales, https://ca.shopatshowcase.com/pages/squishies, https://ca.shopatshowcase.com/pages/flyer, https://ca.shopatshowcase.com/collections/all-new-arrivals and https://ca.shopatshowcase.com/products/crunch-squish-candy-series-crunchy-squishy-stress-ball-fidget-toy-1pc-color-ships-assorted-order-online-free-shipping-or-shop-in-store and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “myInit is not defined”.

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

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

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 3 testimonial or review blocks. 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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 757 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 mores (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 28 cookies (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 53 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.