semir.com.sa website review

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

About 148 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.

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

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

8 third-party services load with your homepage (Shopify, Hotjar and Klaviyo and others), adding 381 KiB and 219 ms of main-thread time.

About 15 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.

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

1 image could be 27 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

3 files are served with short cache lifetimes, so returning visitors download them again (12 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.

2 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.

For real visitors the layout shifts by 0.85 (75th percentile). Good is under 0.1.

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.9 s).

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

The layout shifts by 0.439 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

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

The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

6 images have no width and height attributes, so the layout jumps as each one loads.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

18 elements hidden from screen readers can still receive keyboard focus.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

73 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.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 71 characters, so Google will cut it off around 60: “سيمر السعودية: أزياء عصرية للرجال والنساء | تسوق أحدث الموديلات – SEMIR”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 88 pages on semir.com.sa and 5 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://semir.com.sa/collections/kids, https://semir.com.sa/pages/%D9%84%D9%84%D8%B1%D8%AC%D8%A7%D9%84 and https://semir.com.sa/collections/women-denim use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://semir.com.sa/collections/%D8%A7%D9%84%D8%B1%D8%AC%D8%A7%D9%84, whose canonical is https://semir.com.sa/collections/%d8%a7%d9%84%d8%b1%d8%ac%d8%a7%d9%84. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://semir.com.sa/collections/new-arrivals, https://semir.com.sa/collections/%D8%A7%D9%84%D8%B1%D8%AC%D8%A7%D9%84, https://semir.com.sa/collections/%D8%A7%D9%84%D9%86%D8%B3%D8%A7%D8%A1, https://semir.com.sa/collections/kids, https://semir.com.sa/pages/%D9%84%D9%84%D8%B1%D8%AC%D8%A7%D9%84 and https://semir.com.sa/collections/new-arrivals-women and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://semir.com.sa/collections/new-arrivals, https://semir.com.sa/collections/%D8%A7%D9%84%D8%B1%D8%AC%D8%A7%D9%84, https://semir.com.sa/collections/%D8%A7%D9%84%D9%86%D8%B3%D8%A7%D8%A1, https://semir.com.sa/collections/kids, https://semir.com.sa/pages/%D9%84%D9%84%D8%B1%D8%AC%D8%A7%D9%84 and https://semir.com.sa/collections/new-arrivals-women 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.

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

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

1 error was 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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 82 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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, Hotjar and Klaviyo and 3 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 19 cookies (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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.