Website review, no card needed
dr-scent.com website review
Visit site (opens in a new tab)Reviewed 1 November 202636 issues · 91 checks
This review found 36 issues worth fixing on dr-scent.com, 8 of them high impact, across 91 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
88B- #5,626 of 117,615 reviewed websitesbeats 93%
- #3,103 of 66,923 online storesbeats 93%
- #63 of 2,700 WooCommerce storesbeats 97%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 98 ms |
| May 16, 2026 | 97 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 130 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 91 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
Speed
Render-blocking requests
2.4 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1,014 KiB and 1.1 s of main-thread time.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 463 ms
463 msGoogle Tag Manager costs a phone 463 ms of main-thread work and 377 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
300 ms · 63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
360 KiB10 files are served with short cache lifetimes, so returning visitors download them again (360 KiB).
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 325 ms. During a long task the page ignores taps.
Reduce unused JavaScript
314 KiBAbout 314 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,804 HTML elements
The page has 1,804 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 150 KiB7 images could be 150 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.
Legacy JavaScript
69 KiBPolyfills for old browsers add 69 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 13.9 s
13.9 sThe page becomes fully interactive after 13.9 s. Good is under 3.8 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dr Scent October 2026 Offers”.
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 479 ms
479 msScripts block taps and scrolling for 479 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 98 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 78 ms
78 msReal visitors wait 78 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.
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.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 2.3 MB in 163 requests
2.3 MBYour homepage downloads 2.3 MB in 163 requests on a phone: scripts 1.3 MB (60), images 734 KiB (33) and stylesheets 172 KiB (34). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
29 text elements with low contrast
29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
20 images without alt text
20 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (57 elements)
All page content should be contained by landmarks: 57 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (5 elements)
Elements marked as presentational should be consistently ignored: 5 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
163 internal links, 13 external
The homepage links to 163 pages on dr-scent.com and 13 external pages.
8 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Discover Dr Scent’s premium aroma oils, diffusers & fragrance solutions in the UAE. Elevate your homes, offices, cars &…”.
One H1 headline
Your main headline reads: “Complete Scenting Solutions for Homes & Businesses in UAE”.
Title: 53 characters
Your title is a healthy 53 characters: “Dr Scent UAE | Premium Aroma Oils & Diffuser Machines”.
Canonical URL set
The canonical URL is https://dr-scent.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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://dr-scent.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,291 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://dr-scent.com/llms.txt (149 KiB, 537 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://dr-scent.com/product-category/aroma/fb, https://dr-scent.com/product-category/aroma/floral, https://dr-scent.com/product-category/aroma/fresh and https://dr-scent.com/product-category/diffuser/dispenser have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://dr-scent.com/shop, https://dr-scent.com/product-category/aroma/car-scent, https://dr-scent.com/product-category/aroma/dr-scents-choice, https://dr-scent.com/product-category/aroma/fb, https://dr-scent.com/product-category/aroma/floral and https://dr-scent.com/product-category/aroma/fresh and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://dr-scent.com/ar has 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 63 found) and read each the way a search engine does.
5 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.
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 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343223982&tm=gtm002&Ver=2&mid=21fcd669-0886-4935-ae79-f244114a5d40&bo=1&sid=51262fc0d5c311f1afc229c821b678fb&vid=51266d30d5c311f1a379ab7ff5482661&vids=1&msclkid=N>m_.
14 small tap targets
14 of 29 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.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map 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 773 words of copy
The homepage carries about 773 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP OFFERS”.
6 calls to action
The homepage has 6 calls to action, for example “SHOP OFFERS”, “Contact Now” and “Enquire More”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 29 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.
30 cookies set on arrival
30Opening the homepage sets 30 cookies (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.
29 other companies contacted
Loading the homepage contacts 29 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 dr-scent.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on dr-scent.com, including 19 speed issues and 1 conversion gap. 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.