Website review, no card needed

size.ca logo

size.ca website review

Visit site (opens in a new tab)Reviewed 4 November 202629 issues · 82 checks

This review found 29 issues worth fixing on size.ca, 11 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.3 s977 msMay 16Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
187 ms102 msMay 16Oct 31174 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026120 ms
May 23, 2026118 ms
May 30, 2026115 ms
Jun 6, 2026113 ms
Jun 13, 2026112 ms
Jun 20, 2026112 ms
Jun 27, 2026114 ms
Jul 4, 2026116 ms
Jul 11, 2026116 ms
Jul 18, 2026118 ms
Jul 25, 2026117 ms
Aug 1, 2026119 ms
Aug 8, 2026121 ms
Aug 15, 2026123 ms
Aug 22, 2026129 ms
Aug 29, 2026137 ms
Sep 5, 2026138 ms
Sep 12, 2026138 ms
Sep 19, 2026137 ms
Sep 26, 2026141 ms
Oct 3, 2026146 ms
Oct 10, 2026154 ms
Oct 17, 2026170 ms
Oct 24, 2026177 ms
Oct 31, 2026174 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

Full-page screenshot of size.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. size.ca at 0.4 s0.4 s
  2. size.ca at 0.8 s0.8 s
  3. size.ca at 1.1 s1.1 s
  4. size.ca at 1.5 s1.5 s
  5. size.ca at 1.9 s1.9 s
  6. size.ca at 2.3 s2.3 s
  7. size.ca at 2.6 s2.6 s
  8. size.ca at 3.0 s3.0 s

Speed

5 to fix75
  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 75

    75/100

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

  • Improve image delivery

    150 ms · 682 KiB

    5 images could be 682 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.

  • Use efficient cache lifetimes

    650 ms · 116 KiB

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

  • Shopify adds 24 ms

    24 ms

    Shopify costs a phone 24 ms of main-thread work and 382 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 · 22 KiB

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

  • Reduce unused JavaScript

    130 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, heatmap.com and Dynamic Yield and others), adding 785 KiB and 40 ms of main-thread time.

  • Minify JavaScript

    25 KiB

    25 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    9 KiB

    9 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 169 ms of it running JavaScript. That is comfortably low.

  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 7.7 s

    7.7 s

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

  • Time to Interactive: 7.7 s

    7.7 s

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

  • Tap response (INP) got 47% slower for real visitors

    +47%

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

11 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: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 130 ms

    130 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 316 ms

    316 ms

    Real visitors wait 316 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 114 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 114 requests on a phone: images 1.2 MB (14), scripts 774 KiB (55) and fonts 558 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (156 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.

  • About 0.8 g of CO₂ per visit

    0.75 g

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

2 checks passed
  • 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

10 to fixGoogle 7385
  • 25 buttons without a name

    25 buttons have no accessible name, so screen readers announce just “button”.

  • 24 text elements with low contrast

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

  • 24 tap targets too small

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

  • Scrollable region must have keyboard access (21 elements)

    Scrollable region must have keyboard access: 21 elements on the page fail this check, rated serious by axe-core.

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 21 links without text

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

  • 2 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9275
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • Meta description is short (68 characters)

    Your meta description is only 68 characters: “Shop for the latest footwear, clothing & accessories online at size?”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • 203 internal links, 5 external

    The homepage links to 203 pages on size.ca and 5 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://size.ca/.

  • Structured data in place

    Structured data found: Organization 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://size.ca/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://size.ca/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 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 (832 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 6 pages without a meta description

    https://size.ca/pages/faq, https://size.ca/blogs/release-calendar, https://size.ca/collections/footwear, https://size.ca/collections/asics-footwear, https://size.ca/collections/new-balance-footwear and https://size.ca/collections/nike-footwear have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://size.ca/blogs/release-calendar 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 89 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    11 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 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 13 small tap targets

    13 of 58 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_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 431 words of copy

    The homepage carries about 431 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Track My Order”, “Contact” and “Shop Now”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 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.

  • 34 other companies contacted

    Loading the homepage contacts 34 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 size.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Langify · Watchlist · 56071677a62720b5cde4241477474f626e61c35a · Swym Wishlist Plus · sharethis.com · botnot.io · riskified.com · rakutenadvertising.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on size.ca, including 8 speed issues, 3 SEO issues and 2 conversion gaps. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25