wheelsmfg.com website review

The page goes through 1 redirect before it starts loading, costing about 11.1 s. Link and advertise the final URL directly.

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Key CDN and userway.org and others), adding 1.2 MB and 503 ms of main-thread time.

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

Klaviyo costs a phone 204 ms of main-thread work and 416 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 86 ms. During a long task the page ignores taps.

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

2 images could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 11 KiB of CSS is downloaded but never applied on this page.

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.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 107 ms to 144 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.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 345 requests on a phone: scripts 1.2 MB (143), images 1.0 MB (80) and HTML 521 KiB (3). Under 2 MB keeps phones on slow connections fast.

Hootin-Hauler-Main-Small.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).

2 images are downloaded at several times the size a phone draws them, for example catalog-ng.svg at 1,440 px wide, shown at 390 px. Resized copies would save about 60 KiB.

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

ARIA attributes must conform to valid values: 8 elements on the page fail this check, rated critical by axe-core.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is 67 characters, so Google will cut it off around 60: “Wheels Manufacturing | Bicycle Derailleur hangers | Bottom Brackets”.

Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:Liquid error (snippets/json-structured-data line …”.

The homepage links to 207 pages on wheelsmfg.com and 13 external pages.

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

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

https://wheelsmfg.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://wheelsmfg.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

12 images are served at too low a resolution for sharp phone screens.

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.

Social proof on the homepage: 13 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Klaviyo (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 6 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.