Programmable

Website review, no card needed

feetures.com.au logo

feetures.com.au website review

Visit site (opens in a new tab)Reviewed 12 November 202631 issues · 80 checks

This review found 31 issues worth fixing on feetures.com.au, 9 of them high impact, across 80 checks. The most urgent: page weight: 10.7 MB in 314 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

82B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.0 s1.2 sMay 23Nov 71.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Nov 7, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
167 ms125 msMay 23Nov 7153 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026135 ms
May 30, 2026130 ms
Jun 6, 2026133 ms
Jun 13, 2026132 ms
Jun 20, 2026154 ms
Jun 27, 2026157 ms
Jul 4, 2026160 ms
Jul 11, 2026160 ms
Jul 18, 2026154 ms
Jul 25, 2026148 ms
Aug 1, 2026144 ms
Aug 8, 2026146 ms
Aug 15, 2026148 ms
Aug 22, 2026153 ms
Aug 29, 2026156 ms
Sep 5, 2026156 ms
Sep 12, 2026162 ms
Sep 19, 2026158 ms
Sep 26, 2026153 ms
Oct 3, 2026152 ms
Oct 10, 2026150 ms
Oct 17, 2026153 ms
Oct 24, 2026154 ms
Oct 31, 2026154 ms
Nov 7, 2026153 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

feetures.com.au (opens in a new tab)
Full-page screenshot of feetures.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. feetures.com.au at 0.4 s0.4 s
  2. feetures.com.au at 0.8 s0.8 s
  3. feetures.com.au at 1.1 s1.1 s
  4. feetures.com.au at 1.5 s1.5 s
  5. feetures.com.au at 1.9 s1.9 s
  6. feetures.com.au at 2.3 s2.3 s
  7. feetures.com.au at 2.6 s2.6 s
  8. feetures.com.au at 3.0 s3.0 s

Speed

5 to fix68

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    750 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Reduce unused JavaScript

    296 KiB

    About 296 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 2.9 s

    A phone's processor spends 2.9 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 2,518 HTML elements

    The page has 2,518 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Shopify and Yotpo and others), adding 632 KiB and 339 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 46 KiB

    About 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 118 ms. During a long task the page ignores taps.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Improve image delivery

    96 KiB

    4 images could be 96 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    59 KiB

    17 files are served with short cache lifetimes, so returning visitors download them again (59 KiB).

  • Legacy JavaScript

    30 KiB

    Polyfills 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 JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed

  • Server response: 100 ms

    100 ms

    Your server sent the HTML in 100 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our Best Fit Yet”.

  • First Contentful Paint: 3.8 s

    3.8 s

    The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 9.5 s

    9.5 s

    The page becomes fully interactive after 9.5 s. Good is under 3.8 s.

  • Speed Index: 4.5 s

    4.5 s

    Visually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.

  • 11 images without width and height

    11 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 16% slower for real visitors

    +16%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 135 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 12% slower for real visitors

    +12%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 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.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 124 ms

    124 ms

    Real visitors wait 124 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 371 ms

    371 ms

    Real visitors wait 371 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.056

    0.056

    The layout barely moves while loading (CLS 0.056, good is under 0.1).

  • Total Blocking Time: 86 ms

    86 ms

    Scripts block the page for only 86 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70

  • Page weight: 10.7 MB in 314 requests

    10.7 MB

    Your homepage downloads 10.7 MB in 314 requests on a phone: media 7.9 MB (1), other files 870 KiB (106) and scripts 837 KiB (90). Under 2 MB keeps phones on slow connections fast.

  • About 3.0 g of CO₂ per visit

    3.04 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.04 g of CO₂e: 364.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

6 to fixGoogle 8992

  • Images must have alternative text (2 elements)

    Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Heading levels should only increase by one (2 elements)

    Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

  • 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.

  • 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

  • 47 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: 47 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8384

  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “Feetures™ | America's #1 Running Sock | Lifetime Guarantee – feetures Australia”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (193 characters)

    Your meta description is 193 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 59 internal links, 16 external

    The homepage links to 59 pages on feetures.com.au and 16 external pages.

5 checks passed

  • One H1 headline

    Your main headline reads: “feetures Australia”.

  • Canonical URL set

    The canonical URL is https://feetures.com.au/.

  • 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://feetures.com.au/sitemap.xml.

AI search readiness

2 to fix75

  • 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.

  • Some text only appears after JavaScript runs

    45%

    The HTML your server sends has 138 of the 306 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

2 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.

  • llms.txt published

    The site publishes https://feetures.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90

  • 13 pages without a meta description

    https://feetures.com.au/policies/shipping-policy, https://feetures.com.au/collections/all-womens-socks, https://feetures.com.au/collections/womens-invisible-socks, https://feetures.com.au/collections/womens-no-show-tab-socks, https://feetures.com.au/collections/womens-quarter-height-socks and https://feetures.com.au/collections/womens-mini-crew-socks and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://feetures.com.au/policies/shipping-policy, https://feetures.com.au/products/gift-card, https://feetures.com.au/pages/wholesale, https://feetures.com.au/collections/all-womens-socks, https://feetures.com.au/collections/womens-invisible-socks and https://feetures.com.au/collections/womens-no-show-tab-socks and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://feetures.com.au/policies/shipping-policy, https://feetures.com.au/products/gift-card, https://feetures.com.au/pages/wholesale, https://feetures.com.au/collections/all-womens-socks, https://feetures.com.au/collections/womens-invisible-socks and https://feetures.com.au/collections/womens-no-show-tab-socks and 9 others 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.

5 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.

  • 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

2 to fixGoogle 9687

  • 3 small tap targets

    3 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57

  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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.

  • About 306 words of copy

    The homepage carries about 306 words of visible text.

3 checks passed

  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop All” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • 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

1 to fix

  • 6 trackers load before any consent

    6

    Before 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.

  • 21 cookies set on arrival

    21

    Opening 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.

  • 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 feetures.com.au, 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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Sales Discounts · Gorgias Live Chat Helpdesk · Pagefly Ai Page Builder · Uppromote Affiliate · Simple Bundle · Selleasy · Affliate By Secomapp · yotpo.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

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on feetures.com.au, including 10 speed issues, 3 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25