simplyo3.com website review

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

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

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

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

8 third-party services load with your homepage (ZenDesk, Google Tag Manager and cloudfront.net and others), adding 2.1 MB and 2.0 s of main-thread time.

ZenDesk costs a phone 584 ms of main-thread work and 476 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.

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

10 KiB could be saved by minifying CSS.

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

cloudfront.net costs a phone 244 ms of main-thread work and 387 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.

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

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

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

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

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

Your largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “getting-started-with-ozone-img-lg.jpg__PID:f995e514-c02c-49…”.

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

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

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

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

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

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-11-07, real Chrome visitors' tap response (inp) went from 103 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.8 MB in 231 requests on a phone: scripts 2.4 MB (88), other files 797 KiB (110) and fonts 214 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example getting-started-with-ozone-img-lg_8cbc0580-4ca8-4f5d-a716-35 at 1,049 px wide, shown at 344 px. Resized copies would save about 2 KiB.

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

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

Some list items are not inside a list.

All page content should be contained by landmarks: 61 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.

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

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

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

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

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

The homepage links to 62 pages on simplyo3.com and 13 external pages.

https://www.simplyo3.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.simplyo3.com/products/black-friday-ozone-kit and https://www.simplyo3.com/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.simplyo3.com/customer_authentication/redirect and https://www.simplyo3.com/collections/ozone-add-ons have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.simplyo3.com/collections/all-products, https://www.simplyo3.com/collections/all-products/Group_Glassware and https://www.simplyo3.com/collections/all-products/Group_Oxygen use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.simplyo3.com/collections/all-products/Group_Glassware, whose canonical is https://www.simplyo3.com/collections/all-products/group_glassware. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.simplyo3.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 817 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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 19 cookies, 2 of them by other companies (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 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.