Website review, no card needed

capsuletoronto.com logo

capsuletoronto.com website review

Visit site (opens in a new tab)Reviewed 8 November 202634 issues · 76 checks

This review found 34 issues worth fixing on capsuletoronto.com, 13 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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
843 ms636 msMay 16Oct 31759 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026707 ms
May 23, 2026704 ms
May 30, 2026677 ms
Jun 6, 2026667 ms
Jun 13, 2026678 ms
Jun 20, 2026660 ms
Jun 27, 2026662 ms
Jul 4, 2026670 ms
Jul 11, 2026660 ms
Jul 18, 2026673 ms
Jul 25, 2026676 ms
Aug 1, 2026692 ms
Aug 8, 2026728 ms
Aug 15, 2026756 ms
Aug 22, 2026806 ms
Aug 29, 2026798 ms
Sep 5, 2026793 ms
Sep 12, 2026809 ms
Sep 19, 2026819 ms
Sep 26, 2026817 ms
Oct 3, 2026816 ms
Oct 10, 2026791 ms
Oct 17, 2026768 ms
Oct 24, 2026759 ms
Oct 31, 2026759 ms
Real-visitor tap response (INP)75th percentile, phones
84 ms73 msMay 16Oct 3179 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202675 ms
May 23, 202675 ms
May 30, 202674 ms
Jun 6, 202675 ms
Jun 13, 202677 ms
Jun 20, 202675 ms
Jun 27, 202676 ms
Jul 4, 202677 ms
Jul 11, 202675 ms
Jul 18, 202677 ms
Jul 25, 202678 ms
Aug 1, 202678 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202682 ms
Sep 19, 202682 ms
Sep 26, 202683 ms
Oct 3, 202681 ms
Oct 10, 202679 ms
Oct 17, 202679 ms
Oct 24, 202678 ms
Oct 31, 202679 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 capsuletoronto.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. capsuletoronto.com at 0.4 s0.4 s
  2. capsuletoronto.com at 0.8 s0.8 s
  3. capsuletoronto.com at 1.2 s1.2 s
  4. capsuletoronto.com at 1.6 s1.6 s
  5. capsuletoronto.com at 2.0 s2.0 s
  6. capsuletoronto.com at 2.4 s2.4 s
  7. capsuletoronto.com at 2.7 s2.7 s
  8. capsuletoronto.com at 3.1 s3.1 s

Speed

10 to fix44
  • Reduce unused JavaScript

    1.4 s · 251 KiB

    About 251 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Improve image delivery

    1.1 s · 217 KiB

    2 images could be 217 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Signyfyd, Klaviyo and Shopify and others), adding 999 KiB and 1.2 s of main-thread time.

  • Use efficient cache lifetimes

    900 ms · 197 KiB

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

  • Signyfyd adds 946 ms

    946 ms

    Signyfyd costs a phone 946 ms of main-thread work and 280 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.

  • Main-thread work: 3.7 s

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

  • 12 long tasks on the main thread

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

  • Minify JavaScript

    300 ms · 45 KiB

    45 KiB could be saved by minifying JavaScript.

  • Klaviyo adds 167 ms

    167 ms

    Klaviyo costs a phone 167 ms of main-thread work and 308 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.

  • Legacy JavaScript

    250 ms · 30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 10 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • 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: 8 ms

    8 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 13.8 s

    13.8 s

    Your largest element takes 13.8 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.8 s

    13.8 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Total Blocking Time: 680 ms

    680 ms

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

7 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.0 s

    1.0 s

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

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 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: 0.7 s

    0.7 s

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

  • Real-user TTFB: 297 ms

    297 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 4.3 MB in 255 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 255 requests on a phone: images 2.2 MB (45), scripts 1.1 MB (93) and other files 753 KiB (98). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    October_23_2026-FOG-LaceUpRunner-07.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).

  • 4 images far larger than shown

    39 KiB

    4 images are downloaded at several times the size a phone draws them, for example October_10_2026-AndWander-Editorial-fw26-13.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 39 KiB.

  • About 1.2 g of CO₂ per visit

    1.22 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9394
  • 4 tap targets too small

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

  • Hidden but focusable

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

  • 16 links without text

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

2 checks passed
  • Every image has alt text

    All 115 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 3 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 10084
  • Title is short (7 characters)

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 4 H1 headlines

    There are 4 <h1> headlines (“”, “” and “Your cart -”). One clear main headline is easier for people and search engines.

  • 239 internal links, 2 external

    The homepage links to 239 pages on capsuletoronto.com and 2 external pages.

5 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Est. 2004 – Toronto's premier boutique offering an exclusive selection of footwear, designer apparel, and lifestyle ess…”.

  • Canonical URL set

    The canonical URL is https://www.capsuletoronto.com/.

  • 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.capsuletoronto.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (748 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.capsuletoronto.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 2 pages share a title

    / and https://www.capsuletoronto.com/collections/capsule all use the title “Capsule”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.capsuletoronto.com/collections/new-arrivals, https://www.capsuletoronto.com/collections/and-wander and https://www.capsuletoronto.com/collections/capsule have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.capsuletoronto.com/collections/new-arrivals, https://www.capsuletoronto.com/collections/adidas, https://www.capsuletoronto.com/collections/altra, https://www.capsuletoronto.com/collections/and-wander, https://www.capsuletoronto.com/collections/asics and https://www.capsuletoronto.com/collections/as2ov and 8 others have 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 131 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    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 social proof

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

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

    The homepage carries about 462 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “SHOP” and “Contact information”.

  • 4 short forms

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

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.

  • 11 cookies set on arrival

    11

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 capsuletoronto.com, 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
Shopify;Shopify Hong Kong Dollar;Shopify Plus
Hosting
Shopify

Company

Headquarters
Yorkville

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on capsuletoronto.com, including 15 speed issues, 3 SEO issues and 3 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