Website review, no card needed

footlocker.com.au logo

footlocker.com.au website review

Visit site (opens in a new tab)Reviewed 30 October 202639 issues · 82 checks

This review found 39 issues worth fixing on footlocker.com.au, 16 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
4.0 s1.8 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.4 s
May 16, 20263.3 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.5 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.6 s
Jul 4, 20263.0 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.8 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.5 s
Sep 19, 20262.2 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
396 ms319 msMay 9Oct 24386 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026353 ms
May 16, 2026343 ms
May 23, 2026330 ms
May 30, 2026328 ms
Jun 6, 2026336 ms
Jun 13, 2026347 ms
Jun 20, 2026370 ms
Jun 27, 2026381 ms
Jul 4, 2026387 ms
Jul 11, 2026379 ms
Jul 18, 2026371 ms
Jul 25, 2026369 ms
Aug 1, 2026367 ms
Aug 8, 2026371 ms
Aug 15, 2026362 ms
Aug 22, 2026360 ms
Aug 29, 2026367 ms
Sep 5, 2026375 ms
Sep 12, 2026385 ms
Sep 19, 2026378 ms
Sep 26, 2026362 ms
Oct 3, 2026360 ms
Oct 10, 2026364 ms
Oct 17, 2026376 ms
Oct 24, 2026386 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

Full-page screenshot of footlocker.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. footlocker.com.au at 1.0 s1.0 s
  2. footlocker.com.au at 1.9 s1.9 s
  3. footlocker.com.au at 2.9 s2.9 s
  4. footlocker.com.au at 3.9 s3.9 s
  5. footlocker.com.au at 4.8 s4.8 s
  6. footlocker.com.au at 5.8 s5.8 s
  7. footlocker.com.au at 6.8 s6.8 s
  8. footlocker.com.au at 7.8 s7.8 s

Speed

13 to fix31
  • Use efficient cache lifetimes

    6.9 s · 5.6 MB

    57 files are served with short cache lifetimes, so returning visitors download them again (5.6 MB).

  • Reduce unused JavaScript

    3.5 s · 977 KiB

    About 977 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

  • Improve image delivery

    2.6 s · 1.7 MB

    8 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

  • Render-blocking requests

    1.1 s

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 8.2 s

    A phone's processor spends 8.2 s on main-thread work while loading, 5.6 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 (Adobe Tag Manager, Google Tag Manager and ContentSquare and others), adding 8.1 MB and 1.6 s of main-thread time.

  • footlocker.com adds 0 ms

    0 ms

    footlocker.com costs a phone 0 ms of main-thread work and 7.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.

  • Reduce unused CSS

    600 ms · 119 KiB

    About 119 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.

  • Adobe Tag Manager adds 495 ms

    495 ms

    Adobe Tag Manager costs a phone 495 ms of main-thread work and 394 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 524 ms. During a long task the page ignores taps.

  • Google Tag Manager adds 442 ms

    442 ms

    Google Tag Manager costs a phone 442 ms of main-thread work and 189 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.

  • ContentSquare adds 393 ms

    393 ms

    ContentSquare costs a phone 393 ms of main-thread work and 161 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.

  • Legacy JavaScript

    16 KiB

    Polyfills for old browsers add 16 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: 27 ms

    27 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Real-user INP: 572 ms

    572 ms

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

  • Real-user CLS: 0.85

    0.85

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

  • Largest Contentful Paint: 14.0 s

    14.0 s

    Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SPEND & SAVE The more you spend, the more you save. SHOP NOW”.

  • Time to Interactive: 24.2 s

    24.2 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

    Scripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

5 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 533 ms

    533 ms

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

  • Largest content (LCP) got 38% faster for real visitors

    -38%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix38
  • Page weight: 9.7 MB in 119 requests

    9.7 MB

    Your homepage downloads 9.7 MB in 119 requests on a phone: media 5.1 MB (2), scripts 2.1 MB (51) and images 2.0 MB (23). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Untitled design.png weighs 939 KiB. On a phone connection a single image that size takes seconds.

  • 7 images below the first screen load straight away

    7 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 4 images far larger than shown

    225 KiB

    4 images are downloaded at several times the size a phone draws them, for example gender-button-refresh-womens-4up.jpg at 1,000 px wide, shown at 191 px. Resized copies would save about 225 KiB.

  • 1 image in older formats

    1 image (292 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 2.7 g of CO₂ per visit

    2.74 g

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

Accessibility

2 to fixGoogle 10098
  • 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.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 73 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 1 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 9291
  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 246 internal links, 13 external

    The homepage links to 246 pages on footlocker.com.au and 13 external pages.

6 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Shop Foot Locker AU for the latest shoes and apparel from Nike, adidas, Jordan and more ☑️ FREE DELIVERY ON ORDERS OVER…”.

  • One H1 headline

    Your main headline reads: “The Heart of Sneakers”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “The Heart of Sneakers | Foot Locker Australia”.

  • Canonical URL set

    The canonical URL is https://www.footlocker.com.au/en/.

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

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.footlocker.com.au/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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (601 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    / and https://www.footlocker.com.au/en all use the title “The Heart of Sneakers | Foot Locker Australia”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 links to non-canonical URLs

    Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://www.footlocker.com.au/en/category/mens/new-arrivals, whose canonical is https://www.footlocker.com.au/en/category/mens/new-arrivals.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 197 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9687
  • 9 small tap targets

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

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 354 words of copy

    The homepage carries about 354 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN FLX REWARDS & GET 10% OFF*” and “SIGN UP”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “Sign In | Join FLX”, “Shop All Brands” and “Shop All Sale”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies (measured from a US location before any click).

  • 15 other companies contacted

    Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 footlocker.com.au, 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
Hosting
Fastly

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 footlocker.com.au, including 22 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

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