sabateseye.com website review

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

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

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

11 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

8 third-party services load with your homepage (freshpaint-hipaa-maps.com, Google Tag Manager and jQuery CDN and others), adding 1.2 MB and 935 ms of main-thread time.

19 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

10 images could be 229 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

freshpaint-hipaa-maps.com costs a phone 452 ms of main-thread work and 810 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.

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

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

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

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

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.

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

Your largest element takes 12.9 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.

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

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

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

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

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

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

Your homepage downloads 2.4 MB in 101 requests on a phone: other files 890 KiB (27), images 807 KiB (39) and scripts 593 KiB (14). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (197 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (86 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 0.67 g of CO₂e: 80.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Elements must only use permitted ARIA attributes: 8 elements on the page fail this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 94 pages on sabateseye.com and 14 external pages.

Your Organization JSON-LD is missing 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://www.sabateseye.com/locations/university-health, https://www.sabateseye.com/eye-care-services/cataracts, https://www.sabateseye.com/eye-care-services/cataracts/check-cataract-symptoms, https://www.sabateseye.com/eye-care-services/cataracts/explore-treatment-options and https://www.sabateseye.com/eye-care-services/cataracts/learn-what-happens have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sabateseye.com/eye-care-services/cataracts/check-cataract-symptoms, https://www.sabateseye.com/eye-care-services/cataracts/explore-treatment-options and https://www.sabateseye.com/eye-care-services/cataracts/learn-what-happens have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

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

Before a visitor clicks anything, the page loads 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 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.