odysseyelixir.com website review

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

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

Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

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

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

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

Shopify costs a phone 122 ms of main-thread work and 719 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 1,901 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Shopify, userway.org and sealsubscriptions.com and others), adding 979 KiB and 191 ms of main-thread time.

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

47 KiB could be saved by minifying JavaScript.

15 KiB could be saved by minifying CSS.

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

Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A woman in a black bikini holds a yellow can, smiling by a …”.

The layout shifts by 0.252 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

Your homepage downloads 22.6 MB in 327 requests on a phone: media 18.6 MB (3), images 1.7 MB (34) and scripts 1.1 MB (165). Under 2 MB keeps phones on slow connections fast.

Variety_Pack_Cans.webp weighs 651 KiB. On a phone connection a single image that size takes seconds.

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

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

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

Your title is only 25 characters: “Odyssey Functional Energy”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 11 <h1> headlines (“Odyssey Functional Energy”, “Energy. Focus. No Crash.” and “222 LINE electric energy”). One clear main headline is easier for people and search engines.

Your meta description is 254 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.

The homepage links to 99 pages on odysseyelixir.com and 11 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.odysseyfunctionalenergy.com/pages/5-reasons-why-222 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.odysseyfunctionalenergy.com/collections/85, https://www.odysseyfunctionalenergy.com/pages/shop-by-flavor, https://www.odysseyfunctionalenergy.com/pages/5-reasons-why-222, https://www.odysseyfunctionalenergy.com/pages/store-locator, https://www.odysseyfunctionalenergy.com/blogs/news and https://www.odysseyfunctionalenergy.com/pages/blogs and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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