velosports.com website review

8 third-party services load with your homepage (cloudfront.net, Shopify and Clarity and others), adding 23.7 MB and 564 ms of main-thread time.

Shopify costs a phone 124 ms of main-thread work and 22.7 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.

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

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

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

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

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

cloudfront.net costs a phone 193 ms of main-thread work and 392 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.

Soundest costs a phone 0 ms of main-thread work and 352 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.

5 long tasks block the main thread while loading, the longest for 202 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).

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.

1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Player and coach, Matt Antonelli, posing with black Pro VEL…”.

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

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

The first text or image appears after 2.0 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 29.3 MB in 189 requests on a phone: media 27.0 MB (5), other files 946 KiB (82) and scripts 881 KiB (64). Under 2 MB keeps phones on slow connections fast.

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

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

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

Your title is only 11 characters: “Velo Sports”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 35 pages on velosports.com and 13 external pages.

https://velosports.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://velosports.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://velosports.com/blogs/the_pressbox_news_and_updates/blog-list-sep-23-20-25-56, https://velosports.com/customer_authentication/redirect, https://velosports.com/policies/refund-policy, https://velosports.com/policies/privacy-policy, https://velosports.com/policies/terms-of-service and https://velosports.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://velosports.com/products/velo-overspeed and https://velosports.com/products/velo-mvp-bundle use the same meta description. A description written for each page earns more clicks.

https://velosports.com/pages/increase-bat-speed, https://velosports.com/products/velo-overspeed, https://velosports.com/products/velo-overload-underload-fast-pitch, https://velosports.com/products/velo-puck, https://velosports.com/products/prgr-baseball-kit and https://velosports.com/products/velo-mvp-bundle and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://velosports.com/pages/increase-bat-speed and https://velosports.com/products/velo-overload-underload-fast-pitch have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage shows no opening hours. If customers visit or call, show when.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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 20 cookies, 1 of them by other companies (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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.