Website review, no card needed
footgear.co.za website review
Visit site (opens in a new tab)Reviewed 18 November 202643 issues · 89 checks
This review found 43 issues worth fixing on footgear.co.za, 17 of them high impact, across 89 checks. The most urgent: render-blocking 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
67D- #107,936 of 120,300 reviewed websitesbeats 9%
- #64,430 of 68,126 online storesbeats 4%
- #2,426 of 2,779 WooCommerce storesbeats 10%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.2 s |
| Oct 31, 2026 | 3.2 s |
| Nov 7, 2026 | 3.1 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 322 ms |
| Jun 6, 2026 | 320 ms |
| Jun 13, 2026 | 322 ms |
| Jun 20, 2026 | 322 ms |
| Jun 27, 2026 | 327 ms |
| Jul 4, 2026 | 330 ms |
| Jul 11, 2026 | 326 ms |
| Jul 18, 2026 | 326 ms |
| Jul 25, 2026 | 322 ms |
| Aug 1, 2026 | 327 ms |
| Aug 8, 2026 | 337 ms |
| Aug 15, 2026 | 343 ms |
| Aug 22, 2026 | 353 ms |
| Aug 29, 2026 | 354 ms |
| Sep 5, 2026 | 351 ms |
| Sep 12, 2026 | 354 ms |
| Sep 19, 2026 | 354 ms |
| Sep 26, 2026 | 361 ms |
| Oct 3, 2026 | 371 ms |
| Oct 10, 2026 | 376 ms |
| Oct 17, 2026 | 382 ms |
| Oct 24, 2026 | 379 ms |
| Oct 31, 2026 | 369 ms |
| Nov 7, 2026 | 353 ms |
| Nov 14, 2026 | 337 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
3.0 s
6.0 s
9.1 s
12.1 s
15.1 s
18.1 s
21.1 s
24.1 s
Speed
Render-blocking requests
3.5 s69 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Improve image delivery
1.6 s · 322 KiB3 images could be 322 KiB 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.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.0 MB and 1.5 s of main-thread time.
Reduce unused JavaScript
300 ms · 878 KiBAbout 878 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
600 ms · 130 KiBAbout 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce initial server response time
660 msReduce initial server response time. Google estimates savings of 660 ms on a phone.
Document request latency
650 msThe HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Google CDN adds 440 ms
440 msGoogle CDN costs a phone 440 ms of main-thread work and 1.1 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.
Google Tag Manager adds 365 ms
365 msGoogle Tag Manager costs a phone 365 ms of main-thread work and 368 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Use efficient cache lifetimes
277 KiB9 files are served with short cache lifetimes, so returning visitors download them again (277 KiB).
2,422 HTML elements
The page has 2,422 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 760 ms
760 msYour server takes 760 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 227 ms. During a long task the page ignores taps.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
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.
Largest Contentful Paint: 9.6 s
9.6 sYour largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BF Mobile Banners-01”. Most of its time is element render delay (10.1 s).
Speed Index: 23.9 s
23.9 sVisually, the page fills in at 23.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.9 s
24.9 sThe page becomes fully interactive after 24.9 s. Good is under 3.8 s.
Total Blocking Time: 795 ms
795 msScripts block taps and scrolling for 795 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 324 ms
324 msReal visitors wait 324 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 322 ms to 337 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-11-14, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user TTFB: 771 ms
771 msReal visitors wait 771 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: 4.4 MB in 206 requests
4.4 MBYour homepage downloads 4.4 MB in 206 requests on a phone: scripts 2.4 MB (95), fonts 784 KiB (13) and images 470 KiB (9). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (1.0 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.
About 1.3 g of CO₂ per visit
1.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 150.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 96 images in the HTML carry an alt attribute.
47 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: 47 passed and 8 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
328 internal links, 5 external
The homepage links to 328 pages on footgear.co.za and 5 external pages.
8 checks passed
Meta description: 124 characters
Your meta description is 124 characters: “Shop Footgear for top-quality footwear for ladies and men! Find the latest styles and unbeatable comfort for every occa…”.
One H1 headline
Your main headline reads: “BIGGEST BRANDS!! BEST PRICES!!”.
Title: 57 characters
Your title is a healthy 57 characters: “Footgear® SA | Biggest Footwear Brands | Men, Women, Kids”.
Canonical URL set
The canonical URL is https://www.footgear.co.za/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.
XML sitemap found
Your XML sitemap is reachable at https://www.footgear.co.za/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.footgear.co.za/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 (515 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page slow to respond
https://www.footgear.co.za/k took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 101 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'https'”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
Only about 236 words
The homepage has only about 236 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL” and “SHOP BRANDS”.
7 calls to action
The homepage has 7 calls to action, for example “Shop All Brands”, “shop all” and “shop brands”.
4 short forms
4 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
21 other companies contacted
Loading the homepage contacts 21 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 footgear.co.za, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- (Pty) Ltd - Xneelo (Pty) Ltd
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on footgear.co.za, including 26 speed 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.