victoriousbeings.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and shgcdn3.com and others), adding 6.9 MB and 412 ms of main-thread time.

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

auglio.com costs a phone 20 ms of main-thread work and 6.2 MB 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.

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

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

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

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

About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 220 ms faster on a phone.

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

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

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

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 9.8 MB in 268 requests on a phone: other files 6.8 MB (101), images 1.6 MB (38) and scripts 1.1 MB (93). Under 2 MB keeps phones on slow connections fast.

ELIPSE_Large_140f8ec9-c9e0-456b-8ee4-37b6eb23208a.jpg 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).

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 87 characters, so Google will cut it off around 60: “Revitalize with Color Therapy Glasses | VictoriousBeings.com – Loving Victorious Beings”.

There are 4 <h1> headlines (“”, “More than protection.” and “An uplift for how you feel.”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/logo-pink_94aab80b-f007-4a30-909e-b937b92e3…”.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 159 pages on victoriousbeings.com and 8 external pages.

https://victoriousbeings.com/collections/elipse, https://victoriousbeings.com/collections/mayan, https://victoriousbeings.com/collections/hexagon and https://victoriousbeings.com/collections/blue-color-therapy use the same meta description. A description written for each page earns more clicks.

https://victoriousbeings.com/collections/elipse, https://victoriousbeings.com/collections/mayan, https://victoriousbeings.com/collections/hexagon, https://victoriousbeings.com/collections/lover, https://victoriousbeings.com/collections/creator and https://victoriousbeings.com/collections/supercat and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

10 of 41 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 “Uncaught (in promise) TypeError: Cannot destructure property 'name' of 'e' as it is undefined.”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 759 words of visible text.

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