Website review, no card needed
ae.goldenscent.com website review
Visit site (opens in a new tab)Reviewed 17 November 202641 issues · 75 checks
This review found 41 issues worth fixing on ae.goldenscent.com, 11 of them high impact, across 75 checks. The most urgent: fails Core Web Vitals for real visitors. 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.9 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 5.0 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 5.0 s |
| Jul 18, 2026 | 5.0 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.0 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 189 ms |
| Jun 6, 2026 | 189 ms |
| Jun 13, 2026 | 191 ms |
| Jun 20, 2026 | 191 ms |
| Jun 27, 2026 | 189 ms |
| Jul 4, 2026 | 193 ms |
| Jul 11, 2026 | 189 ms |
| Jul 18, 2026 | 193 ms |
| Jul 25, 2026 | 208 ms |
| Aug 1, 2026 | 237 ms |
| Aug 8, 2026 | 268 ms |
| Aug 15, 2026 | 304 ms |
| Aug 22, 2026 | 323 ms |
| Aug 29, 2026 | 349 ms |
| Sep 5, 2026 | 345 ms |
| Sep 12, 2026 | 345 ms |
| Sep 19, 2026 | 339 ms |
| Sep 26, 2026 | 293 ms |
| Oct 3, 2026 | 282 ms |
| Oct 10, 2026 | 275 ms |
| Oct 17, 2026 | 267 ms |
| Oct 24, 2026 | 281 ms |
| Oct 31, 2026 | 262 ms |
| Nov 7, 2026 | 246 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.5 s
1.1 s
1.6 s
2.1 s
2.6 s
3.2 s
3.7 s
4.2 s
Speed
5,359 HTML elements
The page has 5,359 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Insider and TikTok and others), adding 1.3 MB and 1.4 s of main-thread time.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
999 KiB12 files are served with short cache lifetimes, so returning visitors download them again (999 KiB).
Google Tag Manager adds 771 ms
771 msGoogle Tag Manager costs a phone 771 ms of main-thread work and 698 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 JavaScript
754 KiBAbout 754 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
628 KiB4 images could be 628 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
600 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 414 ms. During a long task the page ignores taps.
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 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: 23 ms
23 msYour server sent the HTML in 23 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: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
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.
Tap response (INP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 189 ms to 246 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Main lp - MobileWeb - H - 410*190 - Main Banner Best Seller”.
Cumulative Layout Shift: 0.134
0.134The layout shifts by 0.134 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 43% faster for real visitors
-43%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.9 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.3 s
3.3 sVisually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.8 MB in 144 requests
2.8 MBYour homepage downloads 2.8 MB in 144 requests on a phone: scripts 1.8 MB (54), images 808 KiB (39) and HTML 148 KiB (5). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
sb101854-allure-set---2-pcs_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).
2 images in older formats
2 images (614 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.
2 images far larger than shown
156 KiB2 images are downloaded at several times the size a phone draws them, for example sb101854-allure-set---2-pcs_1.png at 750 px wide, shown at 216 px. Resized copies would save about 156 KiB.
About 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 96.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
48 text elements with low contrast
48 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 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.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 398 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
577 internal links, 66 external
The homepage links to 577 pages on ae.goldenscent.com and 66 external pages.
7 checks passed
Meta description: 100 characters
Your meta description is 100 characters: “اكتشف أفضل العطور ومستحضرات التجميل الأصلية من قولدن سنت مع عروض حصرية وتوصيل سريع وجودة مضمونة 100%”.
One H1 headline
Your main headline reads: “Golden Scent”.
Title: 52 characters
Your title is a healthy 52 characters: “عطور ومستحضرات تجميل أصلية بأسعار مميزة من قولدن سنت”.
Canonical URL set
The canonical URL is https://ae.goldenscent.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.
XML sitemap found
Your XML sitemap is reachable at https://ae.goldenscent.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
2 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://ae.goldenscent.com/llms.txt (21 KiB, 129 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a title
https://ae.goldenscent.com/c/best-sellers/best-sellers-on-sale, https://ae.goldenscent.com/c/perfumes, https://ae.goldenscent.com/c/perfumes/men, https://ae.goldenscent.com/c/perfumes/women, https://ae.goldenscent.com/c/perfumes/kids and https://ae.goldenscent.com/c/perfumes/niche and 9 others have no <title>, so Google invents the link text in results.
15 pages without a meta description
https://ae.goldenscent.com/c/best-sellers/best-sellers-on-sale, https://ae.goldenscent.com/c/perfumes, https://ae.goldenscent.com/c/perfumes/men, https://ae.goldenscent.com/c/perfumes/women, https://ae.goldenscent.com/c/perfumes/kids and https://ae.goldenscent.com/c/perfumes/niche and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://ae.goldenscent.com/c/best-sellers/best-sellers-on-sale, https://ae.goldenscent.com/c/perfumes, https://ae.goldenscent.com/c/perfumes/men, https://ae.goldenscent.com/c/perfumes/women, https://ae.goldenscent.com/c/perfumes/kids and https://ae.goldenscent.com/c/perfumes/niche 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 197 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
2 third-party cookies
2 third-party cookies are 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 “Cannot read properties of undefined (reading 'getRegistrations')”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
65 of 69 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.
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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 37 words
The homepage has only about 37 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
10 short forms
10 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 4 phone links and 2 email links.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 ae.goldenscent.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on ae.goldenscent.com, including 19 speed issues, 1 SEO issue and 5 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.