roxy.ca website review

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

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

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

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Noibu and Shopify and others), adding 6.5 MB and 1.2 s of main-thread time.

22 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

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

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

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

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

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

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

Klaviyo costs a phone 144 ms of main-thread work and 515 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.

Attentive costs a phone 37 ms of main-thread work and 915 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.

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

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

12 KiB could be saved by minifying JavaScript.

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

Real visitors wait 535 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A festive holiday-themed collage with two women dancing joy…”.

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

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

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

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

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

Your homepage downloads 9.7 MB in 523 requests on a phone: images 4.8 MB (144), scripts 3.4 MB (204) and other files 884 KiB (142). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example RX_263_SNOW_US_LUTTON_4834-2.png at 2,272 px wide, shown at 390 px. Resized copies would save about 575 KiB.

1 image further down the page (387 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 401 pages on roxy.ca and 7 external pages.

https://www.roxy.com/pages/gift-guide and https://www.roxy.com/collections/all-gifts all use the title “Holiday Gifts for Women & Girls | ROXY”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.roxy.com/pages/the-snow-shop, https://www.roxy.com/collections/gifts-under-25, https://www.roxy.com/collections/gifts-under-50 and https://www.roxy.com/collections/gifts-under-100 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.roxy.com/pages/gift-guide and https://www.roxy.com/collections/all-gifts use the same meta description. A description written for each page earns more clicks.

https://www.roxy.com/collections/clothing-new-arrivals, https://www.roxy.com/pages/the-snow-shop, https://www.roxy.com/pages/gift-guide, https://www.roxy.com/collections/new-arrivals, https://www.roxy.com/pages/search-results and https://www.roxy.com/collections/all-gifts 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 132 found) and read each the way a search engine does.

10 images failed to load on a phone, for example https://www.roxy.com/.

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

Large scripts ship without source maps.

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

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

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