Website review, no card needed
albayanperfumes.com website review
Visit site (opens in a new tab)Reviewed 9 November 202639 issues · 84 checks
This review found 39 issues worth fixing on albayanperfumes.com, 10 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
70C- #103,166 of 123,862 reviewed websitesbeats 14%
- #62,583 of 69,698 online storesbeats 8%
- #57,899 of 63,406 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 173 ms |
| May 30, 2026 | 182 ms |
| Jun 6, 2026 | 185 ms |
| Jun 13, 2026 | 185 ms |
| Jun 20, 2026 | 187 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 192 ms |
| Jul 11, 2026 | 202 ms |
| Jul 18, 2026 | 202 ms |
| Jul 25, 2026 | 202 ms |
| Aug 1, 2026 | 202 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 202 ms |
| Aug 22, 2026 | 210 ms |
| Aug 29, 2026 | 210 ms |
| Sep 5, 2026 | 216 ms |
| Sep 12, 2026 | 224 ms |
| Sep 19, 2026 | 218 ms |
| Sep 26, 2026 | 215 ms |
| Oct 3, 2026 | 201 ms |
| Oct 10, 2026 | 189 ms |
| Oct 17, 2026 | 188 ms |
| Oct 24, 2026 | 183 ms |
| Oct 31, 2026 | 181 ms |
| Nov 7, 2026 | 178 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
0.4 s
0.8 s
1.2 s
1.7 s
2.1 s
2.5 s
2.9 s
3.3 s
Speed
Render-blocking requests
2.3 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Reduce unused JavaScript
1.2 s · 759 KiBAbout 759 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
5,242 HTML elements
The page has 5,242 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 (ContentSquare, TikTok and Shopify and others), adding 1.6 MB and 1.2 s of main-thread time.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
ContentSquare adds 531 ms
531 msContentSquare costs a phone 531 ms of main-thread work and 185 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.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 202 ms
202 msShopify costs a phone 202 ms of main-thread work and 704 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.
TikTok adds 223 ms
223 msTikTok costs a phone 223 ms of main-thread work and 296 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.
Google Tag Manager adds 130 ms
130 msGoogle Tag Manager costs a phone 130 ms of main-thread work and 312 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
150 ms · 64 KiB7 files are served with short cache lifetimes, so returning visitors download them again (64 KiB).
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
150 ms · 15 KiB1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 97 ms. During a long task the page ignores taps.
Duplicated JavaScript
31 KiB31 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
10 KiBAbout 10 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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 20 ms
20 msYour server sent the HTML in 20 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.
Time to Interactive: 16.3 s
16.3 sThe page becomes fully interactive after 16.3 s. Good is under 3.8 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 236 ms
236 msReal visitors wait 236 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 957 ms
957 msReal visitors wait 957 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 173 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 112 ms
112 msScripts block the page for only 112 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.032
0.032The layout barely moves while loading (CLS 0.032, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 311 requests
3.5 MBYour homepage downloads 3.5 MB in 311 requests on a phone: scripts 1.6 MB (73), other files 978 KiB (128) and images 742 KiB (62). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Banner_6_1.png 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.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 119.8 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
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (68 characters)
Your meta description is only 68 characters: “خبرة أكثر من 25 سنة في مجال تركيب العطور الرجالية والنسائية والعربية”. 70 to 160 characters is enough to sell the click.
One H1 headline
Your <h1> is empty.
202 internal links, 8 external
The homepage links to 202 pages on albayanperfumes.com and 8 external pages.
6 checks passed
Title: 61 characters
Your title is a healthy 61 characters: “عطورات البيان أفضل عطور مستوحاة في البحرين – Albayan Perfumes”.
Canonical URL set
The canonical URL is https://albayanperfumes.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://albayanperfumes.com/sitemap.xml.
AI search readiness
4 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 sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (652 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://albayanperfumes.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://albayanperfumes.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://albayanperfumes.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 pages without a meta description
https://albayanperfumes.com/collections/all, https://albayanperfumes.com/customer_authentication/redirect, https://albayanperfumes.com/policies/shipping-policy, https://albayanperfumes.com/collections/newperfumes, https://albayanperfumes.com/collections/summer-discount and https://albayanperfumes.com/collections/special-discount-bundles and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://albayanperfumes.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://albayanperfumes.com/policies/shipping-policy and https://albayanperfumes.com/collections/special-discount-bundles 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 101 found) and read each the way a search engine does.
3 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.
Titles are unique
Every page we checked has its own title.
Best practices
34 small tap targets
34 of 127 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “ttq is not defined”.
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 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.
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 421 words of copy
The homepage carries about 421 words of visible text.
3 checks passed
33 short forms
33 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 168 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.
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.
30 cookies set on arrival
30Opening the homepage sets 30 cookies, 3 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.
30 other companies contacted
Loading the homepage contacts 30 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 albayanperfumes.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Kai Progress Bar Free Gift · Bucks · Judge Me Reviews · Sami Product Labels · Appstle Loyalty · Ecomsend · 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
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on albayanperfumes.com, including 20 speed issues, 2 SEO issues and 3 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.