squishcandies.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and JSDelivr CDN and others), adding 1.4 MB and 255 ms of main-thread time.

About 322 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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

6 KiB JavaScript is shipped twice across bundles.

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 4.7 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 4.7 s. Good is under 3.8 s.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.9 MB in 478 requests on a phone: other files 1.2 MB (220), scripts 1.1 MB (170) and images 1.1 MB (30). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Squish_Advent2026_Hero_Front_1.jpg at 2,200 px wide, shown at 390 px. Resized copies would save about 102 KiB.

1 image further down the page (142 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Alternative text of images should not be repeated as text: 15 elements on the page fail this check, rated minor by axe-core.

Your canonical URL points to squishcandies.ca, not squishcandies.com, so Google may credit that host instead.

There are 2 <h1> headlines (“” and “24 DAYS OF SWEET SURPRISES!”). One clear main headline is easier for people and search engines.

The homepage links to 110 pages on squishcandies.com and 14 external pages.

https://squishcandies.com/collections/all, https://squishcandies.com/policies/shipping-policy and https://squishcandies.com/pages/wholesale-1 have no meta description, so Google writes the search snippet from whatever text it finds.

https://squishcandies.com/pages/wholesale-1 has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Social proof on the homepage: 123 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 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 824 words of visible text.

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