omeir.com website review

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

Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.

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

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

About 354 KiB of JavaScript is downloaded but never used on this page.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and cloudflare.com and others), adding 686 KiB and 397 ms of main-thread time.

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

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Omeir Travel Agency LLC”.

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 3.0 MB in 71 requests on a phone: images 1.0 MB (25), scripts 884 KiB (16) and other files 759 KiB (14). Under 2 MB keeps phones on slow connections fast.

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

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

8 images have no alt text, which hurts accessibility and image search.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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 on the page fails this check, rated moderate by axe-core.

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

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.omeir.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 81 pages on omeir.com and 12 external pages.

https://www.omeir.com/packages/all, https://www.omeir.com/packages/all/theme/city-breaks, https://www.omeir.com/packages/all/theme/luxury-charm, https://www.omeir.com/packages/all/theme/natures-wonders, https://www.omeir.com/packages/all/theme/safari-thrills and https://www.omeir.com/packages/all/theme/staycation-getaways all use the title “Holiday Package Deals UAE - Omeir Travel Agency LLC”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.omeir.com/contact, https://www.omeir.com/packages/holidays, https://www.omeir.com/packages/luxury, https://www.omeir.com/cargo, https://www.omeir.com/about-us/british-airways-ba and https://www.omeir.com/about-us/gulf-air-gf and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.omeir.com/packages/all, https://www.omeir.com/packages/all/theme/city-breaks, https://www.omeir.com/packages/all/theme/luxury-charm, https://www.omeir.com/packages/all/theme/natures-wonders, https://www.omeir.com/packages/all/theme/safari-thrills and https://www.omeir.com/packages/all/theme/staycation-getaways use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.omeir.com/packages/all/theme/city-breaks, whose canonical is https://www.omeir.com/packages/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.omeir.com/contact, https://www.omeir.com/visa, https://www.omeir.com/cargo, https://www.omeir.com/about-us/british-airways-ba, https://www.omeir.com/about-us/gulf-air-gf and https://www.omeir.com/about-us/qantas-airways-qf have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.omeir.com/contact took over 3 s to send its HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 334 words of visible text.

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.

Opening the homepage sets 4 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.