rougecare.ca website review

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

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 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 4.6 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, loox.io and Affirm and others), adding 1.5 MB and 1.3 s of main-thread time.

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

5 images could be 224 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.

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

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

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

About 41 KiB of CSS is downloaded but never applied on this page.

11 KiB could be saved by minifying CSS.

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 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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 90 ms to 104 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.9 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.2 MB in 276 requests on a phone: media 6.6 MB (1), scripts 2.0 MB (113) and other files 685 KiB (101). Under 2 MB keeps phones on slow connections fast.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 72 characters, so Google will cut it off around 60: “Rouge Red Light Therapy | Red and Near Infrared LED Devices – Rouge Care”.

Your meta description is 295 characters; Google truncates after about 160, so the end of your pitch is cut.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 85 pages on rougecare.ca and 8 external pages.

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

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

https://rouge.care/pages/commercial-red-light-therapy, https://rouge.care/pages/help-center and https://rouge.care/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://rouge.care/collections/red-light-therapy-panels, https://rouge.care/collections/rouge-g4-panels and https://rouge.care/collections/rouge-g5-red-light-therapy-panels use the same meta description. A description written for each page earns more clicks.

https://rouge.care/blogs/rouge-red-light-therapy-blog, https://rouge.care/pages/what-are-the-benefits-of-red-light-therapy, https://rouge.care/pages/red-light-therapy-reviews-rouge and https://rouge.care/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

https://rouge.care/blogs/rouge-red-light-therapy-blog, https://rouge.care/pages/what-are-the-benefits-of-red-light-therapy and https://rouge.care/customer_authentication/redirect took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=17319554&Ver=2&mid=5b6cceae-0e35-4f56-a187-f4ba1f5b2e68&bo=1&sid=90970c00dd1711f1ba766d4f47b1baba&vid=90974670dd1711f1822d2fd922e3ec4e&vids=1&msclkid=N&pi=918639831&lg.

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

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://rouge.care/cdn/shop/t/125/assets/section-dual-image-with-text.min.css?v=21064' bec…”.

The homepage carries about 532 words of visible text.

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