Website review, no card needed
fitmyfoot.com website review
Visit site (opens in a new tab)Reviewed 5 November 202637 issues · 80 checks
This review found 37 issues worth fixing on fitmyfoot.com, 12 of them high impact, across 80 checks. The most urgent: main-thread work: 21.6 s. 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
81B- #41,966 of 125,974 reviewed websitesbeats 61%
- #27,616 of 70,319 online storesbeats 54%
- #26,594 of 63,864 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 144 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 135 ms |
| Jun 27, 2026 | 131 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 130 ms |
| Aug 1, 2026 | 129 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 134 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 134 ms |
| Sep 5, 2026 | 135 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 131 ms |
| Oct 3, 2026 | 131 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 139 ms |
| Oct 31, 2026 | 138 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
2.3 s
4.6 s
6.9 s
9.2 s
11.5 s
13.9 s
16.2 s
18.5 s
Speed
Main-thread work: 21.6 s
A phone's processor spends 21.6 s on main-thread work while loading, 8.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 1.3 s
1.3 sShopify costs a phone 1.3 s of main-thread work and 610 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 40
40/100Your mobile performance score is 40. 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 (Shopify, Klaviyo and Yotpo and others), adding 1.3 MB and 3.2 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.
Klaviyo adds 833 ms
833 msKlaviyo costs a phone 833 ms of main-thread work and 334 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.
Render-blocking requests
850 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Yotpo adds 801 ms
801 msYotpo costs a phone 801 ms of main-thread work and 236 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 JavaScript
496 KiBAbout 496 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
200 ms · 256 KiB5 images could be 256 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
300 ms · 67 KiBAbout 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
274 KiB14 files are served with short cache lifetimes, so returning visitors download them again (274 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 25.0 s
25.0 sVisually, the page fills in at 25.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 7.3 s
7.3 sScripts block taps and scrolling for 7.3 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 26.2 s
26.2 sThe page becomes fully interactive after 26.2 s. Good is under 3.8 s.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 144 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 150 ms
150 msReal visitors wait 150 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 610 ms
610 msReal visitors wait 610 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.1 MB in 332 requests
6.1 MBYour homepage downloads 6.1 MB in 332 requests on a phone: images 3.6 MB (19), scripts 1.2 MB (182) and other files 848 KiB (98). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
245 KiB2 images are downloaded at several times the size a phone draws them, for example 1_03b03f6c-3503-4b9d-a049-0bb5c597a5f2.svg at 469 px wide, shown at 150 px. Resized copies would save about 245 KiB.
1 image in older formats
1 image (227 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 1.7 g of CO₂ per visit
1.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.73 g of CO₂e: 207.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“FitMyFoot” and “Custom Insoles Made From YourSmartphone”). One clear main headline is easier for people and search engines.
Meta description is long (287 characters)
Your meta description is 287 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
35 internal links, 13 external
The homepage links to 35 pages on fitmyfoot.com and 13 external pages.
5 checks passed
Title: 52 characters
Your title is a healthy 52 characters: “FitMyFoot - Custom insoles made from your smartphone”.
Canonical URL set
The canonical URL is https://fitmyfoot.com/.
Structured data in place
Structured data found: Organization.
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://fitmyfoot.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (1,463 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fitmyfoot.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://fitmyfoot.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://fitmyfoot.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
9 pages without a meta description
https://fitmyfoot.com/collections/all-insole-products, https://fitmyfoot.com/collections/accessories, https://fitmyfoot.com/pages/in-store-locations, https://fitmyfoot.com/pages/contact-us, https://fitmyfoot.com/customer_authentication/redirect and https://fitmyfoot.com/policies/refund-policy and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://fitmyfoot.com/products/fitmyfoot-mens-sandals and https://fitmyfoot.com/products/fitmyfoot-womens-sandals use the same meta description. A description written for each page earns more clicks.
9 pages without an H1
https://fitmyfoot.com/collections/all-insole-products, https://fitmyfoot.com/products/fitmyfoot-mens-sandals, https://fitmyfoot.com/products/fitmyfoot-womens-sandals, https://fitmyfoot.com/collections/accessories, https://fitmyfoot.com/pages/how-it-works and https://fitmyfoot.com/pages/in-store-locations and 3 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 19 found) and read each the way a search engine does.
3 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.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) undefined”.
2 checks passed
Tap targets are thumb-sized
21 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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,277 words of copy
The homepage carries about 1,277 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: “Get Started”.
9 calls to action
The homepage has 9 calls to action, for example “Shop”, “Contact Us” and “Get Started”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 109 testimonial or review blocks and a star rating.
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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
32 other companies contacted
Loading the homepage contacts 32 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 fitmyfoot.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Triplewhale · Klaviyo Email Marketing Sms · yotpo.com · dwin1.com · shareasale.com · hextom.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
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Phoenix
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on fitmyfoot.com, including 16 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.