Website review, no card needed
footwearetc.com website review
Visit site (opens in a new tab)Reviewed 5 November 202649 issues · 98 checks
This review found 49 issues worth fixing on footwearetc.com, 18 of them high impact, across 98 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
71C- #100,993 of 125,453 reviewed websitesbeats 17%
- #61,467 of 70,182 online storesbeats 10%
- #56,987 of 63,766 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 177 ms |
| May 23, 2026 | 196 ms |
| May 30, 2026 | 206 ms |
| Jun 6, 2026 | 214 ms |
| Jun 13, 2026 | 220 ms |
| Jun 20, 2026 | 219 ms |
| Jun 27, 2026 | 220 ms |
| Jul 4, 2026 | 217 ms |
| Jul 11, 2026 | 217 ms |
| Jul 18, 2026 | 222 ms |
| Jul 25, 2026 | 222 ms |
| Aug 1, 2026 | 223 ms |
| Aug 8, 2026 | 223 ms |
| Aug 15, 2026 | 221 ms |
| Aug 22, 2026 | 221 ms |
| Aug 29, 2026 | 221 ms |
| Sep 5, 2026 | 222 ms |
| Sep 12, 2026 | 218 ms |
| Sep 19, 2026 | 211 ms |
| Sep 26, 2026 | 205 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 201 ms |
| Oct 17, 2026 | 189 ms |
| Oct 24, 2026 | 186 ms |
| Oct 31, 2026 | 171 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.0 s
2.1 s
3.1 s
4.1 s
5.1 s
6.2 s
7.2 s
8.2 s
Speed
Use efficient cache lifetimes
1.3 s · 587 KiB32 files are served with short cache lifetimes, so returning visitors download them again (587 KiB).
Render-blocking requests
1.6 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Main-thread work: 10.9 s
A phone's processor spends 10.9 s on main-thread work while loading, 5.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,750 HTML elements
The page has 6,750 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 3.3 MB97 images could be 3.3 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 (cloudfront.net, Klaviyo and Google Tag Manager and others), adding 1.9 MB and 2.0 s of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 643 KiBAbout 643 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Klaviyo adds 332 ms
332 msKlaviyo costs a phone 332 ms of main-thread work and 519 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.
cloudfront.net adds 362 ms
362 mscloudfront.net costs a phone 362 ms of main-thread work and 118 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.
Google Tag Manager adds 300 ms
300 msGoogle Tag Manager costs a phone 300 ms of main-thread work and 331 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.
Attentive adds 277 ms
277 msAttentive costs a phone 277 ms of main-thread work and 228 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.
Google CDN adds 207 ms
207 msGoogle CDN costs a phone 207 ms of main-thread work and 298 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 244 ms. During a long task the page ignores taps.
Reduce unused CSS
50 ms · 63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 50 ms faster on a phone.
Minify CSS
50 ms · 15 KiB15 KiB could be saved by minifying CSS.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Speed Index: 14.2 s
14.2 sVisually, the page fills in at 14.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.3 s
22.3 sThe page becomes fully interactive after 22.3 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 279 ms
279 msReal visitors wait 279 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 177 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (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: 682 ms
682 msReal visitors wait 682 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.031
0.031The layout barely moves while loading (CLS 0.031, good is under 0.1).
Images and page weight
Page weight: 9.5 MB in 657 requests
9.5 MBYour homepage downloads 9.5 MB in 657 requests on a phone: images 5.4 MB (142), scripts 2.2 MB (143) and other files 1.4 MB (342). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
770 KiB6 images are downloaded at several times the size a phone draws them, for example Autogenerated_4b6b71929b344a3786d54b4f1d8dd7f8.jpg at 1,500 px wide, shown at 149 px. Resized copies would save about 770 KiB.
18 images in older formats
18 images (1.5 MB) are 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.
5 images below the first screen load straight away
5 images further down the page (823 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.68 g of CO₂e: 322.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 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 (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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 112 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 9 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“In-Store & Online” and “Stay in touch with us.”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
621 internal links, 9 external
The homepage links to 621 pages on footwearetc.com and 9 external pages.
6 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Shop online with Footwear etc. to find a wide selection of high quality comfort shoe brands for both women and men. Fin…”.
Title: 64 characters
Your title is a healthy 64 characters: “Footwear etc. | Comfort Shoes for Women and Men | Athletic Shoes”.
Canonical URL set
The canonical URL is https://footwearetc.com/.
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.
XML sitemap found
Your XML sitemap is reachable at https://footwearetc.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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 (2,998 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://footwearetc.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://footwearetc.com/collections/vitamin-inhalers 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.
2 pages share a title
/ and https://footwearetc.com/collections/vitamin-inhalers all use the title “Footwear etc. | Comfort Shoes for Women and Men | Athletic Shoes”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://footwearetc.com/collections/new-trending-shoes-accessories has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://footwearetc.com/collections/vitamin-inhalers, https://footwearetc.com/collections/new-trending-shoes-accessories, https://footwearetc.com/collections/asics, https://footwearetc.com/collections/kizik-handsfree-shoes, https://footwearetc.com/collections/birkenstock and https://footwearetc.com/collections/uggs and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://footwearetc.com/collections/asics has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 179 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.
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
36 small tap targets
36 of 156 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
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
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.
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.
Thin social proof
Social proof on the homepage: 79 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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,502 words of copy
The homepage carries about 1,502 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
195 calls to action
The homepage has 195 calls to action, for example “Sign in / Join Account”, “Trending The UGG Shop” and “New Arrivals Shop All New Arrivals”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
31 cookies set on arrival
31Opening the homepage sets 31 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.
41 other companies contacted
Loading the homepage contacts 41 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 footwearetc.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
Helium Customer Fields · Attentive · Sc Easy Redirects · Klaviyo Email Marketing Sms · cloudfront.net · merchantyard.com · kount.com · attn.tv
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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Employees
- 77
- Headquarters
- Sunnyvale
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on footwearetc.com, including 21 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.