Website review, no card needed

alrasikhoon.ae logo

alrasikhoon.ae website review

Visit site (opens in a new tab)Reviewed 25 October 202645 issues · 79 checks

This review found 45 issues worth fixing on alrasikhoon.ae, 16 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
4.9 s4.2 sMay 9Oct 174.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.8 s
Oct 3, 20264.3 s
Oct 10, 20264.3 s
Oct 17, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
155 ms136 msMay 9Oct 17153 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026149 ms
Oct 3, 2026144 ms
Oct 10, 2026138 ms
Oct 17, 2026153 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 alrasikhoon.ae (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alrasikhoon.ae at 1.2 s1.2 s
  2. alrasikhoon.ae at 2.3 s2.3 s
  3. alrasikhoon.ae at 3.5 s3.5 s
  4. alrasikhoon.ae at 4.7 s4.7 s
  5. alrasikhoon.ae at 5.9 s5.9 s
  6. alrasikhoon.ae at 7.0 s7.0 s
  7. alrasikhoon.ae at 8.2 s8.2 s
  8. alrasikhoon.ae at 9.4 s9.4 s

Speed

8 to fix35
  • Use efficient cache lifetimes

    1.9 s · 2.2 MB

    35 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

  • Reduce unused JavaScript

    1.3 s · 258 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Render-blocking requests

    600 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 561 KiB and 508 ms of main-thread time.

  • Improve image delivery

    300 ms · 125 KiB

    2 images could be 125 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 231 ms

    231 ms

    Google Tag Manager costs a phone 231 ms of main-thread work and 318 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: 2.5 s

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

  • 10 long tasks on the main thread

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

  • Reduce unused CSS

    26 KiB

    About 26 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

1 checks passed
  • Server response: 532 ms

    532 ms

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

Core Web Vitals

10 to fix33
  • 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 LCP: 4.3 s

    4.3 s

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

  • Real-user CLS: 0.50

    0.50

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

  • Largest Contentful Paint: 11.3 s

    11.3 s

    Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Speed Index: 15.5 s

    15.5 s

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

  • Time to Interactive: 11.9 s

    11.9 s

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

  • Cumulative Layout Shift: 0.422

    0.422

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Total Blocking Time: 305 ms

    305 ms

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

1 checks passed
  • Real-user INP: 142 ms

    142 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 121 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 121 requests on a phone: media 914 KiB (2), images 907 KiB (25) and scripts 785 KiB (44). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

6 to fixGoogle 8991
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 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 4 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

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

SEO

8 to fixGoogle 9254
  • 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 (24 characters)

    Your title is only 24 characters: “Al Rasikhoon Real Estate”. 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.

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

  • No robots.txt

    There is no robots.txt at alrasikhoon.ae/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 11 internal links, 3 external

    The homepage links to 11 pages on alrasikhoon.ae and 3 external pages.

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://alrasikhoon.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

3 to fix83
  • 9 pages share a title

    /, https://alrasikhoon.ae/contact, https://alrasikhoon.ae/about, https://alrasikhoon.ae/services, https://alrasikhoon.ae/projects and https://alrasikhoon.ae/projects-previous and 3 others all use the title “Al Rasikhoon Real Estate”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://alrasikhoon.ae/contact, https://alrasikhoon.ae/about, https://alrasikhoon.ae/services, https://alrasikhoon.ae/projects, https://alrasikhoon.ae/projects-previous and https://alrasikhoon.ae/blogs and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://alrasikhoon.ae/contact and https://alrasikhoon.ae/privacy have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://alrasikhoon.ae/contact, https://alrasikhoon.ae/about, https://alrasikhoon.ae/services, https://alrasikhoon.ae/projects, https://alrasikhoon.ae/projects-previous and https://alrasikhoon.ae/blogs and 2 others 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.

  • 1 page slow to respond

    https://alrasikhoon.ae/privacy took over 3 s to send its HTML from our server.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Hydration completed but contains mismatches.”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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 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 5 words

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

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

2 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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

    5

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 alrasikhoon.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
Nuxt
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on alrasikhoon.ae, including 18 speed issues, 8 SEO issues and 5 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