Website review, no card needed
squishcandies.ca website review
Visit site (opens in a new tab)Reviewed 20 November 202626 issues · 79 checks
This review found 26 issues worth fixing on squishcandies.ca, 8 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
87B- #8,411 of 122,495 reviewed websitesbeats 90%
- #4,846 of 69,177 online storesbeats 90%
- #4,695 of 63,017 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 804 ms |
| Jun 6, 2026 | 796 ms |
| Jun 13, 2026 | 771 ms |
| Jun 20, 2026 | 799 ms |
| Jun 27, 2026 | 825 ms |
| Jul 4, 2026 | 811 ms |
| Jul 11, 2026 | 854 ms |
| Jul 18, 2026 | 818 ms |
| Jul 25, 2026 | 782 ms |
| Aug 1, 2026 | 798 ms |
| Aug 8, 2026 | 806 ms |
| Aug 15, 2026 | 849 ms |
| Aug 22, 2026 | 854 ms |
| Aug 29, 2026 | 831 ms |
| Sep 5, 2026 | 811 ms |
| Sep 12, 2026 | 794 ms |
| Sep 19, 2026 | 794 ms |
| Sep 26, 2026 | 845 ms |
| Oct 3, 2026 | 847 ms |
| Oct 10, 2026 | 862 ms |
| Oct 17, 2026 | 870 ms |
| Oct 24, 2026 | 800 ms |
| Oct 31, 2026 | 802 ms |
| Nov 7, 2026 | 787 ms |
| Nov 14, 2026 | 768 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 106 ms |
| Jun 6, 2026 | 105 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 106 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 106 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 116 ms |
| Sep 12, 2026 | 114 ms |
| Sep 19, 2026 | 118 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 122 ms |
| Oct 24, 2026 | 121 ms |
| Oct 31, 2026 | 120 ms |
| Nov 7, 2026 | 121 ms |
| Nov 14, 2026 | 117 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.7 s
6.5 s
Speed
Reduce unused JavaScript
1.3 s · 289 KiBAbout 289 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Improve image delivery
500 ms · 563 KiB8 images could be 563 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and JSDelivr CDN and others), adding 1.3 MB and 240 ms of main-thread time.
Render-blocking requests
300 ms16 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
2,751 HTML elements
The page has 2,751 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 789 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 116 ms
116 msShopify costs a phone 116 ms of main-thread work and 903 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.
Reduce unused CSS
150 ms · 46 KiBAbout 46 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.
Use efficient cache lifetimes
50 ms · 30 KiB28 files are served with short cache lifetimes, so returning visitors download them again (30 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
6 KiB6 KiB JavaScript is shipped twice across bundles.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.0 s
13.0 sYour largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 13.0 s
13.0 sThe page becomes fully interactive after 13.0 s. Good is under 3.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 106 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 369 ms
369 msReal visitors wait 369 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 5 ms
5 msScripts block the page for only 5 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.7 MB in 411 requests
3.7 MBYour homepage downloads 3.7 MB in 411 requests on a phone: images 1.1 MB (29), other files 1.1 MB (155) and scripts 1.1 MB (170). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 126.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Form elements must have labels (1 element)
Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.
35 text elements with low contrast
35 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
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 (16 elements)
Alternative text of images should not be repeated as text: 16 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“”, “Advent Calendar — NOW $49.99” and “ADVENT CALENDAR — $49.99”). One clear main headline is easier for people and search engines.
118 internal links, 11 external
The homepage links to 118 pages on squishcandies.ca and 11 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Rediscover your love of candy with Squish's variety of vegan and traditional gummies made with real fruit extracts and …”.
Title: 63 characters
Your title is a healthy 63 characters: “Squish Candy | Artfully Crafted Gummies – SQUISH Candies Canada”.
Canonical URL set
The canonical URL is https://www.squishcandies.ca/.
Structured data in place
Structured data found: Organization, ProductGroup and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.squishcandies.ca/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,502 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.squishcandies.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://www.squishcandies.ca/collections/all, https://www.squishcandies.ca/policies/shipping-policy and https://www.squishcandies.ca/pages/wholesale-1 have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.squishcandies.ca/pages/wholesale-1 has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 823 words of copy
The homepage carries about 823 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP THE DEAL”.
7 calls to action
The homepage has 7 calls to action, for example “SHOP ALL 😋”, “SHOP THE DEAL” and “Start mixing”.
12 short forms
12 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 123 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
6 trackers load before any consent
6Before 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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies (measured from a US location before any click).
No consent tool detected
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.
32 other companies contacted
Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at squishcandies.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- 10 Shopify Products;Shopify;Shopify Local Pickup;Shopify Plus;Shopify POS
- Hosting
- Shopify
Company
- Headquarters
- Westmount
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on squishcandies.ca, including 13 speed issues, 1 SEO issue and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.