nepestsports.com website review

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Clarity and others), adding 1.1 MB and 607 ms of main-thread time.

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

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

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

Shopify costs a phone 262 ms of main-thread work and 759 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 91 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 240 ms faster on a phone.

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

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

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

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.

5 KiB could be saved by minifying CSS.

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 17.3 s. Good is under 3.8 s.

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

Real visitors wait 855 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Your largest element takes 3.1 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 292 ms in total while the page loads. Good is under 200 ms.

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

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

Your homepage downloads 10.3 MB in 222 requests on a phone: media 5.9 MB (1), images 2.3 MB (31) and scripts 1.2 MB (76). Under 2 MB keeps phones on slow connections fast.

banner_28be5703-94db-4427-ba36-77ffb38eb296.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).

4 images (132 KiB) are 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.93 g of CO₂e: 351.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 66 characters, so Google will cut it off around 60: “NEPEST | Premium Carbon Wheelsets for Road & Gravel Bikes – Nepest”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 70 pages on nepestsports.com and 15 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.nepestsports.com/en-us and https://www.nepestsports.com/fr-fr all use the title “NEPEST | Premium Carbon Wheelsets for Road & Gravel Bikes – Nepest”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.nepestsports.com/en-us/pages/contact-us, https://www.nepestsports.com/en-us/pages/behind-every-nepest-wheelset, https://www.nepestsports.com/blogs/uci-approval and https://www.nepestsports.com/fr-fr use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.nepestsports.com/blogs/uci-approval, whose canonical is https://www.nepestsports.com/en-us/blogs/uci-approval. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.nepestsports.com/en-us/collections/carbon-road-bike-wheels, https://www.nepestsports.com/en-us/collections/carbon-wheelset-accessories, https://www.nepestsports.com/en-us/pages/nepest-carbontrue, https://www.nepestsports.com/en-us/pages/behind-every-nepest-wheelset, https://www.nepestsports.com/en-us/pages/nepest-customer-reviews and https://www.nepestsports.com/blogs/uci-approval and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.nepestsports.com/en-us/pages/authorized-dealer, https://www.nepestsports.com/en-us/pages/behind-every-nepest-wheelset, https://www.nepestsports.com/en-us/pages/nepest-customer-reviews and https://www.nepestsports.com/blogs/uci-approval took over 3 s to send their HTML from our server.

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

5 of 18 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”.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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