4.7 sec in total
237 ms
4.1 sec
441 ms
Visit echo.ca now to see the best up-to-date ECHO content for Canada and also check out these interesting facts you probably never knew about echo.ca
BEST-IN-CLASS PROFESSIONAL POWER. Tackle the toughest jobs with ECHO’s best-in-class, commercial-grade outdoor power equipment. Find out more today.
Visit echo.caWe analyzed Echo.ca page load time and found that the first response time was 237 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
echo.ca performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value19.1 s
0/100
25%
Value5.6 s
52/100
10%
Value430 ms
64/100
30%
Value0.356
31/100
15%
Value12.3 s
15/100
10%
237 ms
257 ms
254 ms
174 ms
266 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 46% of them (32 requests) were addressed to the original Echo.ca, 29% (20 requests) were made to Static.xx.fbcdn.net and 13% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Echo.ca.
Page size can be reduced by 144.0 kB (16%)
913.3 kB
769.2 kB
In fact, the total size of Echo.ca main page is 913.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 757.3 kB which makes up the majority of the site volume.
Potential reduce by 23.7 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 23.7 kB or 72% of the original size.
Potential reduce by 60.5 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. ECHO images are well optimized though.
Potential reduce by 49.6 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 49.6 kB or 45% of the original size.
Potential reduce by 10.2 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. Echo.ca needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 82% of the original size.
Number of requests can be reduced by 37 (54%)
68
31
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECHO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
echo.ca
237 ms
Home
257 ms
GetResource.ashx
254 ms
jquery.min.js
174 ms
jquery.fancybox-1.3.4.pack.js
266 ms
BrightcoveExperiences.js
119 ms
jquery.fancybox-1.3.4.css
166 ms
jquery.jcarousel.js
165 ms
GetResource.ashx
238 ms
WebResource.axd
179 ms
ScriptResource.axd
858 ms
ScriptResource.axd
603 ms
jquery.anythingslider.css
583 ms
jquery.anythingslider.js
1248 ms
GetCSS.aspx
87 ms
ga.js
200 ms
background_getserious.jpg
277 ms
canadabanner.jpg
881 ms
content_bg4.jpg
2521 ms
echocaspring.jpg
398 ms
instagram.jpg
732 ms
followus.jpg
480 ms
EBC_Info-Banner.jpg
584 ms
txt_GetSerious.gif
618 ms
logo_Signature_Elite.jpg
652 ms
__utm.gif
68 ms
sprite.png
157 ms
round_invert.jpg
122 ms
background_btn
170 ms
Categories_v2.jpg
1225 ms
Home_Back.jpg
367 ms
Left_Col_Top_GetSerious.png
106 ms
pdficon_small.gif
387 ms
upgrade_flash_player2.gif
77 ms
scroll_back.jpg
70 ms
scroll_nav.png
95 ms
cellshade.png
123 ms
likebox.php
244 ms
activityi;src=3500025;type=gener107;cat=homep882;ord=1;num=4470694460906.088
85 ms
mf3o
94 ms
4zvF1Y0eZKv.css
187 ms
FrSU6IlfEX1.css
252 ms
GZeiuqs6M9H.css
305 ms
SRSW8M763HA.js
495 ms
ullQFyhrQFI.js
784 ms
y97Ig99UVTs.js
361 ms
KHAtULXOQuz.js
356 ms
XlY_wsDnClE.js
412 ms
rR4Qw0p7TFQ.js
549 ms
ULtnh-HfQSw.js
477 ms
d_-F4IIjJo3.js
427 ms
FOagnU9QnXq.js
536 ms
Cw6QosZRsiU.js
886 ms
i8XO-4kv8i7.js
898 ms
z5eMxBRE-Ji.js
1028 ms
7YklgZdHLYS.js
587 ms
156253_10153443735274151_683986452226803959_n.jpg
248 ms
10603531_10153485903229151_2930166063865041363_n.jpg
287 ms
1472064_10205648381506513_4901933133157966752_n.jpg
343 ms
1528587_688837977814377_504573297_n.jpg
432 ms
12654500_1114249311919734_4047521810810402815_n.jpg
709 ms
960298_423698561129725_4579902867415705833_n.jpg
711 ms
12247126_10153307499248196_3525220614154247690_n.jpg
713 ms
1479454_1376522665934378_285942623_n.jpg
711 ms
320814_269624223061591_129317329_n.jpg
432 ms
wL6VQj7Ab77.png
124 ms
1JLnMyDN79z.png
127 ms
FASTu8Ostla.png
46 ms
VXcANLwwL5J.js
61 ms
roundtrip.js
110 ms
echo.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
echo.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
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
echo.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Echo.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Echo.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.
echo.ca
Open Graph description is not detected on the main page of ECHO. 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: