Website review, no card needed
isinwheel.ca website review
Visit site (opens in a new tab)Reviewed 8 November 202647 issues · 91 checks
This review found 47 issues worth fixing on isinwheel.ca, 16 of them high impact, across 91 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78C- #59,953 of 118,676 reviewed websitesbeats 44%
- #39,371 of 67,389 online storesbeats 36%
- #37,643 of 61,444 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 121 ms |
| May 23, 2026 | 123 ms |
| May 30, 2026 | 124 ms |
| Jun 6, 2026 | 124 ms |
| Jun 13, 2026 | 123 ms |
| Jun 20, 2026 | 125 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 123 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 166 ms |
| Aug 29, 2026 | 197 ms |
| Sep 5, 2026 | 216 ms |
| Sep 12, 2026 | 228 ms |
| Sep 19, 2026 | 238 ms |
| Sep 26, 2026 | 238 ms |
| Oct 3, 2026 | 243 ms |
| Oct 10, 2026 | 244 ms |
| Oct 17, 2026 | 237 ms |
| Oct 24, 2026 | 237 ms |
| Oct 31, 2026 | 219 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
2.1 s
3.1 s
4.2 s
5.2 s
6.2 s
7.3 s
8.3 s
Speed
Improve image delivery
1.4 s · 1.0 MB18 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (x-future.com, route.com and Clarity and others), adding 1.8 MB and 805 ms of main-thread time.
Reduce unused JavaScript
756 KiBAbout 756 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
575 KiB11 files are served with short cache lifetimes, so returning visitors download them again (575 KiB).
Reduce unused CSS
300 ms · 133 KiBAbout 133 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.
x-future.com adds 286 ms
286 msx-future.com costs a phone 286 ms of main-thread work and 497 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.
2,562 HTML elements
The page has 2,562 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
route.com adds 173 ms
173 msroute.com costs a phone 173 ms of main-thread work and 542 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.
Shopify adds 25 ms
25 msShopify costs a phone 25 ms of main-thread work and 364 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 196 ms. During a long task the page ignores taps.
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Time to Interactive: 18.7 s
18.7 sThe page becomes fully interactive after 18.7 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
Real-user INP: 235 ms
235 msReal visitors wait 235 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 87% slower for real visitors
+87%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 121 ms to 219 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 511 ms
511 msReal visitors wait 511 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 104 ms
104 msScripts block the page for only 104 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 6.2 MB in 442 requests
6.2 MBYour homepage downloads 6.2 MB in 442 requests on a phone: images 2.7 MB (57), scripts 1.6 MB (80) and other files 1.5 MB (273). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
125 KiB1 image is downloaded at several times the size a phone draws it, for example CA-M.png at 1,500 px wide, shown at 390 px. Resized copies would save about 125 KiB.
About 1.8 g of CO₂ per visit
1.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.75 g of CO₂e: 210.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
78 internal links, 10 external
The homepage links to 78 pages on isinwheel.ca and 10 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “isinwheel electric scooter offer a versatile range of high-quality, eco-friendly scooters, travel with our e scooter, e…”.
One H1 headline
Your main headline reads: “iSinwheel iSinwheel”.
Title: 40 characters
Your title is a healthy 40 characters: “Electric Scooter Brand Store – iSinwheel”.
Canonical URL set
The canonical URL is https://www.isinwheel.ca/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.isinwheel.ca/sitemap.xml.
AI search readiness
No Organization structured data
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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
llms.txt published
The site publishes https://www.isinwheel.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.isinwheel.ca/pages/faq has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.isinwheel.ca/collections/isinwheel-sale, https://www.isinwheel.ca/pages/contact and https://www.isinwheel.ca/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
5 checks passed
Linked pages load
3 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 3 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.isinwheel.ca/.
6 small tap targets
6 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Only about 127 words
The homepage has only about 127 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
5 checks passed
17 calls to action
The homepage has 17 calls to action, for example “Contact Us”, “Order note” and “Apply”.
23 short forms
23 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 197 testimonial or review blocks, a star rating and “1.8M+ Active Riders”.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
31 other companies contacted
Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at isinwheel.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Foxify Page Builder · Frequently Bought · Microsoft Clarity · Hulk Form Builder · Judge Me Reviews · Cartsee Email Marketing Sms · Eg Auto Add To Cart · X Future Chatbot · route.com · cloudfront.net · b-cdn.net · nice-team.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on isinwheel.ca, including 20 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.