Website review, no card needed

sophiegrace.ca logo

sophiegrace.ca website review

Visit site (opens in a new tab)Reviewed 11 November 202644 issues · 92 checks

This review found 44 issues worth fixing on sophiegrace.ca, 18 of them high impact, across 92 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
3.9 s2.1 sMay 23Nov 73.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.3 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.6 s
Aug 8, 20262.9 s
Aug 15, 20263.2 s
Aug 22, 20263.4 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.6 s
Sep 19, 20263.5 s
Sep 26, 20263.4 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.3 s
Nov 7, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
138 ms113 msMay 23Nov 7121 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026116 ms
May 30, 2026121 ms
Jun 6, 2026121 ms
Jun 13, 2026125 ms
Jun 20, 2026128 ms
Jun 27, 2026129 ms
Jul 4, 2026135 ms
Jul 11, 2026132 ms
Jul 18, 2026129 ms
Jul 25, 2026128 ms
Aug 1, 2026124 ms
Aug 8, 2026128 ms
Aug 15, 2026128 ms
Aug 22, 2026129 ms
Aug 29, 2026129 ms
Sep 5, 2026130 ms
Sep 12, 2026129 ms
Sep 19, 2026128 ms
Sep 26, 2026127 ms
Oct 3, 2026123 ms
Oct 10, 2026121 ms
Oct 17, 2026121 ms
Oct 24, 2026121 ms
Oct 31, 2026120 ms
Nov 7, 2026121 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 sophiegrace.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sophiegrace.ca at 1.1 s1.1 s
  2. sophiegrace.ca at 2.2 s2.2 s
  3. sophiegrace.ca at 3.3 s3.3 s
  4. sophiegrace.ca at 4.4 s4.4 s
  5. sophiegrace.ca at 5.5 s5.5 s
  6. sophiegrace.ca at 6.6 s6.6 s
  7. sophiegrace.ca at 7.7 s7.7 s
  8. sophiegrace.ca at 8.9 s8.9 s

Speed

14 to fix40
  • Reduce unused JavaScript

    4.7 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

  • Main-thread work: 26.0 s

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

  • Use efficient cache lifetimes

    1.5 s · 541 KiB

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

  • Mobile performance score: 40

    40/100

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

  • 4,899 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (alia-prod.com, Clarity and Shopify and others), adding 2.1 MB and 2.3 s of main-thread time.

  • Render-blocking requests

    850 ms

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

  • alia-prod.com adds 466 ms

    466 ms

    alia-prod.com costs a phone 466 ms of main-thread work and 494 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.

  • Minify JavaScript

    450 ms · 57 KiB

    57 KiB could be saved by minifying JavaScript.

  • Shopify adds 406 ms

    406 ms

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

  • Clarity adds 431 ms

    431 ms

    Clarity costs a phone 431 ms of main-thread work and 31 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.

  • 20 long tasks on the main thread

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

  • SocialShopWave adds 251 ms

    251 ms

    SocialShopWave costs a phone 251 ms of main-thread work and 98 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.

  • rebuyengine.com adds 214 ms

    214 ms

    rebuyengine.com costs a phone 214 ms of main-thread work and 300 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

    190 ms · 106 KiB

    About 106 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.

  • Legacy JavaScript

    200 ms · 77 KiB

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

  • Duplicated JavaScript

    100 ms · 18 KiB

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

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

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 21.2 s

    21.2 s

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

  • Time to Interactive: 31.9 s

    31.9 s

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

  • Speed Index: 13.0 s

    13.0 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Largest content (LCP) got 32% slower for real visitors

    +32%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Tap response (INP) held steady for real visitors

    +2%

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

4 checks passed
  • Real-user INP: 104 ms

    104 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 471 ms

    471 ms

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

1 to fix70
  • Page weight: 6.2 MB in 590 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 590 requests on a phone: scripts 2.7 MB (122), other files 1.7 MB (356) and images 1.4 MB (83). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.76 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.76 g of CO₂e: 211.1 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

7 to fixGoogle 8690
  • 38 tap targets too small

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

  • 6 text elements with low contrast

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

  • [role="img"] and [role="image"] elements must have alternative text (6 elements)

    [role="img"] and [role="image"] elements must have alternative text: 6 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 2 form fields without a label

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

  • 2 links without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (15 elements).

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 10078
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “Dress Up. Be Comfortable. Be Yourself. By Women, For Women. – SOPHIEGRACE”.

  • Meta description is long (298 characters)

    Your meta description is 298 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 147 internal links, 14 external

    The homepage links to 147 pages on sophiegrace.ca and 14 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.sophiegrace.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://www.sophiegrace.ca/sitemap.xml.

AI search readiness

100
  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

  • llms.txt published

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

Other pages

1 to fix95
  • 13 pages without a meta description

    https://www.sophiegrace.ca/collections/sale, https://www.sophiegrace.ca/collections/all, https://www.sophiegrace.ca/collections/just-in-love-poem-punch-blackberry, https://www.sophiegrace.ca/collections/best-sellers-2025, https://www.sophiegrace.ca/collections/tops and https://www.sophiegrace.ca/collections/dresses and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

5 to fixGoogle 6566
  • 10 broken images

    10 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/Product/979295891/801956319/square.png?1786991503.

  • 28 small tap targets

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

  • 9 third-party cookies

    9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • Thin social proof

    Social proof on the homepage: 5 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 1,162 words of copy

    The homepage carries about 1,162 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop”, “Shop All” and “Shop By Fabric”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 46 cookies set on arrival

    46

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

  • 68 other companies contacted

    Loading the homepage contacts 68 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 sophiegrace.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 20 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Platmart Color Swatches · Yotpo Product Reviews · Personizely A B Testing Cro · Redo · Loyalty Rewards And Referrals · Trackbee Connect · Microsoft Clarity · Klaviyo Email Marketing Sms · Triplewhale · Fast Product Colors · Loop Returns · Forms · Xo Gallery · adroll.com · trafficmanager.net · shareasale.com · rebuyengine.com · useamp.com · Swym Wishlist Plus

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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on sophiegrace.ca, including 23 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