trollbeads.ca website review

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

About 195 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and rebuyengine.com and others), adding 2.4 MB and 1.0 s of main-thread time.

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

Google Tag Manager costs a phone 401 ms of main-thread work and 618 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 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

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

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

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

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

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

16 KiB could be saved by minifying CSS.

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

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.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A woman giving a Trollbeads gift box to another woman”.

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

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

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

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

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

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

Your homepage downloads 4.6 MB in 368 requests on a phone: scripts 2.1 MB (164), other files 1.2 MB (149) and images 819 KiB (28). Under 2 MB keeps phones on slow connections fast.

Untitled_2500_x_1500_px.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).

1 image (37 KiB) is 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.

1 image further down the page (22 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 1.30 g of CO₂e: 155.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

60 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

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

5 elements hidden from screen readers can still receive keyboard focus.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 298 pages on trollbeads.ca and 6 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.trollbeads.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.trollbeads.com/collections/christmas-gift-guide-2026, https://www.trollbeads.com/pages/advent-box, https://www.trollbeads.com/collections/i-wish-you and https://www.trollbeads.com/collections/peoples-uniques-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.trollbeads.com/collections/christmas-gift-guide-2026, https://www.trollbeads.com/pages/advent-box, https://www.trollbeads.com/collections/new-in, https://www.trollbeads.com/collections/i-wish-you and https://www.trollbeads.com/collections/peoples-uniques-2026 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.trollbeads.com/collections/christmas-gift-guide-2026 took over 3 s to send its HTML from our server.

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

4 images failed to load on a phone, for example https://www.trollbeads.com/?shpxid=f29a0dc1-4ebe-439a-82b5-8916c08d1b3b.

5 errors were logged to the browser console while the page loaded, for example “menu_override is not defined”.

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,172 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 20 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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.