revrides.com website review

14 images could be 571 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google CDN, Klaviyo and Shopify and others), adding 1.6 MB and 590 ms of main-thread time.

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

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

Google CDN costs a phone 238 ms of main-thread work and 330 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.

convertcart.com costs a phone 66 ms of main-thread work and 829 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.

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

5 KiB could be saved by minifying JavaScript.

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.

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.

Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FIND IT FAST Select Type FIND NOW”.

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

For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

Your homepage downloads 3.6 MB in 275 requests on a phone: images 1.2 MB (44), scripts 1.1 MB (82) and other files 790 KiB (103). Under 2 MB keeps phones on slow connections fast.

ETM_RTR.png 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 2e488a18.webp at 493 px wide, shown at 89 px. Resized copies would save about 143 KiB.

3 images (136 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 1.03 g of CO₂e: 124.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 16 elements on the page fail this check, rated minor by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is 79 characters, so Google will cut it off around 60: “Electric Dirt Bikes, E-Scooters, Parts, Upgrades & More at REV Rides – REVRides”.

There are 2 <h1> headlines (“” and “Electric Dirt-Bikes, Pit-Bikes, e-Scooters & e-Bi…”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 436 pages on revrides.com and 17 external pages.

/collections/electric-pedal-assist-bicycles and /collections/kids-e-bikes have no meta description, so Google writes the search snippet from whatever text it finds.

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

3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://app.ardalio.com/submit/2131260' from origin 'https://revrides.com' has been blocked by CORS…”.

1 image is served at too low a resolution for sharp phone screens.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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