2.5 sec in total
604 ms
1.9 sec
54 ms
Visit ezwheel.ca now to see the best up-to-date Ezwheel content for Canada and also check out these interesting facts you probably never knew about ezwheel.ca
Welcome to EZWheel, we are a trusted brand in Electric Scooters, Electric Bikes and Hoverboards in Montreal, Quebec Canada.
Visit ezwheel.caWe analyzed Ezwheel.ca page load time and found that the first response time was 604 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ezwheel.ca performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value6.9 s
6/100
25%
Value11.4 s
5/100
10%
Value5,060 ms
0/100
30%
Value0.009
100/100
15%
Value25.1 s
0/100
10%
604 ms
45 ms
44 ms
319 ms
52 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ezwheel.ca, 59% (51 requests) were made to Static.wixstatic.com and 23% (20 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (815 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 1.6 MB (56%)
2.8 MB
1.2 MB
In fact, the total size of Ezwheel.ca main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. HTML takes 1.7 MB which makes up the majority of the site volume.
Potential reduce by 1.4 MB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.4 MB or 84% of the original size.
Potential reduce by 95.8 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Ezwheel needs image optimization as it can save up to 95.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 59.3 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 59.3 kB or 22% of the original size.
Number of requests can be reduced by 10 (15%)
66
56
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezwheel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.ezwheel.ca
604 ms
minified.js
45 ms
focus-within-polyfill.js
44 ms
polyfill.min.js
319 ms
thunderbolt-commons.1e70fbb2.bundle.min.js
52 ms
main.42e492e1.bundle.min.js
52 ms
lodash.min.js
51 ms
react.production.min.js
50 ms
react-dom.production.min.js
54 ms
siteTags.bundle.min.js
54 ms
wix-perf-measure.umd.min.js
54 ms
EZwheel_logo3.png
217 ms
2bb0ce_9a754702f1f14627a19f2e853fc7cc07f000.jpg
278 ms
dualtron_canada.png
217 ms
EZwheel_logo3.png
218 ms
Logo-Kaabo-transparent-1.png
217 ms
0452b7c8a80cc0c776ffd1c482090e36_w2000_h500.png
405 ms
VSETT-font.png
216 ms
Inmotion%20logo.png
275 ms
2bb0ce_197c7f0766d5431589651bd4a046862e~mv2.png
378 ms
2bb0ce_fe719f188e4f41ff98a827284b406448~mv2.png
325 ms
2bb0ce_9afaf260da67427498eec19b1b9cba4c~mv2.jpg
324 ms
2bb0ce_ca54eee4bab741579c203f4303e48f12~mv2.jpg
367 ms
2bb0ce_2823932e6ab34ad5a3e6ceffb709d4eb~mv2.jpg
432 ms
2bb0ce_edab5c682b6b4c56a83242081cceec5d~mv2.jpeg
435 ms
2bb0ce_ed38b2983cd24d9f95b10f7e3e107868~mv2.png
441 ms
2bb0ce_7378fb8b8b4f4503b790220330846c81~mv2.jpg
542 ms
2bb0ce_8a4bf816075b46aa9cb1a71be57eb928~mv2.jpg
512 ms
2bb0ce_38ab20a3ecc94f6786e20ace99bbe47f~mv2.jpg
520 ms
2bb0ce_ec5ebe3e2e654c25bfbeff3e7cb2f3f1~mv2.webp
435 ms
2bb0ce_de0b3f779c314f058e5597bbf4d1f880~mv2.webp
436 ms
2bb0ce_a64b481e526d4427a6be6df7d79a9306~mv2.webp
437 ms
2bb0ce_b7c4b3904cdd4fc5b9685bdf82308ecd~mv2.webp
437 ms
2bb0ce_e31c63a45ee04fa2955e5a82e7174070~mv2.png
440 ms
2bb0ce_77d43a1ff636423a84af7f94a2c62345~mv2.png
607 ms
2bb0ce_eb5c248066904366a27055ef5a79c5da~mv2.jpg
606 ms
2bb0ce_e6398fa1931c4b25b44b257425720ed5~mv2.jpeg
557 ms
2bb0ce_52dd17ac211844a58745b05dcbeda08b~mv2.webp
513 ms
2bb0ce_e679212d78e7461789ad6e2ff6aa512b~mv2.jpg
710 ms
2bb0ce_22ba978a49ba43e18cf37ff119fdc5b8~mv2.jpg
656 ms
2bb0ce_96b2ecc2e3ff40719c83c1f39a918972~mv2.png
718 ms
2bb0ce_4d42406e655d447fa7a30ad728a6961b~mv2.png
648 ms
2bb0ce_515a694970b54fb5af44839d3af8f9be~mv2.jpg
747 ms
2bb0ce_e7eeb64671b54c3d8b23f566315a8aad~mv2.png
744 ms
2bb0ce_44c3393fd831423ba20734e6626f5a56~mv2.jpg
815 ms
2bb0ce_6e76d7fda97d468c80e968b2f4293b24~mv2.jpg
659 ms
2bb0ce_a4af323931e14d178685bbb2945dab09~mv2.jpg
662 ms
bundle.min.js
135 ms
2bb0ce_ebc60a1f48374af6bc08f1541afdaa8b~mv2.png
457 ms
2bb0ce_07a3e2a5c4d7405bb3d91550e2aca4ec~mv2.png
462 ms
2bb0ce_aa26c370ee1f43499e5e29edc87cc9d9~mv2.png
468 ms
2bb0ce_3fb240f6052d4701975f46578dc883e2~mv2.png
471 ms
2bb0ce_9e6a33f3053b4fec8a3f3082211755d7~mv2.png
420 ms
2bb0ce_1dd706e8f9474473a6e6e1c0ef3fa479~mv2.png
422 ms
50ac1699-f3d2-47b6-878f-67a368a17c41.woff
45 ms
80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff
45 ms
LuloCleanW05-OneBold.woff
44 ms
ca003289-5ee3-45c2-94ad-36c743c35fc1.woff
48 ms
49631ce8-9201-47a8-8874-45371417c35f.woff
46 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
45 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
46 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
46 ms
2bb0ce_0985fc84758640c4976dc7ee5ca2ad8b~mv2.jpg
423 ms
142 ms
128 ms
131 ms
135 ms
125 ms
121 ms
165 ms
161 ms
161 ms
164 ms
164 ms
168 ms
brand-visa%403x.png
377 ms
brand-mastercard%403x.png
338 ms
brand-amex%403x.png
334 ms
brand-chinaunionpay%403x.png
330 ms
brand-jcb%403x.png
305 ms
brand-diners%403x.png
280 ms
brand-discover%403x.png
280 ms
brand-paypal%403x.png
279 ms
deprecation-en.v5.html
8 ms
bolt-performance
19 ms
deprecation-style.v5.css
8 ms
right-arrow.svg
7 ms
ezwheel.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ezwheel.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ezwheel.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezwheel.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ezwheel.ca main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
ezwheel.ca
Open Graph data is detected on the main page of Ezwheel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: