2.3 sec in total
99 ms
2 sec
157 ms
Visit cansave.ca now to see the best up-to-date Can Save content and also check out these interesting facts you probably never knew about cansave.ca
CanSave is a locally owned company that supplies and distributes building materials, kitchens, and doors across Ontario and the Eastern provinces.
Visit cansave.caWe analyzed Cansave.ca page load time and found that the first response time was 99 ms and then it took 2.2 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.
cansave.ca performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value33.5 s
0/100
25%
Value15.5 s
0/100
10%
Value10,000 ms
0/100
30%
Value0.058
98/100
15%
Value19.9 s
2/100
10%
99 ms
88 ms
281 ms
43 ms
100 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 70% of them (76 requests) were addressed to the original Cansave.ca, 12% (13 requests) were made to Widget.freshworks.com and 9% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (742 ms) belongs to the original domain Cansave.ca.
Page size can be reduced by 197.1 kB (4%)
4.6 MB
4.4 MB
In fact, the total size of Cansave.ca main page is 4.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. 85% 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 4.1 MB which makes up the majority of the site volume.
Potential reduce by 178.3 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 178.3 kB or 84% of the original size.
Potential reduce by 22 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. Can Save images are well optimized though.
Potential reduce by 14.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 4.4 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. Cansave.ca has all CSS files already compressed.
Number of requests can be reduced by 81 (88%)
92
11
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Can Save. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
cansave.ca
99 ms
cansave.ca
88 ms
878936.js
281 ms
style.min.css
43 ms
styles.min.css
100 ms
jquery.qtip.min.css
94 ms
default-calendar-grid.min.css
93 ms
default-calendar-list.min.css
96 ms
style.min.css
95 ms
all.css
422 ms
um-fonticons-ii.css
55 ms
um-fonticons-fa.css
93 ms
select2.min.css
113 ms
um-crop.css
115 ms
um-modal.css
116 ms
um-styles.css
115 ms
um-profile.css
113 ms
um-account.css
113 ms
um-misc.css
212 ms
um-fileupload.css
210 ms
default.css
209 ms
default.date.css
210 ms
default.time.css
211 ms
um-raty.css
204 ms
simplebar.css
255 ms
um-tipsy.css
254 ms
um-responsive.css
256 ms
um-old-default.css
255 ms
um_old_settings.css
253 ms
style.css
255 ms
jquery.min.js
398 ms
jquery-migrate.min.js
397 ms
um-gdpr.min.js
394 ms
et-divi-customizer-global.min.css
395 ms
gallery.min.js
395 ms
scripts.min.js
401 ms
jquery.mobile.js
397 ms
jquery.qtip.min.js
401 ms
moment.min.js
397 ms
moment-timezone-with-data.min.js
384 ms
default-calendar.min.js
380 ms
common.js
558 ms
select2.full.min.js
522 ms
underscore.min.js
707 ms
wp-util.min.js
707 ms
um-crop.min.js
707 ms
um-modal.min.js
705 ms
um-jquery-form.min.js
707 ms
um-fileupload.js
683 ms
picker.js
690 ms
picker.date.js
690 ms
picker.time.js
686 ms
regenerator-runtime.min.js
692 ms
wp-polyfill.min.js
686 ms
hooks.min.js
594 ms
i18n.min.js
596 ms
um-raty.min.js
595 ms
um-tipsy.min.js
621 ms
imagesloaded.min.js
621 ms
masonry.min.js
573 ms
jquery.masonry.min.js
571 ms
simplebar.min.js
569 ms
um-functions.min.js
568 ms
um-responsive.min.js
741 ms
um-conditional.min.js
742 ms
um-scripts.min.js
740 ms
bootstrap.js
380 ms
tti.min.js
601 ms
um-profile.min.js
602 ms
um-account.min.js
604 ms
imagesloaded.pkgd.min.js
600 ms
CANSAVE-2011-Colour.png
415 ms
tccl.min.js
224 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
298 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
487 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff
489 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
587 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff
495 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
495 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff
586 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
494 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff
586 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
589 ms
modules.ttf
196 ms
33000000032.json
197 ms
analytics.js
446 ms
40-year-banner-1-for-web.png
397 ms
typar-header-1.jpg
393 ms
Lomanco-Header-1.jpg
103 ms
henry-image.png
395 ms
grace-iws-install.jpg
209 ms
frame.d7ae132c.css
43 ms
widget.js
202 ms
fa-brands-400.woff
465 ms
fa-solid-900.woff
631 ms
fa-regular-400.woff
468 ms
vendors~polyfill.1cd3d839d72b2aac0b8c.widget.js
26 ms
fetch.e830be6402aed1193c54.widget.js
24 ms
vendors~core-js.01ed1e490b25d6fde934.widget.js
121 ms
collect
133 ms
style.min.css
56 ms
0.1c2c4df3af1f24955f03.widget.js
43 ms
1.0e8f0237accf8416de7f.widget.js
41 ms
8.11bbb2fbc068c24e2209.widget.js
29 ms
10.94324fab217fc1ec04d6.widget.js
32 ms
16.7ec448c965bf78140550.widget.js
33 ms
style.min.css
69 ms
en.json
204 ms
cansave.ca accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
cansave.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cansave.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Cansave.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 Cansave.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.
cansave.ca
Open Graph data is detected on the main page of Can Save. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: