khamashospitality.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google Maps and Cloudflare CDN and others), adding 2.0 MB and 1.1 s of main-thread time.

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

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.

Google Maps costs a phone 110 ms of main-thread work and 375 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.

Cloudflare CDN costs a phone 24 ms of main-thread work and 334 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.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 34.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Khamas Hospitality slide_0”.

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

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

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

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

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

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

Your homepage downloads 10.0 MB in 106 requests on a phone: images 7.6 MB (27), scripts 1.8 MB (40) and fonts 368 KiB (7). Under 2 MB keeps phones on slow connections fast.

4 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example 2068fc39-6166-4f34-bd39-431888d76f1a.png at 1,545 px wide, shown at 340 px. Resized copies would save about 4.0 MB.

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

13 images (4.2 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.

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

1 dropdown has no label.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 18 characters: “Khamas Hospitality”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 48 pages on khamashospitality.com and 10 external pages.

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.

The HTML your server sends has 752 of the 1,295 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

https://www.khamashospitality.com/about-us, https://www.khamashospitality.com/contact-us, https://www.khamashospitality.com/hotels/the-canvas-hotel-dubai, https://www.khamashospitality.com/hotels/mama-shelter-hotel-dubai, https://www.khamashospitality.com/hotels/double-tree-by-hilton-al-jadaf and https://www.khamashospitality.com/hotels/royal-ascot-hotel and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.khamashospitality.com/about-us, https://www.khamashospitality.com/upcoming-projects-khamas-hospitality, https://www.khamashospitality.com/our-hotels-khamas-hospitality, https://www.khamashospitality.com/contact-us, https://www.khamashospitality.com/ar and https://www.khamashospitality.com/hotels/the-canvas-hotel-dubai and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.khamashospitality.com/ar has 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.

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

5 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://macaron-assets.d-edge-webstudio.com/decookie.css' from origin 'https://www.khamash…”.

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.

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,295 words of visible text.

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

Opening the homepage sets 10 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.