omre.co website review

The page goes through 1 redirect before it starts loading, costing about 7.7 s. Link and advertise the final URL directly.

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

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

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

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

8 third-party services load with your homepage (fbot.me, Facebook and Klaviyo and others), adding 1.3 MB and 1.5 s of main-thread time.

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

Polyfills for old browsers add 105 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

fbot.me costs a phone 296 ms of main-thread work and 323 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 costs a phone 274 ms of main-thread work and 226 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.

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

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

1 image could be 52 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

23 KiB could be saved by minifying JavaScript.

17 KiB JavaScript is shipped twice across bundles.

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.

5 KiB could be saved by minifying CSS.

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 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 253 ms to 279 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 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.6 MB in 507 requests on a phone: scripts 2.6 MB (178), other files 1.8 MB (232) and images 1.2 MB (70). Under 2 MB keeps phones on slow connections fast.

Color_Black_White_Mode_Light.svg 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).

5 images (382 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Banner 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 banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 form field has 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.

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

Elements with visible text labels do not have matching accessible names. (4 elements).

There are 4 <h1> headlines (“The Longevity”, “Standard” and “Founded by a doctor, for his family.”). One clear main headline is easier for people and search engines.

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

The homepage links to 58 pages on omre.co and 4 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://omre.co/pages/money-back-guarantee is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://omre.co/pages/refer-a-friend has no meta description, so Google writes the search snippet from whatever text it finds.

https://omre.co/pages/refer-a-friend, https://omre.co/products/nmn-resveratrol, https://omre.co/products/urolithin-a, https://omre.co/products/liquid-turmeric, https://omre.co/products/quercetin-fisetin and https://omre.co/blogs/news/exercise-for-longevity and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://omre.co/products/nmn-resveratrol, https://omre.co/products/urolithin-a, https://omre.co/products/liquid-turmeric and https://omre.co/products/quercetin-fisetin have 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.

https://omre.co/products/urolithin-a, https://omre.co/products/quercetin-fisetin, https://omre.co/blogs/news/exercise-for-longevity, https://omre.co/blogs/news/how-often-to-get-nad-iv and https://omre.co/blogs/news/nmn-benefits-for-women took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://omre.co/.

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

1 error was logged to the browser console while the page loaded, for example “Unexpected token ';'”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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.

The homepage carries about 607 words of visible text.

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