Website review, no card needed
footkorner.com website review
Visit site (opens in a new tab)Reviewed 1 November 202634 issues · 84 checks
This review found 34 issues worth fixing on footkorner.com, 12 of them high impact, across 84 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
77C- #67,513 of 121,135 reviewed websitesbeats 39%
- #43,881 of 68,544 online storesbeats 31%
- #41,771 of 62,462 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 185 ms |
| May 16, 2026 | 180 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 179 ms |
| Jun 6, 2026 | 183 ms |
| Jun 13, 2026 | 187 ms |
| Jun 20, 2026 | 188 ms |
| Jun 27, 2026 | 199 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 209 ms |
| Jul 18, 2026 | 210 ms |
| Jul 25, 2026 | 207 ms |
| Aug 1, 2026 | 210 ms |
| Aug 8, 2026 | 215 ms |
| Aug 15, 2026 | 231 ms |
| Aug 22, 2026 | 250 ms |
| Aug 29, 2026 | 254 ms |
| Sep 5, 2026 | 254 ms |
| Sep 12, 2026 | 241 ms |
| Sep 19, 2026 | 220 ms |
| Sep 26, 2026 | 202 ms |
| Oct 3, 2026 | 185 ms |
| Oct 10, 2026 | 182 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 191 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.2 s
5.2 s
6.3 s
7.3 s
8.4 s
Speed
Render-blocking requests
1.5 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,820 HTML elements
The page has 7,820 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 4.2 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 (Shopify, Clarity and vercel.app and others), adding 1.2 MB and 920 ms of main-thread time.
Reduce unused JavaScript
610 KiBAbout 610 KiB of JavaScript is downloaded but never used on this page.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 486 ms. During a long task the page ignores taps.
Shopify adds 436 ms
436 msShopify costs a phone 436 ms of main-thread work and 208 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.
Use efficient cache lifetimes
445 KiB23 files are served with short cache lifetimes, so returning visitors download them again (445 KiB).
Improve image delivery
150 ms · 96 KiB5 images could be 96 KiB 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.
Reduce unused CSS
150 ms · 49 KiBAbout 49 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
50 KiBPolyfills for old browsers add 50 KiB JavaScript that modern phones do not need.
Minify JavaScript
20 KiB20 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: 78 ms
78 msYour server sent the HTML in 78 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.
Time to Interactive: 22.4 s
22.4 sThe page becomes fully interactive after 22.4 s. Good is under 3.8 s.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BLACK-MONT-tout-en-promotion - Footkorner”.
Total Blocking Time: 943 ms
943 msScripts block taps and scrolling for 943 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 322 ms
322 msReal visitors wait 322 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 185 ms to 191 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 653 ms
653 msReal visitors wait 653 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-24, 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).
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 376 requests
4.4 MBYour homepage downloads 4.4 MB in 376 requests on a phone: scripts 2.0 MB (94), other files 1.3 MB (235) and images 856 KiB (24). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
94 KiB1 image is downloaded at several times the size a phone draws it, for example asics.png at 2,048 px wide, shown at 65 px. Resized copies would save about 94 KiB.
2 images in older formats
2 images (127 KiB) 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.
4 images below the first screen load straight away
4 images further down the page (128 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 149.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
28 links without text
28 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (7 elements)
ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 347 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “Vêtements et accessoires : football, sportswear et streetwear. – Footkorner”.
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.
620 internal links, 9 external
The homepage links to 620 pages on footkorner.com and 9 external pages.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Vêtements et accessoires pour hommes et enfants : Collection FK, survêtements de football, sportswear et streetwear sur…”.
One H1 headline
Your main headline reads: “Vêtement streetwear et accessoires - Footkorner”.
Canonical URL set
The canonical URL is https://www.footkorner.com/.
Structured data in place
Structured data found: Organization, WebPage and WebSite.
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.footkorner.com/sitemap.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: 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 (3,240 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.footkorner.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.footkorner.com/collections/ensemble-t-shirt-short has no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://www.footkorner.com/collections/vetements-fk, https://www.footkorner.com/collections/nouveautes-globales, https://www.footkorner.com/collections/hommes, https://www.footkorner.com/collections/football, https://www.footkorner.com/collections/survetements and https://www.footkorner.com/collections/enfants and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.footkorner.com/collections/promotions took over 3 s to send its HTML from our server.
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.
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 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
29 of 33 tappable elements near the top are at least 24 px.
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.
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 1,110 words of copy
The homepage carries about 1,110 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Shop par club” and “Formulaire de contact”.
204 short forms
204 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 29 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel, Microsoft Clarity and Snap 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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
48 other companies contacted
Loading the homepage contacts 48 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 footkorner.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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Employees
- 550
- Headquarters
- Paris
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on footkorner.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.