Website review, no card needed
danubehome.com website review
Visit site (opens in a new tab)Reviewed 3 November 202651 issues · 93 checks
This review found 51 issues worth fixing on danubehome.com, 23 of them high impact, across 93 checks. The most urgent: improve image delivery. 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 16, 2026 | 2.6 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 175 ms |
| May 23, 2026 | 164 ms |
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 152 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 159 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 182 ms |
| Aug 1, 2026 | 188 ms |
| Aug 8, 2026 | 193 ms |
| Aug 15, 2026 | 195 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 190 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 186 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 183 ms |
| Oct 10, 2026 | 185 ms |
| Oct 17, 2026 | 188 ms |
| Oct 24, 2026 | 194 ms |
| Oct 31, 2026 | 195 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.2 s
2.5 s
3.7 s
4.9 s
6.1 s
7.4 s
8.6 s
9.8 s
Speed
Improve image delivery
10.1 s · 7.2 MB91 images could be 7.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.1 s faster on a phone.
Reduce unused JavaScript
5.3 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 4.2 MB39 files are served with short cache lifetimes, so returning visitors download them again (4.2 MB).
Render-blocking requests
1.6 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Google Tag Manager adds 1.5 s
1.5 sGoogle Tag Manager costs a phone 1.5 s of main-thread work and 980 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 11.9 s
A phone's processor spends 11.9 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 18
18/100Your mobile performance score is 18. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8,030 HTML elements
The page has 8,030 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 (Google Tag Manager, Facebook and moengage.com and others), adding 2.0 MB and 2.0 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 520 ms. During a long task the page ignores taps.
Reduce unused CSS
310 ms · 66 KiBAbout 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Facebook adds 286 ms
286 msFacebook costs a phone 286 ms of main-thread work and 314 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.
moengage.com adds 67 ms
67 msmoengage.com costs a phone 67 ms of main-thread work and 437 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
35 KiBPolyfills for old browsers add 35 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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 34 ms
34 msYour server sent the HTML in 34 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.90
0.90For real visitors the layout shifts by 0.90 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 83.8 s
83.8 sYour largest element takes 83.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MRU26-MB-P-B1-Static”.
Time to Interactive: 88.9 s
88.9 sThe page becomes fully interactive after 88.9 s. Good is under 3.8 s.
Speed Index: 12.7 s
12.7 sVisually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.279
0.279The layout shifts by 0.279 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 220 ms
220 msReal visitors wait 220 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 175 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Images and page weight
Page weight: 29.6 MB in 440 requests
29.6 MBYour homepage downloads 29.6 MB in 440 requests on a phone: images 22.4 MB (272), media 3.8 MB (1) and scripts 2.9 MB (77). Under 2 MB keeps phones on slow connections fast.
40 images far larger than shown
6.3 MB40 images are downloaded at several times the size a phone draws them, for example mobile-en-1793443648529.gif at 586 px wide, shown at 84 px. Resized copies would save about 6.3 MB.
1 image over 500 KB
mobile-en-1793443648529.gif weighs 623 KiB. On a phone connection a single image that size takes seconds.
39 images below the first screen load straight away
39 images further down the page (7.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
24 images in older formats
24 images (5.2 MB) 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.
About 8.4 g of CO₂ per visit
8.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.39 g of CO₂e: 1006.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
185 text elements with low contrast
185 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Hidden but focusable
7 elements hidden from screen readers can still receive keyboard focus.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 453 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 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 long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
1,137 internal links, 24 external
The homepage links to 1,137 pages on danubehome.com and 24 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Best Furniture and Home Furnishing Stores in the UAE”.
Title: 61 characters
Your title is a healthy 61 characters: “Furniture Stores in Dubai | Home Furnishing | Danube Home UAE”.
Canonical URL set
The canonical URL is https://www.danubehome.com/ae/en.
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://www.danubehome.com/ae/en/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (4,706 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.danubehome.com/llms.txt (67 KiB, 297 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a title
https://www.danubehome.com/ae/en/catalogsearch, https://www.danubehome.com/ae/en/landing-cz/Garden2026-LP and https://www.danubehome.com/ae/en/landing-cz/Appliance-Page have no <title>, so Google invents the link text in results.
5 linked pages hidden from search
https://www.danubehome.com/ae/en/store-locator, https://www.danubehome.com/ae/en/landing-cz/Garden2026-LP, https://www.danubehome.com/ae/en/landing-cz/uae-decor, https://www.danubehome.com/ae/en/landing-cz/u25-furnishing-landing-page and https://www.danubehome.com/ae/en/landing-cz/Appliance-Page are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.danubehome.com/ae/en and https://www.danubehome.com/ae/en/landing-cz/u25-furnishing-landing-page all use the title “Furniture Stores in Dubai | Home Furnishing | Danube Home UAE”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.danubehome.com/ae/en/catalogsearch, https://www.danubehome.com/ae/en/landing-cz/Garden2026-LP and https://www.danubehome.com/ae/en/landing-cz/Appliance-Page have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.danubehome.com/ae/en/bulk-order, https://www.danubehome.com/ae/en/landing-cz/Garden2026-LP, https://www.danubehome.com/ae/en/landing-cz/uae-decor, https://www.danubehome.com/ae/en/landing-cz/u25-furnishing-landing-page and https://www.danubehome.com/ae/en/landing-cz/Appliance-Page 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 194 found) and read each the way a search engine does.
2 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.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
245 of 253 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 3,622 words of copy
The homepage carries about 3,622 words of visible text.
4 checks passed
11 calls to action
The homepage has 11 calls to action, for example “Track Order”, “Buy In Bulk” and “Sign Up NowGet Exclusive Benefits”.
2 short forms
2 short forms (0 fields at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Tag Manager and Meta 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
18 other companies contacted
Loading the homepage contacts 18 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 danubehome.com, 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
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on danubehome.com, including 25 speed issues, 1 SEO issue and 4 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.