Website review, no card needed

grandiose.ae logo

grandiose.ae website review

Visit site (opens in a new tab)Reviewed 4 November 202663 issues · 87 checks

This review found 63 issues worth fixing on grandiose.ae, 26 of them high impact, across 87 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.8 s2.8 sMay 16Oct 314.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.4 s
Jul 11, 20263.5 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.7 s
Aug 22, 20263.8 s
Aug 29, 20263.9 s
Sep 5, 20264.1 s
Sep 12, 20264.4 s
Sep 19, 20264.8 s
Sep 26, 20265.1 s
Oct 3, 20265.5 s
Oct 10, 20265.3 s
Oct 17, 20265.0 s
Oct 24, 20264.6 s
Oct 31, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
264 ms197 msMay 16Oct 31238 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026223 ms
May 23, 2026213 ms
May 30, 2026208 ms
Jun 6, 2026205 ms
Jun 13, 2026207 ms
Jun 20, 2026211 ms
Jun 27, 2026216 ms
Jul 4, 2026220 ms
Jul 11, 2026225 ms
Jul 18, 2026227 ms
Jul 25, 2026226 ms
Aug 1, 2026228 ms
Aug 8, 2026227 ms
Aug 15, 2026226 ms
Aug 22, 2026225 ms
Aug 29, 2026228 ms
Sep 5, 2026227 ms
Sep 12, 2026233 ms
Sep 19, 2026241 ms
Sep 26, 2026245 ms
Oct 3, 2026256 ms
Oct 10, 2026255 ms
Oct 17, 2026252 ms
Oct 24, 2026245 ms
Oct 31, 2026238 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

Full-page screenshot of grandiose.ae (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. grandiose.ae at 1.5 s1.5 s
  2. grandiose.ae at 3.0 s3.0 s
  3. grandiose.ae at 4.4 s4.4 s
  4. grandiose.ae at 5.9 s5.9 s
  5. grandiose.ae at 7.4 s7.4 s
  6. grandiose.ae at 8.9 s8.9 s
  7. grandiose.ae at 10.3 s10.3 s
  8. grandiose.ae at 11.8 s11.8 s

Speed

19 to fix6
  • Render-blocking requests

    15.1 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 15.1 s.

  • Improve image delivery

    5.8 s · 1.2 MB

    21 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.8 s faster on a phone.

  • Reduce unused JavaScript

    5.4 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.

  • Use efficient cache lifetimes

    2.3 s · 475 KiB

    18 files are served with short cache lifetimes, so returning visitors download them again (475 KiB).

  • Reduce unused CSS

    1.2 s · 259 KiB

    About 259 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 6

    6/100

    Your mobile performance score is 6. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 9.3 s

    A phone's processor spends 9.3 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 4,042 HTML elements

    The page has 4,042 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 (Facebook, Google Tag Manager and ZenDesk and others), adding 2.4 MB and 2.4 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.7 s. During a long task the page ignores taps.

  • Document request latency

    800 ms

    The 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

    777 ms

    Reduce initial server response time. Google estimates savings of 777 ms on a phone.

  • Facebook adds 663 ms

    663 ms

    Facebook costs a phone 663 ms of main-thread work and 399 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

    700 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).

  • Google Tag Manager adds 573 ms

    573 ms

    Google Tag Manager costs a phone 573 ms of main-thread work and 540 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.

  • ZenDesk adds 347 ms

    347 ms

    ZenDesk costs a phone 347 ms of main-thread work and 477 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.

  • TikTok adds 291 ms

    291 ms

    TikTok costs a phone 291 ms of main-thread work and 291 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.

  • Google CDN adds 124 ms

    124 ms

    Google CDN costs a phone 124 ms of main-thread work and 349 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: 877 ms

    877 ms

    Your server takes 877 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Legacy JavaScript

    150 ms · 46 KiB

    Polyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 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.

Core Web Vitals

14 to fix0
  • 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.40

    For real visitors the layout shifts by 0.40 (75th percentile). Good is under 0.1.

  • First Contentful Paint: 16.2 s

    16.2 s

    The first text or image appears after 16.2 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 46.8 s

    46.8 s

    Your largest element takes 46.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Eat well, live well, stay happy. HOME DELIVERY Select Emira…”.

  • Speed Index: 26.7 s

    26.7 s

    Visually, the page fills in at 26.7 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 50.5 s

    50.5 s

    The page becomes fully interactive after 50.5 s. Good is under 3.8 s.

  • Cumulative Layout Shift: 0.687

    0.687

    The layout shifts by 0.687 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 1.5 s

    1.5 s

    Scripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 4.0 s

    4.0 s

    Real visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 284 ms

    284 ms

    Real visitors wait 284 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 31% slower for real visitors

    +31%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.8 s

    2.8 s

    Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 929 ms

    929 ms

    Real visitors wait 929 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 25 images without width and height

    25 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 11% slower for real visitors

    +11%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 223 ms to 238 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

1 to fix70
  • Page weight: 10.1 MB in 196 requests

    10.1 MB

    Your homepage downloads 10.1 MB in 196 requests on a phone: scripts 4.8 MB (44), images 4.0 MB (64) and other files 656 KiB (64). Under 2 MB keeps phones on slow connections fast.

  • About 2.9 g of CO₂ per visit

    2.87 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.87 g of CO₂e: 344.1 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

9 to fixGoogle 6784
  • [role]s are not contained by their required parent element

    [role]s are not contained by their required parent element (16 elements).

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (2 elements).

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 32 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

10 to fixGoogle 7554
  • 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 short (16 characters)

    Your title is only 16 characters: “Client Challenge”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 23 links crawlers can't follow

    23 links have no real href, so search engines can't follow them.

  • 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://www.grandiose.ae/sitemap.xml, so Google discovers your pages only by following links.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

1 checks passed
  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix83
  • 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.grandiose.ae/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.

1 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.

Best practices

3 to fixGoogle 4687
  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 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 “Failed to load resource: the server responded with a status of 401 ()”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 13 words

    The homepage has only about 13 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening 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 grandiose.ae, 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 © 2025.

Stack

E-commerce
Magento
Analytics
Google Tag Manager
Hosting
Fastly

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 63 issues on grandiose.ae, including 33 speed issues, 10 SEO issues and 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25