raylena.com website review

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

2 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, 926 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Shopify and others), adding 748 KiB and 390 ms of main-thread time.

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

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

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

About 154 KiB of JavaScript is downloaded but never used on this page.

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

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

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

3 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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 2.6 MB in 261 requests on a phone: other files 1.1 MB (157), images 664 KiB (21) and scripts 592 KiB (65). Under 2 MB keeps phones on slow connections fast.

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

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

All page content should be contained by landmarks: 9 elements on the page fail 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.

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. (2 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 7 characters: “Raylena”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“”, “Power, Not Powder.” and “Stronger You.”). One clear main headline is easier for people and search engines.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 42 pages on raylena.com and 9 external pages.

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

https://raylena.com/products/5-flavors-creatine-monohydrate-gummies-5g-per-serving-150-count and https://raylena.com/products/strawberry-creatine-monohydrate-gummies declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://raylena.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, https://raylena.com/products/5-flavors-creatine-monohydrate-gummies-5g-per-serving-150-count, https://raylena.com/apps/17TRACK and https://raylena.com/products/strawberry-creatine-monohydrate-gummies all use the title “Raylena”. Search engines can't tell which page to show for a search, so each competes with the others.

https://raylena.com/customer_authentication/redirect, https://raylena.com/collections/all, https://raylena.com/products/5-flavors-creatine-monohydrate-gummies-5g-per-serving-150-count, https://raylena.com/apps/17TRACK, https://raylena.com/products/strawberry-creatine-monohydrate-gummies and https://raylena.com/pages/protocol and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://raylena.com/customer_authentication/redirect, https://raylena.com/pages/contact and https://raylena.com/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

https://raylena.com/customer_authentication/redirect, https://raylena.com/products/5-flavors-creatine-monohydrate-gummies-5g-per-serving-150-count, https://raylena.com/apps/17TRACK and https://raylena.com/products/strawberry-creatine-monohydrate-gummies took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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 404 ()”.

Chrome logged issues while loading the page (“Cookie”).

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

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 1,018 words of visible text.

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