Website review, no card needed
lyalclothing.com website review
Visit site (opens in a new tab)Reviewed 9 November 202645 issues · 91 checks
This review found 45 issues worth fixing on lyalclothing.com, 17 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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
58F- #124,107 of 126,369 reviewed websitesbeats 1%
- #70,077 of 70,448 online storesbeats 0%
- #63,702 of 63,950 Shopify storesbeats 0%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.2 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.7 s |
| Nov 7, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 162 ms |
| Jul 18, 2026 | 173 ms |
| Jul 25, 2026 | 180 ms |
| Aug 1, 2026 | 183 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 201 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 202 ms |
| Oct 10, 2026 | 184 ms |
| Oct 17, 2026 | 184 ms |
| Oct 24, 2026 | 198 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.1 s
2.1 s
3.2 s
4.2 s
5.3 s
6.3 s
7.4 s
8.4 s
Speed
Reduce unused JavaScript
1.5 s · 785 KiBAbout 785 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.5 s
A phone's processor spends 9.5 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,868 HTML elements
The page has 4,868 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hotjar and salla.network and others), adding 2.8 MB and 2.9 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.8 s. During a long task the page ignores taps.
Google Tag Manager adds 801 ms
801 msGoogle Tag Manager costs a phone 801 ms of main-thread work and 487 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.
salla.network adds 536 ms
536 mssalla.network costs a phone 536 ms of main-thread work and 1.5 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.
Hotjar adds 573 ms
573 msHotjar costs a phone 573 ms of main-thread work and 65 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.
Facebook adds 373 ms
373 msFacebook costs a phone 373 ms of main-thread work and 287 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
379 KiB10 files are served with short cache lifetimes, so returning visitors download them again (379 KiB).
TikTok adds 320 ms
320 msTikTok costs a phone 320 ms of main-thread work and 284 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.
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Reduce unused CSS
290 ms · 53 KiBAbout 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
Improve image delivery
7 KiB1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
Real-user CLS: 0.36
0.36For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 13.5 s
13.5 sYour largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “S337”.
Total Blocking Time: 4.2 s
4.2 sScripts block taps and scrolling for 4.2 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 21.2 s
21.2 sThe page becomes fully interactive after 21.2 s. Good is under 3.8 s.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 162 ms to 198 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 153 requests
3.2 MBYour homepage downloads 3.2 MB in 153 requests on a phone: scripts 2.0 MB (90), images 619 KiB (25) and fonts 418 KiB (4). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
263 KiB2 images are downloaded at several times the size a phone draws them, for example uBqj6wA33GVI9958Y2kUJx56J2h5QF5v3tFvEZdh.jpg at 1,043 px wide, shown at 50 px. Resized copies would save about 263 KiB.
5 images below the first screen load straight away
5 images further down the page (385 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (92 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 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
96 text elements with low contrast
96 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
30 images without alt text
30 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Hidden but focusable
25 elements hidden from screen readers can still receive keyboard focus.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 7 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (12 characters)
Your title is only 12 characters: “LyalClothing”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (198 characters)
Your meta description is 198 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
403 internal links, 6 external
The homepage links to 403 pages on lyalclothing.com and 6 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://lyalclothing.com/en.
Structured data in place
Structured data found: Organization and WebPage.
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://lyalclothing.com/sitemap.xml.
AI search readiness
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 description; sameAs (social profiles) and contact details would complete it.
llms.txt published
The site publishes https://lyalclothing.com/llms.txt (7 KiB, 32 links), a plain-text guide to the site for AI tools.
Other pages
15 pages with very little text
https://lyalclothing.com/en/shop/c1459544335, https://lyalclothing.com/en/abayas-by-style/c1923100425, https://lyalclothing.com/en/bisht-abayas/c1849638426, https://lyalclothing.com/en/kloosh-abayas/c1081975406, https://lyalclothing.com/en/hajj-umrah-abayas/c1814552680 and https://lyalclothing.com/en/prayer-gowns/c24742773 and 9 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.
3 pages slow to respond
https://lyalclothing.com/en/half-bisht/c983815315, https://lyalclothing.com/en/quarter-bisht/c344519580 and https://lyalclothing.com/en/quarter-kloosh/c1608810392 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 124 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
1 broken image
1 image failed to load on a phone, for example https://cdn.salla.network/images/payment/mahally_customer_wallet_mini.png?v=2.0.5.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
42 of 42 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Only about 120 words
The homepage has only about 120 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “[email protected]”.
Social proof on the page
Social proof on the homepage: 34 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
9 other companies contacted
Loading the homepage contacts 9 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 lyalclothing.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- 10 Shopify Products;Shopify;Shopify Plus
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on lyalclothing.com, including 24 speed issues, 4 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.