Website review, no card needed
falke.com.kw website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 80 checks
This review found 38 issues worth fixing on falke.com.kw, 10 of them high impact, across 80 checks. The most urgent: 20 buttons without a name. 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
One score from every part of this review. How it works
Speed
Mobile performance score: 75
75/100Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
8 third-party services on the page
8 third-party services load with your homepage (infobip.com, WebEngage and Snapchat and others), adding 1.3 MB and 622 ms of main-thread time.
Reduce unused JavaScript
601 KiBAbout 601 KiB of JavaScript is downloaded but never used on this page.
infobip.com adds 363 ms
363 msinfobip.com costs a phone 363 ms of main-thread work and 556 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
100 ms · 271 KiB13 files are served with short cache lifetimes, so returning visitors download them again (271 KiB).
Improve image delivery
324 KiB21 images could be 324 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,085 HTML elements
The page has 2,085 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 30 ms
30 msShopify costs a phone 30 ms of main-thread work and 339 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need.
Reduce unused CSS
14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 746 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 15.6 s
15.6 sThe page becomes fully interactive after 15.6 s. Good is under 3.8 s.
Largest Contentful Paint: 5.8 s
5.8 sYour largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
30 images without width and height
30 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Total Blocking Time: 185 ms
185 msScripts block the page for only 185 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
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.
Images and page weight
Page weight: 3.4 MB in 278 requests
3.4 MBYour homepage downloads 3.4 MB in 278 requests on a phone: scripts 1.3 MB (58), images 1.0 MB (63) and other files 853 KiB (127). Under 2 MB keeps phones on slow connections fast.
6 images below the first screen load straight away
6 images further down the page (411 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
67 KiB1 image is downloaded at several times the size a phone draws it, for example newsletter-background-image.jpg at 1,440 px wide, shown at 390 px. Resized copies would save about 67 KiB.
2 images in older formats
2 images (266 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.
About 1.0 g of CO₂ per visit
0.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 115.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
20 buttons without a name
20 buttons have no accessible name, so screen readers announce just “button”.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
20 images without alt text
20 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
9 links without text
9 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
298 internal links, 2 external
The homepage links to 298 pages on falke.com.kw and 2 external pages.
6 checks passed
Meta description: 102 characters
Your meta description is 102 characters: “Socks for Every Occasion. Legwear, Sports & Fashion for Men & Women. Online, Instore. Click & Collect.”.
Title: 64 characters
Your title is a healthy 64 characters: “FALKE | Kuwait Official Store | Premium Socks for Every Occasion”.
Canonical URL set
The canonical URL is https://falke.com.kw/.
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://falke.com.kw/sitemap.xml.
AI search readiness
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.
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 (944 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://falke.com.kw/ar has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 124 found) and read each the way a search engine does.
6 checks passed
Linked pages load
1 page of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 1 page 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 1 page that loaded have a <title>.
Best practices
40 small tap targets
40 of 127 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://falke.com.kw/cdn/shop/t/3/assets/single-image-banner.css?v=33229' because its MIME…”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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
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.
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 570 words of copy
The homepage carries about 570 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Shop All” and “Contact”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel 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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 1 of them by other companies (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.
39 other companies contacted
Loading the homepage contacts 39 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 falke.com.kw, 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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Webengage · Forms · snapchat.com
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 38 issues on falke.com.kw, including 13 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.