Website review, no card needed
maidubaiwater.com website review
Visit site (opens in a new tab)Reviewed 1 November 202652 issues · 92 checks
This review found 52 issues worth fixing on maidubaiwater.com, 21 of them high impact, across 92 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
70C- #105,238 of 126,508 reviewed websitesbeats 14%
- #63,277 of 70,497 online storesbeats 8%
- #2,278 of 2,974 WooCommerce storesbeats 19%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 142 ms |
| May 16, 2026 | 139 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 151 ms |
| Aug 22, 2026 | 149 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 149 ms |
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 157 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 157 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
3.7 s
7.4 s
11.1 s
14.8 s
18.5 s
22.2 s
25.9 s
29.6 s
Speed
Use efficient cache lifetimes
21.3 s · 5.1 MB91 files are served with short cache lifetimes, so returning visitors download them again (5.1 MB).
Render-blocking requests
10.3 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 10.3 s.
Improve image delivery
6.3 s · 2.1 MB16 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.3 s faster on a phone.
Reduce unused CSS
4.5 s · 887 KiBAbout 887 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Reduce unused JavaScript
2.9 s · 486 KiBAbout 486 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.
Font display
2.2 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.2 s).
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Document request latency
800 ms · 48 KiBThe HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
796 msReduce initial server response time. Google estimates savings of 796 ms on a phone.
Minify JavaScript
300 ms · 67 KiB67 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 225 ms
225 msGoogle Tag Manager costs a phone 225 ms of main-thread work and 305 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.
Server response: 896 ms
896 msYour server takes 896 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Facebook and Unpkg and others), adding 580 KiB and 405 ms of main-thread time.
Legacy JavaScript
100 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.
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
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 538 ms of it running JavaScript. That is comfortably low.
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.
First Contentful Paint: 8.6 s
8.6 sThe first text or image appears after 8.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 36.0 s
36.0 sYour largest element takes 36.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 36.2 s
36.2 sVisually, the page fills in at 36.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 37.5 s
37.5 sThe page becomes fully interactive after 37.5 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.431
0.431The layout shifts by 0.431 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 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.
45 images without width and height
45 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 203 ms
203 msScripts block taps and scrolling for 203 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 142 ms to 157 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-24, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 171 ms
171 msReal visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 6.8 MB in 101 requests
6.8 MBYour homepage downloads 6.8 MB in 101 requests on a phone: images 4.4 MB (45), scripts 1.1 MB (27) and stylesheets 958 KiB (21). Under 2 MB keeps phones on slow connections fast.
19 images far larger than shown
5.7 MB19 images are downloaded at several times the size a phone draws them, for example NPD_Banner-1.png at 2,561 px wide, shown at 390 px. Resized copies would save about 5.7 MB.
1 image over 500 KB
NPD_Banner-1.png weighs 3.7 MB. On a phone connection a single image that size takes seconds.
23 images in older formats
23 images (8.1 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.
8 images below the first screen load straight away
8 images further down the page (982 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.92 g of CO₂e: 231.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Mai Dubai Water – Bottled Drinking Water Delivery Company in Dubai”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://serveruat.com/maidubai-new/sitemap.xml, so Google discovers your pages only by following links.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
44 internal links, 13 external
The homepage links to 44 pages on maidubaiwater.com and 13 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.maidubaiwater.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.
No llms.txt
There is no https://www.maidubaiwater.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 (332 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
/ and https://www.maidubaiwater.com/ar all use the title “Mai Dubai Water – Bottled Drinking Water Delivery Company in Dubai”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.maidubaiwater.com/ar, https://www.maidubaiwater.com/why-mai-dubai, https://www.maidubaiwater.com/about-us, https://www.maidubaiwater.com/sustainabilities, https://www.maidubaiwater.com/explore-our-products and https://www.maidubaiwater.com/whats-on and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.maidubaiwater.com/sustainability/recycling-initiative, whose canonical is https://www.maidubaiwater.com/sustainabilities. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.maidubaiwater.com/ar, https://www.maidubaiwater.com/careers and https://www.maidubaiwater.com/our-shop have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.maidubaiwater.com/ar and https://www.maidubaiwater.com/careers 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.
4 pages slow to respond
https://www.maidubaiwater.com/sustainabilities, https://www.maidubaiwater.com/our-shop, https://www.maidubaiwater.com/product-category/hygiene and https://www.maidubaiwater.com/sustainability/recycling-initiative took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 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.
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
20 small tap targets
20 of 87 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 309 words of copy
The homepage carries about 309 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join Us” and “Shop Now”.
3 calls to action
The homepage has 3 calls to action, for example “Join Us” and “Shop Now”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links 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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
6 other companies contacted
Loading the homepage contacts 6 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 maidubaiwater.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Moro
Company
- Founded
- 2012
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on maidubaiwater.com, including 23 speed issues, 7 SEO issues and 2 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.