squishable.ca website review

45 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

52 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

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

4 third-party services load with your homepage (Shopify, Mailchimp and intuit.com and others), adding 295 KiB and 71 ms of main-thread time.

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

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

About 14 KiB of CSS is downloaded but never applied on this page.

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.

Your largest element takes 12.5 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 13.0 s. Good is under 3.8 s.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 87 ms to 102 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 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 201 requests on a phone: images 2.4 MB (46), other files 622 KiB (56) and scripts 328 KiB (76). Under 2 MB keeps phones on slow connections fast.

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

9 images (545 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.

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

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

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

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

Your title is only 13 characters: “Squishable.ca”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 185 pages on squishable.ca and 0 external pages.

Your homepage links to https://www.squishable.ca/collections/picnic-baby-by-squishable, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.squishable.ca/collections/winter-wonderland, https://www.squishable.ca/collections/standard-squishables, https://www.squishable.ca/collections/comfort-food, https://www.squishable.ca/collections/clearance, https://www.squishable.ca/collections/plague-doctor and https://www.squishable.ca/collections/bags-and-accessories and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.squishable.ca/collections/winter-wonderland, https://www.squishable.ca/collections/standard-squishables, https://www.squishable.ca/collections/comfort-food, https://www.squishable.ca/collections/minis, https://www.squishable.ca/collections/clearance and https://www.squishable.ca/collections/alter-egos and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.squishable.ca/collections/comfort-food and https://www.squishable.ca/collections/minis took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 66 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 404 ()”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 398 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager 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 10 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.