omnes.com website review

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

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

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

The page has 5,015 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 2.3 MB and 2.5 s of main-thread time.

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

About 848 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

Shopify costs a phone 819 ms of main-thread work and 377 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.

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

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

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

Klaviyo costs a phone 395 ms of main-thread work and 637 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.

About 112 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.

83 KiB could be saved by minifying JavaScript.

PayPal costs a phone 242 ms of main-thread work and 392 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.

LoyaltyLion costs a phone 142 ms of main-thread work and 355 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.

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

12 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

Your homepage downloads 6.2 MB in 398 requests on a phone: scripts 2.5 MB (179), images 2.3 MB (29) and other files 940 KiB (158). Under 2 MB keeps phones on slow connections fast.

HOMEPAGE_BANNER_CAMPAIGN_5.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images are downloaded at several times the size a phone draws them, for example HOMEPAGE_BANNER_CAMPAIGN_5.png at 2,705 px wide, shown at 390 px. Resized copies would save about 378 KiB.

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

52 buttons have no accessible name, so screen readers announce just “button”.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“THE PARTY EDIT”, “THE PARTY EDIT” and “SHOP AW26”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 262 pages on omnes.com and 5 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.

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

1 image failed to load on a phone, for example https://www.omnes.com/en-us.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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 22 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.