boyy.com website review

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

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

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

Your mobile performance score is 61 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

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

Shopify costs a phone 13 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.

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

Klaviyo costs a phone 112 ms of main-thread work and 322 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 images could be 189 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

Desktop scores 99 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Complimentary international shipping.”.

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

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

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

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

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

Your homepage downloads 9.1 MB in 237 requests on a phone: media 6.6 MB (1), scripts 960 KiB (77) and other files 856 KiB (124). 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.59 g of CO₂e: 310.5 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 253 pages on boyy.com and 3 external pages.

/pages/wishlist, /pages/boyy-stores, /pages/faqs, /collections/new-arrival-handbags, /collections/b-frame and /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 140 found) and read each the way a search engine does.

2 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=79966d9c4fe491951415a4531c78d725-1792293010693.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

boyy.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

The homepage has only about 75 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.

DMARC is set to p=none, so mail pretending to be boyy.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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