Website review, no card needed
marysquare.com website review
Visit site (opens in a new tab)Reviewed 19 November 202635 issues · 91 checks
This review found 35 issues worth fixing on marysquare.com, 16 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
84B- #21,515 of 119,792 reviewed websitesbeats 77%
- #13,960 of 67,919 online storesbeats 73%
- #13,547 of 61,905 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.9 s |
| Nov 14, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 115 ms |
| Jun 6, 2026 | 115 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 129 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 111 ms |
| Sep 5, 2026 | 114 ms |
| Sep 12, 2026 | 120 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 122 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 129 ms |
| Oct 24, 2026 | 130 ms |
| Oct 31, 2026 | 130 ms |
| Nov 7, 2026 | 127 ms |
| Nov 14, 2026 | 123 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
1.4 s
2.7 s
4.1 s
5.5 s
6.8 s
8.2 s
9.5 s
10.9 s
Speed
Improve image delivery
1.6 s · 8.6 MB40 images could be 8.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused JavaScript
4.5 s · 866 KiBAbout 866 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Use efficient cache lifetimes
3.1 s · 682 KiB20 files are served with short cache lifetimes, so returning visitors download them again (682 KiB).
Main-thread work: 8.1 s
A phone's processor spends 8.1 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,520 HTML elements
The page has 4,520 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 (Klaviyo, Shopify and Clarity and others), adding 2.3 MB and 1.1 s of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms16 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused CSS
450 ms · 132 KiBAbout 132 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Klaviyo adds 255 ms
255 msKlaviyo costs a phone 255 ms of main-thread work and 662 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.
Shopify adds 234 ms
234 msShopify costs a phone 234 ms of main-thread work and 611 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.
route.com adds 219 ms
219 msroute.com costs a phone 219 ms of main-thread work and 543 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.
azurefd.net adds 58 ms
58 msazurefd.net costs a phone 58 ms of main-thread work and 335 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 247 ms. During a long task the page ignores taps.
Legacy JavaScript
200 ms · 44 KiBPolyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
16 KiB16 KiB could be saved by minifying CSS.
Duplicated JavaScript
10 KiB10 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 JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 103.8 s
103.8 sYour largest element takes 103.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 18.9 s
18.9 sVisually, the page fills in at 18.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 108.7 s
108.7 sThe page becomes fully interactive after 108.7 s. Good is under 3.8 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 258 ms
258 msScripts block taps and scrolling for 258 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 115 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.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: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 145 ms
145 msReal visitors wait 145 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: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 383 ms
383 msReal visitors wait 383 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).
Images and page weight
Page weight: 30.1 MB in 642 requests
30.1 MBYour homepage downloads 30.1 MB in 642 requests on a phone: images 25.8 MB (121), scripts 2.2 MB (147) and other files 1.6 MB (325). Under 2 MB keeps phones on slow connections fast.
15 images over 500 KB
15 images weigh 10.6 MB together. On a phone connection a single image that size takes seconds.
23 images far larger than shown
11.1 MB23 images are downloaded at several times the size a phone draws them, for example 78307_4.jpg at 2,100 px wide, shown at 154 px. Resized copies would save about 11.1 MB.
1 image below the first screen load straight away
1 image further down the page (59 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 8.5 g of CO₂ per visit
8.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.53 g of CO₂e: 1023.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
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (3 elements)
Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6, h1 → h3 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 128 images in the HTML carry an alt attribute.
58 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 58 passed and 5 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
477 internal links, 3 external
The homepage links to 477 pages on marysquare.com and 3 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Mary Square is a lifestyle brand dedicated to inspiring women to celebrate each day. Shop beautifully designed apparel,…”.
Title: 46 characters
Your title is a healthy 46 characters: “Women’s Apparel, Pajamas & Gifts | Mary Square”.
Canonical URL set
The canonical URL is https://marysquare.com/.
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://marysquare.com/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,722 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://marysquare.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://marysquare.com/products/sarah-dress-lacecap-white and https://marysquare.com/collections/all-holiday, which answer with an error. Visitors hit a dead end and search engines drop them.
6 pages share a meta description
https://marysquare.com/policies/shipping-policy, https://marysquare.com/collections/all-holiday-home-gifts, https://marysquare.com/collections/wreath-ribbon and https://marysquare.com/collections/tidings-toile use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://marysquare.com/collections/dresses, https://marysquare.com/collections/pajamas-sleepwear, https://marysquare.com/products/riley-dress-ivy-script-gold, https://marysquare.com/products/riley-dress-lacecap-white, https://marysquare.com/products/adelyn-dress-thistle-vines-sand and https://marysquare.com/collections/holiday-pajamas and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://marysquare.com/products/riley-dress-ivy-script-gold, https://marysquare.com/products/riley-dress-lacecap-white, https://marysquare.com/products/adelyn-dress-thistle-vines-sand, https://marysquare.com/collections/holiday-apparel, https://marysquare.com/collections/all-holiday-home-gifts and https://marysquare.com/collections/tidings-toile have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://marysquare.com/policies/shipping-policy took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 145 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 13 pages that loaded have a meta description.
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 13 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://cdn.klaviyomail.com/company/TPBhq3/images/38dcf4d1-84f4-4c69-af15-fbcad7762df4.jpeg.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
81 of 83 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 23 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 659 words of copy
The homepage carries about 659 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 NOW”.
76 calls to action
The homepage has 76 calls to action, for example “SHOP BY STYLE”, “Shop All” and “SHOP BY COLLECTION”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
30 cookies set on arrival
30Opening the homepage sets 30 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.
57 other companies contacted
Loading the homepage contacts 57 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 marysquare.com, 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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Sa Variants · Trusted Faq · Microsoft Clarity · Instafeed · Wair Size Fit Recommendation · Okendo · Awin Affiliate Marketing · Powerful Form Builder · Gorgias Live Chat Helpdesk · Userway Website Accessibility · Klaviyo Email Marketing Sms · Stape Remix · Navidium Shipping Protection · route.com · cloudfront.net
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
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Apex
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on marysquare.com, including 19 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.