Website review, no card needed
orthofeet.com website review
Visit site (opens in a new tab)Reviewed 11 October 202639 issues · 95 checks
This review found 39 issues worth fixing on orthofeet.com, 16 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. 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
83B- #25,242 of 109,350 reviewed websitesbeats 72%
- #16,619 of 61,859 online storesbeats 67%
- #16,121 of 56,401 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 2.1 s |
| Apr 25, 2026 | 2.1 s |
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 203 ms |
| Apr 25, 2026 | 203 ms |
| May 2, 2026 | 202 ms |
| May 9, 2026 | 196 ms |
| May 16, 2026 | 197 ms |
| May 23, 2026 | 199 ms |
| May 30, 2026 | 197 ms |
| Jun 6, 2026 | 197 ms |
| Jun 13, 2026 | 195 ms |
| Jun 20, 2026 | 191 ms |
| Jun 27, 2026 | 192 ms |
| Jul 4, 2026 | 194 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 195 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 199 ms |
| Aug 8, 2026 | 204 ms |
| Aug 15, 2026 | 209 ms |
| Aug 22, 2026 | 211 ms |
| Aug 29, 2026 | 212 ms |
| Sep 5, 2026 | 210 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 216 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 211 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
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.3 s
2.7 s
3.1 s
Speed
Use efficient cache lifetimes
2.5 s · 479 KiB37 files are served with short cache lifetimes, so returning visitors download them again (479 KiB).
Reduce unused JavaScript
2.3 s · 426 KiBAbout 426 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.
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 1.4 MB22 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and truevaultcdn.com and others), adding 1.3 MB and 936 ms of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51 (desktop: 90). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 326 ms
326 msGoogle Tag Manager costs a phone 326 ms of main-thread work and 343 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
300 ms · 25 KiBAbout 25 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.
2,310 HTML elements
The page has 2,310 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 97 ms
97 msKlaviyo costs a phone 97 ms of main-thread work and 305 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.
userway.org adds 48 ms
48 msuserway.org costs a phone 48 ms of main-thread work and 343 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 205 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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).
Duplicated JavaScript
12 KiB12 KiB JavaScript is shipped twice across bundles.
Phones get a much slower page than desktops
Desktop scores 90 but mobile only 51. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.1 s
9.1 sThe first text or image appears after 9.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 26.7 s
26.7 sYour largest element takes 26.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Orthofeet Autumn-Winter 2026 New Collection”.
Time to Interactive: 27.2 s
27.2 sThe page becomes fully interactive after 27.2 s. Good is under 3.8 s.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 279 ms
279 msScripts block taps and scrolling for 279 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 203 ms to 211 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-03, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 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.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 761 ms
761 msReal visitors wait 761 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 8.3 MB in 376 requests
8.3 MBYour homepage downloads 8.3 MB in 376 requests on a phone: media 2.9 MB (2), images 2.3 MB (85) and scripts 1.7 MB (120). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
OTF_HP_WebBanner_Mob_1720x360px_AW26Cover_1026_136f1a5f-2628 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).
1 image in older formats
1 image (85 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.
1 image below the first screen load straight away
1 image further down the page (41 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.34 g of CO₂e: 280.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA attributes must conform to valid values (4 elements)
ARIA attributes must conform to valid values: 4 elements on the page fail this check, rated critical by axe-core.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn'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 (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (12 elements)
ARIA role should be appropriate for the element: 12 elements on the page fail this check, rated minor by axe-core.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“New Season. The Trails Are Ready.”, “New Season. The Trails Are Ready.” and “New Season. The Trails Are Ready.”). One clear main headline is easier for people and search engines.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
443 internal links, 21 external
The homepage links to 443 pages on orthofeet.com and 21 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Orthopedic shoes, insoles, and socks expertly designed to help relieve foot pain and keep you moving. Find your fit and…”.
Title: 55 characters
Your title is a healthy 55 characters: “Orthopedic Shoes and Comfortable Orthotics - Orthofeet®”.
Canonical URL set
The canonical URL is https://www.orthofeet.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://www.orthofeet.com/orthofeetsitemap.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,170 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.orthofeet.com/llms.txt (4 KiB, 5 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.orthofeet.com/discount/EXTRA10 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
4 linked pages hidden from search
https://www.orthofeet.com/pages/shipping-returns-exchange-policy, https://www.orthofeet.com/collections/select-styles-sale, https://www.orthofeet.com/collections/womens-hiking-shoes and https://www.orthofeet.com/collections/womens-heels are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
/ and https://www.orthofeet.com/discount/EXTRA10 all use the title “Orthopedic Shoes and Comfortable Orthotics - Orthofeet®”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://www.orthofeet.com/discount/EXTRA10, https://www.orthofeet.com/pages/shipping-returns-exchange-policy, https://www.orthofeet.com/collections/select-styles-sale, https://www.orthofeet.com/collections/new-arrivals-for-women and https://www.orthofeet.com/collections/womens-heels use the same meta description. A description written for each page earns more clicks.
11 pages without an H1
https://www.orthofeet.com/collections/select-styles-sale, https://www.orthofeet.com/collections/women-shoes, https://www.orthofeet.com/collections/new-arrivals-for-women, https://www.orthofeet.com/collections/sneakers-for-women, https://www.orthofeet.com/collections/casual-shoes-for-women and https://www.orthofeet.com/collections/slippers-for-women and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.orthofeet.com/collections/slippers-for-women, https://www.orthofeet.com/collections/dress-shoes-for-women and https://www.orthofeet.com/collections/orthopedic-clogs-for-women 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.
5 pages slow to respond
https://www.orthofeet.com/collections/dress-shoes-for-women, https://www.orthofeet.com/collections/orthopedic-clogs-for-women, https://www.orthofeet.com/collections/womens-heels, https://www.orthofeet.com/collections/sandals-for-women and https://www.orthofeet.com/collections/orthopedic-mary-jane-shoes took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 168 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example https://s.amazon-adsystem.com/iui3?d=forester-did&ex-fargs=%3Fid%3D7c5d4a87-49ce-988f-afe3-3f2145d1abcb%26type%3D55%26m%3D1&ex-fch=416613&ex-src=https://www.orthofeet.com/&ex-hargs=v%3D1.0%3Bc%3D86214.
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_FAILED”.
2 checks passed
Tap targets are thumb-sized
41 of 47 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 650 words of copy
The homepage carries about 650 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Women's” and “Shop Men's”.
31 calls to action
The homepage has 31 calls to action, for example “Shop Insoles”, “Shop by Category” and “Shop by Condition”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and “Join 3M+ customers”.
Direct contact links
Visitors can reach you directly: 3 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
13 trackers load before any consent
13Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 8 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.
36 cookies set on arrival
36Opening the homepage sets 36 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.
73 other companies contacted
Loading the homepage contacts 73 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 orthofeet.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on orthofeet.com, including 17 speed issues, 2 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.