Website review, no card needed
jaresortshotels.com website review
Visit site (opens in a new tab)Reviewed 1 November 202657 issues · 99 checks
This review found 57 issues worth fixing on jaresortshotels.com, 28 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.0 s |
| May 16, 2026 | 6.0 s |
| May 23, 2026 | 5.9 s |
| May 30, 2026 | 5.7 s |
| Jun 6, 2026 | 5.7 s |
| Jun 13, 2026 | 5.6 s |
| Jun 20, 2026 | 5.5 s |
| Jun 27, 2026 | 5.8 s |
| Jul 4, 2026 | 5.6 s |
| Jul 11, 2026 | 5.4 s |
| Jul 18, 2026 | 5.3 s |
| Jul 25, 2026 | 5.0 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.5 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 5.6 s |
| Sep 5, 2026 | 6.1 s |
| Sep 12, 2026 | 6.2 s |
| Sep 19, 2026 | 6.4 s |
| Sep 26, 2026 | 6.4 s |
| Oct 3, 2026 | 6.3 s |
| Oct 10, 2026 | 6.3 s |
| Oct 17, 2026 | 6.0 s |
| Oct 24, 2026 | 5.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 298 ms |
| May 16, 2026 | 301 ms |
| May 23, 2026 | 295 ms |
| May 30, 2026 | 279 ms |
| Jun 6, 2026 | 287 ms |
| Jun 13, 2026 | 286 ms |
| Jun 20, 2026 | 283 ms |
| Jun 27, 2026 | 302 ms |
| Jul 4, 2026 | 302 ms |
| Jul 11, 2026 | 305 ms |
| Jul 18, 2026 | 322 ms |
| Jul 25, 2026 | 323 ms |
| Aug 1, 2026 | 320 ms |
| Aug 8, 2026 | 320 ms |
| Aug 15, 2026 | 314 ms |
| Aug 22, 2026 | 350 ms |
| Aug 29, 2026 | 458 ms |
| Sep 5, 2026 | 551 ms |
| Sep 12, 2026 | 573 ms |
| Sep 19, 2026 | 637 ms |
| Sep 26, 2026 | 691 ms |
| Oct 3, 2026 | 705 ms |
| Oct 10, 2026 | 705 ms |
| Oct 17, 2026 | 677 ms |
| Oct 24, 2026 | 534 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
1.2 s
2.5 s
3.7 s
4.9 s
6.2 s
7.4 s
8.6 s
9.8 s
Speed
Reduce unused JavaScript
12.2 s · 2.2 MBAbout 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.2 s faster on a phone.
Use efficient cache lifetimes
3.3 s · 680 KiB37 files are served with short cache lifetimes, so returning visitors download them again (680 KiB).
Google Tag Manager adds 2.0 s
2.0 sGoogle Tag Manager costs a phone 2.0 s of main-thread work and 2.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.2 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.9 s
A phone's processor spends 9.9 s on main-thread work while loading, 6.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7,660 HTML elements
The page has 7,660 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 (Google Tag Manager, Sojern and Facebook and others), adding 4.5 MB and 4.2 s of main-thread time.
Improve image delivery
1.8 MB13 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
600 ms · 121 KiBAbout 121 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 625 ms. During a long task the page ignores taps.
Sojern adds 578 ms
578 msSojern costs a phone 578 ms of main-thread work and 77 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 375 ms
375 msFacebook costs a phone 375 ms of main-thread work and 365 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 281 ms
281 msGoogle CDN costs a phone 281 ms of main-thread work and 736 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.
triptease.io adds 227 ms
227 mstriptease.io costs a phone 227 ms of main-thread work and 491 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.
Legacy JavaScript
71 KiBPolyfills for old browsers add 71 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
23 KiB23 KiB could be saved by minifying CSS.
Minify JavaScript
19 KiB19 KiB could be saved by minifying JavaScript.
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: 46 ms
46 msYour server sent the HTML in 46 ms, well inside Google's 600 ms guideline.
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.
Real-user LCP: 6.8 s
6.8 sReal visitors wait 6.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 601 ms
601 msReal visitors wait 601 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 5.3 s
5.3 sReal visitors see the first content after 5.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.8 s
3.8 sReal visitors wait 3.8 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 8.3 s
8.3 sThe first text or image appears after 8.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 45.7 s
45.7 sYour largest element takes 45.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies on our website to give you the most relevant…”.
Speed Index: 25.5 s
25.5 sVisually, the page fills in at 25.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 48.9 s
48.9 sThe page becomes fully interactive after 48.9 s. Good is under 3.8 s.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 102% slower for real visitors
+102%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 298 ms to 534 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.0 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.026
0.026The layout barely moves while loading (CLS 0.026, good is under 0.1).
Images and page weight
Page weight: 9.4 MB in 317 requests
9.4 MBYour homepage downloads 9.4 MB in 317 requests on a phone: scripts 5.4 MB (90), images 2.9 MB (75) and other files 485 KiB (116). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
agl_2x-1792319175.png weighs 490 KiB. On a phone connection a single image that size takes seconds.
5 images far larger than shown
631 KiB5 images are downloaded at several times the size a phone draws them, for example agl_2x-1792319175.png at 1,234 px wide, shown at 320 px. Resized copies would save about 631 KiB.
16 images in older formats
16 images (2.3 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.
17 images below the first screen load straight away
17 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.65 g of CO₂e: 318.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
13 form fields without a label
13 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (78 characters)
Your title is 78 characters, so Google will cut it off around 60: “Luxury Hotels in Dubai, Maldives, Scotland | Official Site JA Resorts & Hotels”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
17 links crawlers can't follow
17 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
40 internal links, 0 external
The homepage links to 40 pages on jaresortshotels.com and 0 external pages.
5 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Whatever your dream escape looks like, JA Resorts & Hotels makes it a reality. Explore luxury hotels in Dubai crafted f…”.
Canonical URL set
The canonical URL is https://www.jaresortshotels.com/.
Structured data in place
Structured data found: Hotel.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.jaresortshotels.com/sitemap/sitemap.xml.
AI search readiness
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (7,503 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.jaresortshotels.com/llms.txt (1 KiB, 0 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.jaresortshotels.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
1 linked page hidden from search
https://www.jaresortshotels.com/festive is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://www.jaresortshotels.com/home all use the title “Luxury Hotels in Dubai, Maldives, Scotland | Official Site JA Resorts…”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without an H1
https://www.jaresortshotels.com/home, https://www.jaresortshotels.com/festive, https://www.jaresortshotels.com/dubai/ja-beach-hotel, https://www.jaresortshotels.com/dubai/ja-palm-tree-court, https://www.jaresortshotels.com/dubai/ja-lake-view-hotel and https://www.jaresortshotels.com/dubai/ja-ocean-view-hotel and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=13006875&Ver=2&mid=2f048fc9-e77a-4321-8400-99675f09ebe6&bo=1&sid=519d58a0d64111f1a9c8f9d8854ec0ac&vid=519d8ce0d64111f1a7fa7d347be424fd&vids=1&msclkid=N&pi=918639831&lg.
10 small tap targets
10 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “The source list for Content Security Policy directive 'script-src' contains a source with an invalid path: 'https://www.jaresortshotels.com/widget-loa…”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 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 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 572 words of copy
The homepage carries about 572 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Book Now”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
33 cookies set on arrival
33Opening the homepage sets 33 cookies (measured from a US location before any click).
55 other companies contacted
Loading the homepage contacts 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 jaresortshotels.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
- Sitefinity 15.3.8500.0 DX
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on jaresortshotels.com, including 27 speed issues, 4 SEO issues and 4 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.