1.9 sec in total
41 ms
1.4 sec
432 ms
Welcome to 1800wheelchair.ca homepage info - get ready to check 1800 Wheelchair best content for Canada right away, or after learning these important things about 1800wheelchair.ca
Wheelchair Store Sale | Free shipping on all wheelchairs. Wheelchairs from $--. Electric Wheelchairs from $---. Mobility Scooters from $---. We'll match our competition's prices.
Visit 1800wheelchair.caWe analyzed 1800wheelchair.ca page load time and found that the first response time was 41 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
1800wheelchair.ca performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value14.2 s
0/100
25%
Value7.5 s
26/100
10%
Value1,710 ms
11/100
30%
Value0.546
13/100
15%
Value18.5 s
3/100
10%
41 ms
257 ms
97 ms
55 ms
28 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 85% of them (150 requests) were addressed to the original 1800wheelchair.ca, 5% (8 requests) were made to Static.klaviyo.com and 2% (4 requests) were made to Static-tracking.klaviyo.com. The less responsive or slowest element that took the longest time to load (417 ms) belongs to the original domain 1800wheelchair.ca.
Page size can be reduced by 466.1 kB (30%)
1.6 MB
1.1 MB
In fact, the total size of 1800wheelchair.ca main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 850.2 kB which makes up the majority of the site volume.
Potential reduce by 282.8 kB
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 282.8 kB or 77% of the original size.
Potential reduce by 0 B
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. 1800 Wheelchair images are well optimized though.
Potential reduce by 44.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 44.3 kB or 22% of the original size.
Potential reduce by 139.0 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. 1800wheelchair.ca needs all CSS files to be minified and compressed as it can save up to 139.0 kB or 97% of the original size.
Number of requests can be reduced by 146 (88%)
166
20
The browser has sent 166 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1800 Wheelchair. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 147 to 1 for JavaScripts and as a result speed up the page load time.
1800wheelchair.ca
41 ms
www.1800wheelchair.ca
257 ms
dcfc9e182f050f1633ddd0e87a254a51.css
97 ms
styles-l.css
55 ms
require.js
28 ms
mixins.js
24 ms
requirejs-config.js
35 ms
klaviyo.js
22 ms
bootstrap.min.css
78 ms
bootstrap.min.css
70 ms
desktop_banner_v2.png
69 ms
flag_usa.png
63 ms
flag_france.png
64 ms
jquery.js
62 ms
common.js
60 ms
dataPost.js
62 ms
bootstrap.js
63 ms
app.js
61 ms
form-key-provider.js
63 ms
mage-translation-dictionary.js
61 ms
theme.js
62 ms
latoregular.woff
66 ms
latobold.woff
66 ms
latoheavy.woff
66 ms
latoblack.woff
66 ms
DMSans-Regular.ttf
24 ms
DMSans-Medium.ttf
23 ms
DMSans-Bold.ttf
23 ms
domReady.js
59 ms
template.js
53 ms
confirm.js
48 ms
widget.js
50 ms
text.js
49 ms
main.js
49 ms
bootstrap.js
47 ms
smart-keyboard-handler.js
92 ms
mage.js
91 ms
ie-class-fixer.js
91 ms
collapsible.js
91 ms
accordion.js
90 ms
gtm.js
107 ms
loader.js
100 ms
jquery-mixin.js
64 ms
types.js
63 ms
layout.js
63 ms
matchMedia.js
56 ms
cookies.js
75 ms
iframeResizer.min.js
75 ms
weltpixel_ga4_persistentlayer.js
77 ms
weltpixel_ga4_gtm.js
73 ms
intersection-observer.js
78 ms
vanilla.lazyload.js
37 ms
fender_analytics.113876fdc67592e7cbfd.js
150 ms
static.047f24ade89e4aff54a9.js
150 ms
runtime.134dfcf3f5ea95d04d69.js
32 ms
sharedUtils.00081c57cddd29832b4e.js
71 ms
vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.b0930143925bb765e2d3.js
74 ms
vendors~signup_forms~onsite-triggering.733ed8744f200f7d4d54.js
73 ms
vendors~signup_forms.824396622be3ec2234ff.js
73 ms
default~signup_forms~onsite-triggering.968e4cc173bff13b788f.js
73 ms
signup_forms.3c339f68eee3e750afea.js
73 ms
vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.b0930143925bb765e2d3.js
171 ms
post_identification_sync.9785ea669391d6a8413c.js
171 ms
underscore.js
144 ms
translate.js
143 ms
modal.js
144 ms
knockout.js
142 ms
knockout-es5.js
141 ms
js-translation.json
139 ms
owl.carousel.min.js
160 ms
customer-data.js
160 ms
customer-data-mixin.js
183 ms
engine.js
158 ms
bootstrap.js
158 ms
observable_array.js
158 ms
bound-nodes.js
182 ms
version.js
297 ms
scripts.js
181 ms
tabs.js
296 ms
core.js
179 ms
storage-wrapper.js
295 ms
wrapper.js
290 ms
main.js
290 ms
registry.js
289 ms
call-tracking_9.js
115 ms
console-logger.js
417 ms
feathermanualgray_eb_worldslightestwheelchair_1200x1200.jpg
386 ms
feathertransport_worldslightestwheelchair_1200x1200_1.jpg
386 ms
featherscooter_worldslightestwheelchair_1200x1200_1.jpg
389 ms
featherpower_worldslightestwheelchair_1200x1200_1.jpg
387 ms
featherweighthouse_39.jpg
388 ms
js
102 ms
analytics.js
209 ms
destination
206 ms
bat.js
337 ms
fbevents.js
88 ms
jd42zakd81
337 ms
cookie-wrapper.js
324 ms
local.js
321 ms
wcm
287 ms
modal-popup.html
293 ms
modal-slide.html
294 ms
modal-custom.html
293 ms
key-codes.js
291 ms
z-index.js
288 ms
knockout-repeat.js
274 ms
knockout-fast-foreach.js
279 ms
section-config.js
279 ms
url.js
280 ms
storage.js
277 ms
renderer.js
277 ms
resizable.js
277 ms
i18n.js
278 ms
scope.js
280 ms
range.js
278 ms
mage-init.js
279 ms
keyboard.js
279 ms
optgroup.js
278 ms
after-render.js
274 ms
autoselect.js
272 ms
datepicker.js
272 ms
outer_click.js
272 ms
175535029887305
155 ms
fadeVisible.js
160 ms
collapsible.js
158 ms
staticChecked.js
159 ms
simple-checked.js
160 ms
bind-html.js
160 ms
tooltip.js
160 ms
collect
117 ms
color-picker.js
72 ms
observable_source.js
72 ms
events.js
72 ms
data.js
74 ms
disable-selection.js
70 ms
focusable.js
70 ms
form.js
72 ms
ie.js
73 ms
keycode.js
72 ms
labels.js
70 ms
jquery-patch.js
73 ms
plugin.js
69 ms
safe-active-element.js
69 ms
safe-blur.js
70 ms
scroll-parent.js
70 ms
tabbable.js
68 ms
unique-id.js
68 ms
tabs.js
68 ms
js.storage.js
68 ms
arrays.js
73 ms
compare.js
78 ms
misc.js
73 ms
objects.js
77 ms
strings.js
77 ms
template.js
77 ms
js.cookie.js
71 ms
clarity.js
35 ms
async.js
49 ms
tooltip.html
58 ms
collect
59 ms
logger.js
41 ms
entry-factory.js
49 ms
console-output-handler.js
35 ms
formatter.js
34 ms
message-pool.js
52 ms
levels-pool.js
57 ms
logger-utils.js
51 ms
loader.js
50 ms
spectrum.js
55 ms
tinycolor.js
67 ms
class.js
66 ms
jquery.cookie.js
60 ms
dom-observer.js
59 ms
bindings.js
48 ms
moment.js
42 ms
entry.js
34 ms
1800wheelchair.ca accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
1800wheelchair.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
1800wheelchair.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 1800wheelchair.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 1800wheelchair.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.
1800wheelchair.ca
Open Graph description is not detected on the main page of 1800 Wheelchair. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: