Website review, no card needed
royalfurniture.ae website review
Visit site (opens in a new tab)Reviewed 3 November 202640 issues · 84 checks
This review found 40 issues worth fixing on royalfurniture.ae, 12 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 12, 2026 | 190 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 184 ms |
| Oct 10, 2026 | 186 ms |
| Oct 17, 2026 | 193 ms |
| Oct 24, 2026 | 196 ms |
| Oct 31, 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
0.8 s
1.7 s
2.5 s
3.4 s
4.2 s
5.1 s
5.9 s
6.8 s
Speed
Use efficient cache lifetimes
3.3 s · 2.6 MB40 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Reduce unused JavaScript
2.9 s · 550 KiBAbout 550 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Improve image delivery
950 ms · 2.0 MB27 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. 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 (Google Tag Manager, Facebook and Clarity and others), adding 1.1 MB and 703 ms of main-thread time.
Google Tag Manager adds 355 ms
355 msGoogle Tag Manager costs a phone 355 ms of main-thread work and 517 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: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,559 HTML elements
The page has 1,559 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. 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 182 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
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: 25 ms
25 msYour server sent the HTML in 25 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 CLS: 0.40
0.40For real visitors the layout shifts by 0.40 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 20.0 s
20.0 sYour largest element takes 20.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hero banner 25%-75”.
Time to Interactive: 22.2 s
22.2 sThe page becomes fully interactive after 22.2 s. Good is under 3.8 s.
Speed Index: 12.9 s
12.9 sVisually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 208 ms
208 msReal visitors wait 208 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 818 ms
818 msReal visitors wait 818 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 206 ms
206 msScripts block taps and scrolling for 206 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 190 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 108 requests
4.1 MBYour homepage downloads 4.1 MB in 108 requests on a phone: images 2.5 MB (41), scripts 1.5 MB (37) and HTML 71 KiB (1). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
85677fd15992240c.webp weighs 1.1 MB. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
RF_MOBILE.webp 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).
4 images far larger than shown
30 KiB4 images are downloaded at several times the size a phone draws them, for example HOMEPAGE_DESIGN_MOBILE_HOMEPAGE_MOBILE-19_hFXd4ix.webp at 1,170 px wide, shown at 384 px. Resized copies would save about 30 KiB.
1 image below the first screen load straight away
1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 141.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
34 links without text
34 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 189 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Furniture Store | Furniture Online UAE SALE UPTO 50% OFF - Royal Furniture”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
118 internal links, 3 external
The homepage links to 118 pages on royalfurniture.ae and 3 external pages.
6 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Royal Furniture is a one-stop store for the best furniture in Dubai, UAE. PAY DAY SALE UPTO 50% OFF on Everything*. Buy…”.
One H1 headline
Your main headline reads: “Royal Furniture”.
Canonical URL set
The canonical URL is https://www.royalfurniture.ae/ae/en/.
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://www.royalfurniture.ae/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 (304 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.royalfurniture.ae/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://www.royalfurniture.ae/ae/en/help-center and https://www.royalfurniture.ae/ae/en/store-locator use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://www.royalfurniture.ae/ae/en/furniture, https://www.royalfurniture.ae/ae/en/sofas, https://www.royalfurniture.ae/ae/en/bedroom, https://www.royalfurniture.ae/ae/en/household, https://www.royalfurniture.ae/ae/en/cooltech-mattress and https://www.royalfurniture.ae/ae/en/kids-and-teens and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://www.royalfurniture.ae/ae/en/cooltech-mattress, https://www.royalfurniture.ae/ae/en/kids-and-teens, https://www.royalfurniture.ae/ae/en/amazing-deal/amazing-deal, https://www.royalfurniture.ae/ae/en/sofas/corner-sofas, https://www.royalfurniture.ae/ae/en/sofas/recliner and https://www.royalfurniture.ae/ae/en/furniture/living-room/end-table and 1 other 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 57 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 “Access to XMLHttpRequest at 'https://sdk-02.moengage.com/v2/websdksettings?app_id=EJ0XODFEHKM64TC3VL1SAM40' from origin…”.
11 distorted images
11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
41 of 43 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 250 words of copy
The homepage carries about 250 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call Royal Furniture” and “Open contact panel”.
4 calls to action
The homepage has 4 calls to action, for example “Track Order”, “Contact Us” and “Call Royal Furniture”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
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 Microsoft Clarity 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
20 other companies contacted
Loading the homepage contacts 20 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 royalfurniture.ae, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on royalfurniture.ae, including 19 speed issues, 3 SEO 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.