Website review, no card needed

aeontrisl.com logo

aeontrisl.com website review

Visit site (opens in a new tab)Reviewed 19 October 202623 issues · 73 checks

This review found 23 issues worth fixing on aeontrisl.com, 7 of them high impact, across 73 checks. The most urgent: fails Core Web Vitals for real visitors. 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.2 s3.0 sApr 25Oct 103.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.0 s
May 2, 20264.1 s
May 9, 20264.0 s
May 16, 20263.9 s
May 23, 20263.7 s
May 30, 20263.6 s
Jun 6, 20263.4 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.2 s
Aug 1, 20263.3 s
Aug 8, 20263.4 s
Aug 15, 20263.7 s
Aug 22, 20263.8 s
Aug 29, 20263.7 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.4 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
162 ms87 msApr 25Oct 10112 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026136 ms
May 2, 2026144 ms
May 9, 2026153 ms
May 16, 2026130 ms
May 23, 2026130 ms
May 30, 2026150 ms
Jun 6, 2026139 ms
Jun 13, 2026131 ms
Jun 20, 2026125 ms
Jun 27, 2026120 ms
Jul 4, 2026120 ms
Jul 11, 2026105 ms
Jul 18, 2026105 ms
Jul 25, 2026126 ms
Aug 1, 2026133 ms
Aug 8, 2026129 ms
Aug 15, 2026129 ms
Aug 22, 2026124 ms
Aug 29, 2026100 ms
Sep 5, 202698 ms
Sep 12, 202696 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 2026106 ms
Oct 10, 2026112 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 aeontrisl.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aeontrisl.com at 0.4 s0.4 s
  2. aeontrisl.com at 0.8 s0.8 s
  3. aeontrisl.com at 1.2 s1.2 s
  4. aeontrisl.com at 1.7 s1.7 s
  5. aeontrisl.com at 2.1 s2.1 s
  6. aeontrisl.com at 2.5 s2.5 s
  7. aeontrisl.com at 2.9 s2.9 s
  8. aeontrisl.com at 3.3 s3.3 s

Speed

1 to fix96
  • Render-blocking requests

    750 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

  • Improve image delivery

    85 KiB

    4 images could be 85 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 1 KiB and 0 ms of main-thread time.

3 checks passed
  • Mobile performance score: 96

    96/100

    Your mobile performance score is 96 (desktop: 99). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 33 ms of it running JavaScript. That is comfortably low.

  • Server response: 415 ms

    415 ms

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

Core Web Vitals

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Speed Index: 4.3 s

    4.3 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

8 checks passed
  • Real-user INP: 121 ms

    121 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 22% faster for real visitors

    -22%

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Largest Contentful Paint: 1.8 s

    1.8 s

    Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Buy Property In Downtown Dubai”.

  • Cumulative Layout Shift: 0.004

    0.004

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.8 s

    1.8 s

    The page is fully interactive after 1.8 s.

Images and page weight

2 to fix80
  • 6 images in older formats

    6 images (704 KiB) 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.

  • 1 image far larger than shown

    244 KiB

    1 image is downloaded at several times the size a phone draws it, for example Emaar-No-1-Agency-in-Dubai-2026.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 244 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (175 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.3 g of CO₂ per visit

    0.33 g

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

1 checks passed
  • Page weight: 1.2 MB in 20 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 20 requests on a phone: images 589 KiB (14), fonts 533 KiB (2) and HTML 45 KiB (1). That is a lean page.

Accessibility

7 to fixGoogle 8191
  • Malformed lists

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

  • 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 (17 elements)

    All page content should be contained by landmarks: 17 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.

  • Zoom is disabled

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

  • 25 form fields without a label

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

  • 5 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 32 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “Aeon & Trisl - Leading Real Estate Agency - Top Realtors Brokers in Dubai”.

  • 2 links crawlers can't follow

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

  • 95 internal links, 7 external

    The homepage links to 95 pages on aeontrisl.com and 7 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “As leading real estate brokers in Dubai, we represent prestigious developers like Emaar, Damac, Nakheel, and Sobha, off…”.

  • One H1 headline

    Your main headline reads: “Popular Areas in Dubai”.

  • Canonical URL set

    The canonical URL is https://aeontrisl.com/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://aeontrisl.com/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,109 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://aeontrisl.com/llms.txt (5 KiB, 45 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix0
  • 1 linked page is broken

    Your homepage links to https://aeontrisl.com/+97143957550, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'setAttribute')”.

  • 6 low-resolution images

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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.

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

    The homepage carries about 840 words of visible text.

6 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact”, “get in touch” and “Buy Ready Apartments in Dubai”.

  • 6 short forms

    6 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 10 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 7 phone links and 3 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 aeontrisl.com, 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
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on aeontrisl.com, including 7 speed issues, 2 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