Website review, no card needed

dubaifuture.ae logo

dubaifuture.ae website review

Visit site (opens in a new tab)Reviewed 26 October 202644 issues · 84 checks

This review found 44 issues worth fixing on dubaifuture.ae, 17 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
3.2 s1.9 sMay 9Oct 243.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.6 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
276 ms162 msMay 9Oct 24261 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026182 ms
May 16, 2026183 ms
May 23, 2026187 ms
May 30, 2026186 ms
Jun 6, 2026180 ms
Jun 13, 2026177 ms
Jun 20, 2026175 ms
Jun 27, 2026177 ms
Jul 4, 2026182 ms
Jul 11, 2026185 ms
Jul 18, 2026194 ms
Jul 25, 2026200 ms
Aug 1, 2026206 ms
Aug 8, 2026209 ms
Aug 15, 2026214 ms
Aug 22, 2026220 ms
Aug 29, 2026219 ms
Sep 5, 2026226 ms
Sep 12, 2026229 ms
Sep 19, 2026232 ms
Sep 26, 2026242 ms
Oct 3, 2026246 ms
Oct 10, 2026252 ms
Oct 17, 2026263 ms
Oct 24, 2026261 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 dubaifuture.ae (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dubaifuture.ae at 0.4 s0.4 s
  2. dubaifuture.ae at 0.9 s0.9 s
  3. dubaifuture.ae at 1.3 s1.3 s
  4. dubaifuture.ae at 1.7 s1.7 s
  5. dubaifuture.ae at 2.1 s2.1 s
  6. dubaifuture.ae at 2.6 s2.6 s
  7. dubaifuture.ae at 3.0 s3.0 s
  8. dubaifuture.ae at 3.4 s3.4 s

Speed

12 to fix37
  • Improve image delivery

    21.1 s · 5.1 MB

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

  • Render-blocking requests

    3.9 s

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

  • Use efficient cache lifetimes

    1.1 s · 411 KiB

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

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 5.0 s

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

  • Reduce unused JavaScript

    600 ms · 2.3 MB

    About 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.9 MB and 1.7 s of main-thread time.

  • Reduce unused CSS

    900 ms · 149 KiB

    About 149 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Google Tag Manager adds 526 ms

    526 ms

    Google Tag Manager costs a phone 526 ms of main-thread work and 519 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 504 ms

    504 ms

    Google CDN costs a phone 504 ms of main-thread work and 734 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.

  • Facebook adds 418 ms

    418 ms

    Facebook costs a phone 418 ms of main-thread work and 336 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    69 KiB

    Polyfills for old browsers add 69 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    56 KiB

    56 KiB could be saved by minifying JavaScript.

  • Minify CSS

    10 KiB

    10 KiB could be saved by minifying CSS.

  • 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: 108 ms

    108 ms

    Your server sent the HTML in 108 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix67
  • 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.

  • Largest Contentful Paint: 27.2 s

    27.2 s

    Your largest element takes 27.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We reimagine, inspire and design Dubai’s future in collabor…”.

  • Time to Interactive: 42.5 s

    42.5 s

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

  • First Contentful Paint: 5.4 s

    5.4 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • Total Blocking Time: 851 ms

    851 ms

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

  • Real-user INP: 274 ms

    274 ms

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

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

    +44%

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

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

    +47%

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 911 ms

    911 ms

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

3 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 11.4 MB in 170 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 170 requests on a phone: images 6.4 MB (18), scripts 4.0 MB (96) and fonts 417 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    2.3 MB

    2 images are downloaded at several times the size a phone draws them, for example DFF-home.png at 1,600 px wide, shown at 350 px. Resized copies would save about 2.3 MB.

  • 6 images in older formats

    6 images (1.5 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.

  • 6 images below the first screen load straight away

    6 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.2 g of CO₂ per visit

    3.23 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.23 g of CO₂e: 387.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fixGoogle 8993
  • 3 tap targets too small

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

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9288
  • 10 H1 headlines

    There are 10 <h1> headlines (“About”, “Shaping theFUTURE” and “Dubai Future Foundation Launches Agentic AI for G…”). One clear main headline is easier for people and search engines.

  • Meta description is long (198 characters)

    Your meta description is 198 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 9 links with vague text

    9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 85 internal links, 17 external

    The homepage links to 85 pages on dubaifuture.ae and 17 external pages.

6 checks passed
  • Title: 53 characters

    Your title is a healthy 53 characters: “Dubai Future Foundation | Shaping The Future of Dubai”.

  • Canonical URL set

    The canonical URL is https://www.dubaifuture.ae/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.dubaifuture.ae/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.dubaifuture.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.

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 (836 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 3 linked pages hidden from search

    https://www.dubaifuture.ae/dubai-centre-for-artificial-intelligence, https://www.dubaifuture.ae/dubai-future-fellowship and https://www.dubaifuture.ae/dubai-future-readiness-index are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.dubaifuture.ae/hmc, https://www.dubaifuture.ae/research, https://www.dubaifuture.ae/dfac-courses, https://www.dubaifuture.ae/dubai-centre-for-artificial-intelligence, https://www.dubaifuture.ae/dubai-future-fellowship and https://www.dubaifuture.ae/dubai-future-readiness-index have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 59 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.dubaifuture.ae/wp-content/plugins/mamopay-payment-gateway/assets/frontend.css'…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    35 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 direct contact details

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

  • 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 657 words of copy

    The homepage carries about 657 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: “Register to Attend →”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Join Our Team”, “Register to Attend →” and “Apply Now →”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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 dubaifuture.ae, 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
React
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Headquarters
Dubai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on dubaifuture.ae, including 23 speed issues, 3 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

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