Website review, no card needed
benisouk.com website review
Visit site (opens in a new tab)Reviewed 11 November 202630 issues · 82 checks
This review found 30 issues worth fixing on benisouk.com, 8 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
85B- #14,962 of 109,350 reviewed websitesbeats 82%
- #9,513 of 61,859 online storesbeats 79%
- #9,250 of 56,401 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 165 ms |
| May 30, 2026 | 167 ms |
| Jun 6, 2026 | 167 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 175 ms |
| Jun 27, 2026 | 181 ms |
| Jul 4, 2026 | 183 ms |
| Jul 11, 2026 | 187 ms |
| Jul 18, 2026 | 195 ms |
| Jul 25, 2026 | 197 ms |
| Aug 1, 2026 | 206 ms |
| Aug 8, 2026 | 203 ms |
| Aug 15, 2026 | 190 ms |
| Aug 22, 2026 | 181 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 190 ms |
| Oct 17, 2026 | 198 ms |
| Oct 24, 2026 | 204 ms |
| Oct 31, 2026 | 204 ms |
| Nov 7, 2026 | 201 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
4.1 s
8.2 s
12.3 s
16.5 s
20.6 s
24.7 s
28.8 s
32.9 s
Speed
Improve image delivery
1.0 s · 1.7 MB7 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Facebook and Klaviyo and others), adding 2.9 MB and 644 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 490 KiB20 files are served with short cache lifetimes, so returning visitors download them again (490 KiB).
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Reduce unused JavaScript
347 KiBAbout 347 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 22 ms
22 msShopify costs a phone 22 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.
1,561 HTML elements
The page has 1,561 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 108 ms
108 msKlaviyo costs a phone 108 ms of main-thread work and 309 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.
azurefd.net adds 53 ms
53 msazurefd.net costs a phone 53 ms of main-thread work and 331 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.
Reduce unused CSS
150 ms · 32 KiBAbout 32 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Legacy JavaScript
45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 30.2 s
30.2 sVisually, the page fills in at 30.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 23.1 s
23.1 sThe page becomes fully interactive after 23.1 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Material, hand,”.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 165 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 161 ms
161 msReal visitors wait 161 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 469 ms
469 msReal visitors wait 469 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 57% faster for real visitors
-57%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.1 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 176 ms
176 msScripts block the page for only 176 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.9 MB in 403 requests
5.9 MBYour homepage downloads 5.9 MB in 403 requests on a phone: images 2.3 MB (19), other files 1.5 MB (257) and scripts 1.4 MB (111). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Benisouk_Mrirt_Middle_Atlas_slide.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.7 g of CO₂ per visit
1.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.3 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
44 text elements with low contrast
44 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
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
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “BENISOUK | Moroccan Rugs & Home Decor, Made in Our Ateliers – Benisouk”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“”, “” and “Maison Benisouk”). One clear main headline is easier for people and search engines.
180 internal links, 8 external
The homepage links to 180 pages on benisouk.com and 8 external pages.
5 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Hand-knotted Moroccan rugs, made to order in your size and colors. Home decor made by hand in our own ateliers. Materia…”.
Canonical URL set
The canonical URL is https://benisouk.com/.
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://benisouk.com/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,320 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://benisouk.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://benisouk.com/collections/moroccan-rug, https://benisouk.com/collections/bestseller-moroccan-rugs, https://benisouk.com/collections/vintage-moroccan-rugs, https://benisouk.com/collections/custom-moroccan-rugs, https://benisouk.com/collections/clearance and https://benisouk.com/collections/shag-rug and 9 others have 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 45 found) and read each the way a search engine does.
6 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
2 checks passed
Tap targets are thumb-sized
21 of 26 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 795 words of copy
The homepage carries about 795 words of visible text.
6 checks passed
22 calls to action
The homepage has 22 calls to action, for example “Shop all rugs”, “Made to order” and “Shop all”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and “700+ reviews”.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 4 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 6 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
46 cookies set on arrival
46Opening the homepage sets 46 cookies, 9 of them by other companies (measured from a US location before any click).
50 other companies contacted
Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 benisouk.com, 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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Blockx Country Blocker · Klaviyo Email Marketing Sms · quotify.dev · hubapi.com · weglot.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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on benisouk.com, including 15 speed issues, 3 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.