mokwheel.ca website review

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

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

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

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

8 third-party services load with your homepage (Facebook, Klaviyo and Trust Pilot and others), adding 1.7 MB and 1.3 s of main-thread time.

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

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

6 images could be 102 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

Trust Pilot costs a phone 205 ms of main-thread work and 340 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 63 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 37 KiB JavaScript that modern phones do not need.

31 KiB could be saved by minifying JavaScript.

11 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

11 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' tap response (inp) went from 146 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.8 MB in 364 requests on a phone: scripts 2.3 MB (122), other files 726 KiB (155) and images 473 KiB (43). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 1087_3x_710eb7c5-dea7-4293-ab86-06ced9ce7f76.webp at 389 px wide, shown at 127 px. Resized copies would save about 2 KiB.

1 image (61 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.09 g of CO₂e: 130.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

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

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

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

19 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 267 pages on mokwheel.ca and 52 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.mokwheel.com/products/basalt-st-2-0-s, https://www.mokwheel.com/products/onyx, https://www.mokwheel.com/products/tarmac, https://www.mokwheel.com/products/flint-st, https://www.mokwheel.com/products/slate and https://www.mokwheel.com/products/granite have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mokwheel.com/pages/deals, https://www.mokwheel.com/pages/contact-us, https://www.mokwheel.com/products/basalt-st-2-0-s and https://www.mokwheel.com/products/onyx took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://cdn.klaviyomail.com/company/TqjpEv/images/d08842ba-747f-409e-8a52-517c4acb8912.png.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: e is not a function”.

Requests the notification permission on page load.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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 2,130 words of visible text.

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