faly.me website review

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

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

176 images could be 10.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

About 62 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

8 third-party services load with your homepage (Shopify, bc-cdn.net and Twitter Online Conversion Tracking and others), adding 264 KiB and 89 ms of main-thread time.

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

15 KiB JavaScript is shipped twice across bundles.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 37.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Your homepage downloads 22.2 MB in 488 requests on a phone: images 21.6 MB (397), scripts 419 KiB (56) and stylesheets 64 KiB (20). Under 2 MB keeps phones on slow connections fast.

36 images are downloaded at several times the size a phone draws them, for example 06022510103White_1_d390c089-44b5-4705-9696-3a90703feba6.jpg at 2,453 px wide, shown at 176 px. Resized copies would save about 2.8 MB.

06022510103White_1_d390c089-44b5-4705-9696-3a90703feba6.jpg weighs 756 KiB. On a phone connection a single image that size takes seconds.

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

7 images (1.7 MB) 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.

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

5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

3 tap targets are too small or too close together to hit reliably with a finger.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

10 visible links have no text or label, so screen readers cannot say where they go.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 78 characters, so Google will cut it off around 60: “فالي - أزياء مريحة وعملية تخليك دائما متفائل فالك الزين | فالي السعودية – FALY”.

Structured data found (untyped) but with 2 problems, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.

The homepage links to 243 pages on faly.me and 19 external pages.

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.

https://www.faly.me/collections/jackets-1, https://www.faly.me/collections/comfort-thobe, https://www.faly.me/collections/sales-items-oct, https://www.faly.me/collections/%D8%B3%D8%AF%D9%8A%D8%B1%D9%8A and https://www.faly.me/collections/jackets have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.faly.me/collections/%D8%B3%D8%AF%D9%8A%D8%B1%D9%8A, whose canonical is https://www.faly.me/collections/%d8%b3%d8%af%d9%8a%d8%b1%d9%8a. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.faly.me/collections/jackets-1, https://www.faly.me/collections/cooltech, https://www.faly.me/collections/loungewear, https://www.faly.me/collections/underwear, https://www.faly.me/collections/thobe and https://www.faly.me/collections/travel-bag and 8 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.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 256 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap 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.

Opening the homepage sets 21 cookies, 2 of them by other companies (measured from a US location before any click).

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.

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