thefloatlife.ca website review

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

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

10 images could be 332 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.

About 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

7 third-party services load with your homepage (Shopify, Klaviyo and sezzle.com and others), adding 240 KiB and 220 ms of main-thread time.

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

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

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

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

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.

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

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

Visually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 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 6.6 MB in 244 requests on a phone: media 4.2 MB (1), other files 1.0 MB (161) and images 772 KiB (21). Under 2 MB keeps phones on slow connections fast.

XR_Collection_Onewheel.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).

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

1 image has no alt text, which hurts accessibility and image search.

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

Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 21 characters: “The Float Life Canada”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“The Float Life | Onewheel Parts, Accessories, & U…” and “The Float Life | Onewheel Parts, Accessories, & U…”). One clear main headline is easier for people and search engines.

The homepage links to 125 pages on thefloatlife.ca and 0 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://thefloatlife.ca/collections/onewheel%E2%84%A2-parts-accessories, https://thefloatlife.ca/pages/contact and https://thefloatlife.ca/collections/onewheel%E2%84%A2-tires have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://thefloatlife.ca/collections/onewheel%E2%84%A2-parts-accessories, whose canonical is https://thefloatlife.ca/collections/onewheel%e2%84%a2-parts-accessories. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://thefloatlife.ca/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

https://thefloatlife.ca/collections/onewheel%E2%84%A2-parts-accessories took over 3 s to send its HTML from our server.

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

1 error was 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.

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