Website review, no card needed
shoegumi.com website review
Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 77 checks
This review found 34 issues worth fixing on shoegumi.com, 9 of them high impact, across 77 checks. The most urgent: page weight: 34.1 MB in 659 requests. 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
75C- #70,774 of 107,092 reviewed websitesbeats 30%
- #44,828 of 60,457 online storesbeats 22%
- #42,393 of 55,149 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
2.3 s · 324 KiBAbout 324 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,514 HTML elements
The page has 5,514 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
450 ms · 1.2 MB24 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, rebuyengine.com and Shopify and others), adding 3.0 MB and 751 ms of main-thread time.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
740 ms · 131 KiBAbout 131 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 740 ms faster on a phone.
Shopify adds 190 ms
190 msShopify costs a phone 190 ms of main-thread work and 1.6 MB 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.
Klaviyo adds 279 ms
279 msKlaviyo costs a phone 279 ms of main-thread work and 608 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 239 ms
239 msrebuyengine.com costs a phone 239 ms of main-thread work and 652 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.
Use efficient cache lifetimes
150 ms · 67 KiB11 files are served with short cache lifetimes, so returning visitors download them again (67 KiB).
Legacy JavaScript
150 ms · 48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 157 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 6 KiB6 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Duplicated JavaScript
27 KiB27 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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 26.2 s
26.2 sYour largest element takes 26.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “STAY IN TOUCH!”.
Time to Interactive: 27.0 s
27.0 sThe page becomes fully interactive after 27.0 s. Good is under 3.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 194 ms
194 msScripts block the page for only 194 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 34.1 MB in 659 requests
34.1 MBYour homepage downloads 34.1 MB in 659 requests on a phone: media 26.8 MB (2), images 3.5 MB (166) and scripts 1.7 MB (243). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
121 KiB1 image is downloaded at several times the size a phone draws it, for example ac.svg at 1,000 px wide, shown at 24 px. Resized copies would save about 121 KiB.
1 image below the first screen load straight away
1 image further down the page (114 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 9.7 g of CO₂ per visit
9.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.66 g of CO₂e: 1159.2 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
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
49 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: 49 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Canonical points to another host
Your canonical URL points to shoegummi.com, not shoegumi.com, so Google may credit that host instead.
Structured data has 3 problems
Structured data found (BreadcrumbList, Organization and WebSite) but with 3 problems, for example “Organization: sameAs is not an absolute URL ("@shoegummi")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
One H1 headline
Your <h1> is empty.
87 internal links, 2 external
The homepage links to 87 pages on shoegumi.com and 2 external pages.
4 checks passed
Meta description: 104 characters
Your meta description is 104 characters: “Wear high heels up 4x longer! Reduce pressure on the balls of the feet. Wear High Heels more comfortable”.
Title: 41 characters
Your title is a healthy 41 characters: “SHOE GUMMI | HIGH HEEL COMFORT AWAITS YOU”.
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://shoegumi.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://shoegumi.com/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 (1,213 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without a meta description
https://shoegumi.com/pages/print-to-size, https://shoegumi.com/policies/privacy-policy, https://shoegumi.com/policies/refund-policy, https://shoegumi.com/policies/terms-of-service, https://shoegumi.com/policies/shipping-policy and https://shoegumi.com/pages/faqs and 2 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 36 found) and read each the way a search engine does.
6 checks passed
Linked pages load
9 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.
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 9 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
163 of 168 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: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,884 words of copy
The homepage carries about 1,884 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BUY NOW” and “SHOP YOUR OCCASION”.
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “BUY NOW” and “SHOP YOUR OCCASION”.
6 short forms
6 short forms (2 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
9 cookies set on arrival
9Opening the homepage sets 9 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 shoegumi.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Instafeed · Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Bixgrow Affiliate · afterpay.com · avada.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
- Hosting
- Shopify
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 shoegumi.com, including 14 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.