roycechocolate.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.

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

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

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

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

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

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

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

Shopify costs a phone 104 ms of main-thread work and 548 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 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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.

Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ROYCE' Chocolate Collection Promotional Banner”.

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

Visually, the page fills in at 7.4 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 93 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Scripts block taps and scrolling for 347 ms in total while the page loads. Good is under 200 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' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.6 MB in 297 requests on a phone: scripts 2.8 MB (122), other files 1.1 MB (126) and images 414 KiB (26). Under 2 MB keeps phones on slow connections fast.

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

Your title is only 16 characters: “ROYCE' CHOCOLATE”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 132 pages on roycechocolate.com and 15 external pages.

https://roycechocolate.com/collections/gift-set and https://roycechocolate.com/collections/bars use the same meta description. A description written for each page earns more clicks.

https://roycechocolate.com/pages/sustainability-policy, https://roycechocolate.com/pages/royce-cacao-and-chocolate-town, https://roycechocolate.com/collections/all-products, https://roycechocolate.com/collections/best-sellers, https://roycechocolate.com/collections/gift-set and https://roycechocolate.com/collections/nama and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://roycechocolate.com/collections/nama, https://roycechocolate.com/collections/bars and https://roycechocolate.com/collections/online-exclusives have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

6 of 27 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 “$ is not defined”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 188 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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