boyy-up.com website review

8 third-party services load with your homepage (Facebook, Klaviyo and Adroll and others), adding 7.2 MB and 473 ms of main-thread time.

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

Shopify costs a phone 44 ms of main-thread work and 6.6 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 222 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 430 ms faster on a phone.

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

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

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

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

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

4 images could be 122 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 99 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.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.9 MB in 205 requests on a phone: media 6.6 MB (1), scripts 920 KiB (73) and other files 763 KiB (102). Under 2 MB keeps phones on slow connections fast.

BOYY_-_Web_banner_Mobile_FISH_0000_Untitled-4_0000_BOYY_CONT 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 2.54 g of CO₂e: 304.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

The homepage links to 261 pages on boyy-up.com and 3 external pages.

https://www.boyy.com/pages/wishlist, https://www.boyy.com/pages/boyy-stores, https://www.boyy.com/pages/faqs, https://www.boyy.com/collections/new-arrival-handbags, https://www.boyy.com/collections/b-frame and https://www.boyy.com/collections/benji and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

3 images failed to load on a phone, for example https://d.adroll.com/uev/WCYMJKA27NAOXPLD2A4CIT/X4IIK66UY5E5PJZZNGA22N/?adroll_tpc=lx3%3Dlex-875dcf7e-8824-4efd-8dd5-36b3b8e5e127&af0=0fe6f973&adroll_fpc=55be8e84d331fd18d4a92a321c5f290e-1794402191214.

9 of 20 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 “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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 77 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, Klaviyo and Meta Pixel and 2 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 16 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.