bdraddy.com website review

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

8 third-party services load with your homepage (Clarity, Klaviyo and rebuyengine.com and others), adding 1.7 MB and 790 ms of main-thread time.

About 864 KiB of JavaScript is downloaded but never used on this page.

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

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

Klaviyo costs a phone 162 ms of main-thread work and 534 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 1,764 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

rebuyengine.com costs a phone 116 ms of main-thread work and 332 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.

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

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

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

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

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

27 KiB could be saved by minifying JavaScript.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “HUNTER HEATHER”.

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

The layout shifts by 0.284 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your homepage downloads 9.2 MB in 460 requests on a phone: media 4.7 MB (1), scripts 2.1 MB (145) and other files 1.0 MB (191). Under 2 MB keeps phones on slow connections fast.

1 image (191 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.

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

71 elements use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

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

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

All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 309 pages on bdraddy.com and 5 external pages.

/collections/all-best-sellers and /collections/all-best-sellers-2025 all use the title “Best Sellers | Polos, Hoodies & Boxers | B. Draddy – B.Draddy”. Search engines can't tell which page to show for a search, so each competes with the others.

/policies/shipping-policy and /pages/holiday-homepage have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all-best-sellers and /collections/all-best-sellers-2025 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /collections/all-best-sellers-2025, whose canonical is /collections/all-best-sellers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/collections/all-best-sellers, /collections/shop-all-mens, /collections/holiday-gift-shop, /products/andy-quilted-hoodie, /products/richard-boxer and /products/siobhan-sweatshirt-1 and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355015144&Ver=2&mid=754cae37-8ed8-47b7-b955-5ecd091b563a&bo=1&sid=4d8f0c40d9c611f18e54b96ba45cf9a7&vid=4d8f0450d9c611f18bdfd32a88735b29&vids=1&msclkid=N&pi=918639831&l.

38 of 80 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were 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.

1 link go through two or more redirects, for example https://bdraddy.com/account.

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.

bdraddy.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

bdraddy.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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