brightspherestore.shop website review

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

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

17 images could be 8.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 158 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 560 ms faster on a phone.

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

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

Clarity costs a phone 263 ms of main-thread work and 29 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 (Clarity, Facebook and Cloudflare and others), adding 554 KiB and 455 ms of main-thread time.

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

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

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

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.

Your largest element takes 41.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NEW SWAG DROP ! in stores now”.

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

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

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

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 21.5 MB in 250 requests on a phone: images 19.0 MB (31), other files 1.5 MB (101) and scripts 757 KiB (66). Under 2 MB keeps phones on slow connections fast.

10 images weigh 14.0 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example Youth_Mortals_Tee.png at 504 px wide, shown at 161 px. Resized copies would save about 1.1 MB.

19 images (15.4 MB) 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.

MrBxJL-Mobile-hero-banner-V2.png 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).

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

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

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

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

Headings skip levels (h2 → h5, h1 → h5 and h1 → h5), which makes the page harder to scan with a screen reader.

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

Your title is 104 characters, so Google will cut it off around 60: “brightspherestore.shop | The ONLY Official Merch Store for MrBeast in the world – brights…”.

There are 4 <h1> headlines (“”, “#pre_heading-slide_VQLemp { font-size: 80px; line…” and “#pre_heading-slide_AjKyUh { font-size: 20px; line…”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 133 pages on brightspherestore.shop and 12 external pages.

https://brightspherestore.shop/collections/bestsellers/adult has no <title>, so Google invents the link text in results.

https://brightspherestore.shop/collections/kids, https://brightspherestore.shop/policies/shipping-policy, https://brightspherestore.shop/collections/jacklinks-x-mrbeast, https://brightspherestore.shop/collections/bestsellers/kids, https://brightspherestore.shop/collections/bestsellers/adult and https://brightspherestore.shop/collections/adults and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://brightspherestore.shop/collections/all and https://brightspherestore.shop/collections/all/adult use the same meta description. A description written for each page earns more clicks.

https://brightspherestore.shop/collections/kids, https://brightspherestore.shop/collections/all, https://brightspherestore.shop/collections/new/kids, https://brightspherestore.shop/collections/typebeast, https://brightspherestore.shop/collections/jacklinks-x-mrbeast and https://brightspherestore.shop/collections/bestsellers/kids and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://brightspherestore.shop/products/mr-beast-digital-gift-card and https://brightspherestore.shop/collections/beast-football took over 3 s to send their HTML from our server.

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

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

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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

Before a visitor clicks anything, the page loads Amazon Ads, Meta Pixel, Microsoft Ads, Microsoft Clarity and Pinterest Tag 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 11 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.