designsforsport.com website review

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Hotjar, Facebook and rebuyengine.com and others), adding 1.5 MB and 1.7 s of main-thread time.

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

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

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

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

Hotjar costs a phone 392 ms of main-thread work and 65 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.

Facebook costs a phone 306 ms of main-thread work and 227 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.

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

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

About 76 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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.3 MB in 302 requests on a phone: images 2.0 MB (29), scripts 1.8 MB (95) and other files 873 KiB (117). Under 2 MB keeps phones on slow connections fast.

Whey-Protein-Launch-Banner-mobile.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).

3 images are downloaded at several times the size a phone draws them, for example dfs-neuromagsport_hero_2000_1.png at 2,000 px wide, shown at 382 px. Resized copies would save about 187 KiB.

3 images further down the page (390 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (245 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 1.51 g of CO₂e: 180.8 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.

10 images have no alt text, which hurts accessibility and image search.

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

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

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

15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 180 pages on designsforsport.com and 16 external pages.

https://designsforsport.com/collections/best-sellers and https://designsforsport.com/collections/bundles have no meta description, so Google writes the search snippet from whatever text it finds.

https://designsforsport.com/collections/all, https://designsforsport.com/collections/best-sellers, https://designsforsport.com/collections/retail, https://designsforsport.com/collections/bundles, https://designsforsport.com/pages/about-us and https://designsforsport.com/pages/pro-formance-peptides and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://designsforsport.com/collections/retail, https://designsforsport.com/collections/bundles, https://designsforsport.com/pages/pro-formance-peptides, https://designsforsport.com/pages/affiliate-program-refersion and https://designsforsport.com/pages/press-page took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

Social proof on the homepage: 2 trust badges. 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 carries about 451 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 19 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.