Website review, no card needed
madkicks.com website review
Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 86 checks
This review found 33 issues worth fixing on madkicks.com, 8 of them high impact, across 86 checks. The most urgent: fails Core Web Vitals for real visitors. 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
82B- #28,396 of 100,140 reviewed websitesbeats 66%
- #18,417 of 55,068 online storesbeats 60%
- #17,789 of 50,005 Shopify storesbeats 57%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.4 s |
| Oct 31, 2026 | 3.3 s |
| Nov 7, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 171 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 162 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 164 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 169 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 172 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 179 ms |
| Aug 8, 2026 | 179 ms |
| Aug 15, 2026 | 181 ms |
| Aug 22, 2026 | 182 ms |
| Aug 29, 2026 | 185 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 189 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 188 ms |
| Oct 10, 2026 | 195 ms |
| Oct 17, 2026 | 194 ms |
| Oct 24, 2026 | 192 ms |
| Oct 31, 2026 | 187 ms |
| Nov 7, 2026 | 179 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
Speed
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 2.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 (Google Tag Manager, Google CDN and Clarity and others), adding 1.8 MB and 1.4 s of main-thread time.
Mobile performance score: 79
79/100Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
809 KiBAbout 809 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
650 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Google Tag Manager adds 549 ms
549 msGoogle Tag Manager costs a phone 549 ms of main-thread work and 652 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 356 ms
356 msGoogle CDN costs a phone 356 ms of main-thread work and 743 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.
2,080 HTML elements
The page has 2,080 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
241 KiB8 files are served with short cache lifetimes, so returning visitors download them again (241 KiB).
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 218 ms. During a long task the page ignores taps.
Improve image delivery
174 KiB8 images could be 174 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need.
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: 279 ms
279 msYour server sent the HTML in 279 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: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 466 ms
466 msScripts block taps and scrolling for 466 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 171 ms to 179 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 2.9 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 188 ms
188 msReal visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 771 ms
771 msReal visitors wait 771 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Loewe x On Cloudtilt Cosmic”.
Images and page weight
Page weight: 4.1 MB in 229 requests
4.1 MBYour homepage downloads 4.1 MB in 229 requests on a phone: scripts 2.1 MB (51), images 1.0 MB (95) and other files 519 KiB (67). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (94 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.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 140.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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”.
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.
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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
244 internal links, 31 external
The homepage links to 244 pages on madkicks.com and 31 external pages.
8 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Discover limited and authentic sneakers, streetwear, and accessories in the UAE. Curated luxury collections with fast l…”.
One H1 headline
Your main headline reads: “Limited & Authentic Sneakers in the UAE – Mad Kicks”.
Title: 64 characters
Your title is a healthy 64 characters: “Men's & Women's Luxury Sneakers, Bags & Collectibles | Mad Kicks”.
Canonical URL set
The canonical URL is https://madkicks.com/.
Structured data in place
Structured data found: Organization 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://madkicks.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://madkicks.com/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 (1,100 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://madkicks.com/blog, which answers with an error. Visitors hit a dead end and search engines drop it.
3 pages share a meta description
https://madkicks.com/sell-your-product, https://madkicks.com/store-locations and https://madkicks.com/faqs use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://madkicks.com/sell-your-product has no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://madkicks.com/faqs, https://madkicks.com/collections/hermes-bags, https://madkicks.com/collections/nike-mind, https://madkicks.com/collections/air-jordan-x-travis-scott, https://madkicks.com/collections/on-running-x-loewe and https://madkicks.com/collections/pokemon and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 163 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 43 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is 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 “p: MISSING_MESSAGE: misc.scrollLeft (en)”.
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
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.
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,036 words of copy
The homepage carries about 1,036 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “BUY NOW”.
9 calls to action
The homepage has 9 calls to action, for example “Shop Now”, “Buy Now” and “SHOP BYChanel 25”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
25 other companies contacted
Loading the homepage contacts 25 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 madkicks.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Next.js
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Vercel
Company
- Headquarters
- Dubai
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on madkicks.com, including 14 speed issues, 1 SEO issue 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.