Website review, no card needed
goldenscent.com website review
Visit site (opens in a new tab)Reviewed 23 October 202640 issues · 79 checks
This review found 40 issues worth fixing on goldenscent.com, 17 of them high impact, across 79 checks. The most urgent: mobile performance score: 38. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.7 s |
| May 9, 2026 | 4.8 s |
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.8 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 171 ms |
| May 9, 2026 | 175 ms |
| May 16, 2026 | 176 ms |
| May 23, 2026 | 176 ms |
| May 30, 2026 | 177 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 177 ms |
| Jul 4, 2026 | 175 ms |
| Jul 11, 2026 | 174 ms |
| Jul 18, 2026 | 174 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 211 ms |
| Aug 8, 2026 | 250 ms |
| Aug 15, 2026 | 312 ms |
| Aug 22, 2026 | 351 ms |
| Aug 29, 2026 | 380 ms |
| Sep 5, 2026 | 402 ms |
| Sep 12, 2026 | 402 ms |
| Sep 19, 2026 | 379 ms |
| Sep 26, 2026 | 354 ms |
| Oct 3, 2026 | 303 ms |
| Oct 10, 2026 | 285 ms |
| Oct 17, 2026 | 281 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.0 s
2.0 s
3.0 s
4.0 s
5.0 s
6.0 s
7.0 s
8.0 s
Speed
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,910 HTML elements
The page has 4,910 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
1.8 MB5 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Insider and Snapchat and others), adding 1.3 MB and 1.7 s of main-thread time.
Reduce unused JavaScript
300 ms · 733 KiBAbout 733 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.
Render-blocking requests
900 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Google Tag Manager adds 813 ms
813 msGoogle Tag Manager costs a phone 813 ms of main-thread work and 697 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 668 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
380 KiB10 files are served with short cache lifetimes, so returning visitors download them again (380 KiB).
Legacy JavaScript
42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 68 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 39 ms
39 msYour server sent the HTML in 39 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: 20.9 s
20.9 sThe page becomes fully interactive after 20.9 s. Good is under 3.8 s.
Largest Contentful Paint: 7.9 s
7.9 sYour largest element takes 7.9 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”.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user INP: 393 ms
393 msReal visitors wait 393 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.
Tap response (INP) got 64% slower for real visitors
+64%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 171 ms to 281 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
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 FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 566 ms
566 msReal visitors wait 566 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 49% faster for real visitors
-49%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.7 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.044
0.044The layout barely moves while loading (CLS 0.044, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 146 requests
4.3 MBYour homepage downloads 4.3 MB in 146 requests on a phone: images 2.1 MB (40), scripts 1.8 MB (56) and HTML 328 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
image weighs 1.8 MB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (1.8 MB) is 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 1.2 g of CO₂ per visit
1.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
120 text elements with low contrast
120 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.
47 links without text
47 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 459 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.
673 internal links, 64 external
The homepage links to 673 pages on goldenscent.com and 64 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://www.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://www.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://www.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://www.goldenscent.com/c/best-sellers/best-sellers-on-sale, https://www.goldenscent.com/c/perfumes, https://www.goldenscent.com/c/perfumes/men, https://www.goldenscent.com/c/perfumes/women, https://www.goldenscent.com/c/perfumes/kids and https://www.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://www.goldenscent.com/c/best-sellers/best-sellers-on-sale, https://www.goldenscent.com/c/perfumes, https://www.goldenscent.com/c/perfumes/men, https://www.goldenscent.com/c/perfumes/women, https://www.goldenscent.com/c/perfumes/kids and https://www.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://www.goldenscent.com/c/best-sellers/best-sellers-on-sale, https://www.goldenscent.com/c/perfumes, https://www.goldenscent.com/c/perfumes/men, https://www.goldenscent.com/c/perfumes/women, https://www.goldenscent.com/c/perfumes/kids and https://www.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')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
121 of 126 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: 3 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 52 words
The homepage has only about 52 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 goldenscent.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on 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.