omnieye.com website review

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

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

Your mobile performance score is 62 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

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

2 images could be 214 KiB 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 48 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.

6 third-party services load with your homepage (Google Tag Manager, Optanon and omappapi.com and others), adding 531 KiB and 378 ms of main-thread time.

4 long tasks block the main thread while loading, the longest for 103 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).

Desktop scores 87 but mobile only 62. A gap that wide usually means heavy scripts and images that hit phones hardest.

Polyfills for old browsers add 9 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.

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

Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OMNI EYE SPECIALISTS + ICON EYECARE Omni Eye Specialists Sa…”.

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

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

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

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

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

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

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

1 image (39 KiB) is 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 0.34 g of CO₂e: 40.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 tap targets are too small or too close together to hit reliably with a finger.

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

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.

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.

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

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.

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

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

The homepage links to 246 pages on omnieye.com and 9 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.

There is no https://iconeyecare.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://iconeyecare.com/schedule-appointment-at-icon, https://iconeyecare.com/cataract-surgery-denver/symptoms, https://iconeyecare.com/cataract-surgery-denver/recovery and https://iconeyecare.com/eye-health-services have no meta description, so Google writes the search snippet from whatever text it finds.

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

10 of 37 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 “e.indexOf is not a function”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 809 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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