3.5 sec in total
206 ms
2.8 sec
404 ms
Click here to check amazing Ezedia content. Otherwise, check out these important facts you probably never knew about ezedia.ca
(description)
Visit ezedia.caWe analyzed Ezedia.ca page load time and found that the first response time was 206 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ezedia.ca performance score
206 ms
155 ms
196 ms
26 ms
145 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 17% of them (12 requests) were addressed to the original Ezedia.ca, 34% (24 requests) were made to Maps.googleapis.com and 13% (9 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (516 ms) relates to the external source Google.com.
Page size can be reduced by 943.5 kB (53%)
1.8 MB
852.0 kB
In fact, the total size of Ezedia.ca main page is 1.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. 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. Javascripts take 891.0 kB which makes up the majority of the site volume.
Potential reduce by 10.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 10.3 kB or 67% of the original size.
Potential reduce by 13.9 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. Ezedia images are well optimized though.
Potential reduce by 595.2 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 595.2 kB or 67% of the original size.
Potential reduce by 324.1 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. Ezedia.ca needs all CSS files to be minified and compressed as it can save up to 324.1 kB or 84% of the original size.
Number of requests can be reduced by 30 (48%)
62
32
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezedia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.ezedia.ca
206 ms
wp-emoji-release.min.js
155 ms
style.css
196 ms
css
26 ms
font-awesome.css
145 ms
jquery.js
245 ms
jquery-migrate.min.js
139 ms
bootstrap.js
107 ms
theme.js
180 ms
wp-embed.min.js
210 ms
embed
516 ms
header01.jpg
164 ms
itmanagedservice-300x155.jpg
162 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
128 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
127 ms
fontawesome-webfont.woff
159 ms
Z9HCqD_GA8Y
74 ms
www-embed-player-vflfNyN_r.css
22 ms
www-embed-player.js
45 ms
base.js
71 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
32 ms
ad_status.js
72 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
68 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
69 ms
rs=ABjfnFVPZ9uu9aRwwgB8w1equuqUkK5Raw
33 ms
css
77 ms
js
97 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
59 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
2 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
33 ms
common.js
28 ms
map.js
57 ms
overlay.js
130 ms
1493-wht-blank_maps-4x.png&filter=ff009D57&scale=1.0
173 ms
util.js
124 ms
marker.js
118 ms
geocoder.js
118 ms
controls.js
118 ms
places_impl.js
166 ms
1493-wht-blank_maps-4x.png&filter=ffDB4436&scale=1.0
166 ms
selection_2x-000.png
9 ms
gen204
108 ms
onion.js
102 ms
openhand_8_8.cur
124 ms
ViewportInfoService.GetViewportInfo
93 ms
stats.js
74 ms
StaticMapService.GetMapImage
284 ms
transparent.png
41 ms
mapcnt6.png
22 ms
tmapctrl4.png
29 ms
vt
14 ms
vt
18 ms
vt
24 ms
vt
23 ms
vt
23 ms
vt
26 ms
vt
29 ms
vt
48 ms
vt
42 ms
vt
43 ms
viewer-icons001.png
92 ms
star4.png
92 ms
gen204
86 ms
AuthenticationService.Authenticate
36 ms
MyMaps_Icons003.png
20 ms
mymaps_32.png
24 ms
v1_4593b7d7.png
27 ms
google-my-maps-logo-small-001.png
26 ms
kh
65 ms
ezedia.ca SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezedia.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 Ezedia.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.
ezedia.ca
Open Graph data is detected on the main page of Ezedia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: