1.6 sec in total
12 ms
1.1 sec
484 ms
Visit edge.ca now to see the best up-to-date Edge content for Canada and also check out these interesting facts you probably never knew about edge.ca
102.1 the Edge
Visit edge.caWe analyzed Edge.ca page load time and found that the first response time was 12 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
edge.ca performance score
name
value
score
weighting
Value2.7 s
62/100
10%
Value4.8 s
31/100
25%
Value12.7 s
3/100
10%
Value1,350 ms
17/100
30%
Value1.273
1/100
15%
Value19.1 s
3/100
10%
12 ms
26 ms
91 ms
9 ms
16 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 45% of them (30 requests) were addressed to the original Edge.ca, 5% (3 requests) were made to Dpm.demdex.net and 5% (3 requests) were made to Is5-ssl.mzstatic.com. The less responsive or slowest element that took the longest time to load (634 ms) belongs to the original domain Edge.ca.
Page size can be reduced by 115.0 kB (4%)
2.7 MB
2.6 MB
In fact, the total size of Edge.ca main page is 2.7 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. 70% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 98.9 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 98.9 kB or 78% of the original size.
Potential reduce by 10.1 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. Edge images are well optimized though.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 414 B
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. Edge.ca has all CSS files already compressed.
Number of requests can be reduced by 34 (57%)
60
26
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edge. 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 5 to 1 for CSS and as a result speed up the page load time.
edge.ca
12 ms
edge.ca
26 ms
183422-67482236234351.js
91 ms
style.min.css
9 ms
16 ms
jetpack.css
26 ms
50 ms
i18n.min.js
41 ms
i18n-loader.js
41 ms
48 ms
f7e98148-cb09-4cf1-9b9f-b5aee3465d6e-web.js
311 ms
beacon.js
62 ms
css
73 ms
main.css
52 ms
url.min.js
51 ms
jp-search.js
54 ms
w.js
58 ms
56 ms
script.js
56 ms
55 ms
outbrain.js
61 ms
e-202418.js
57 ms
rid
257 ms
analytics.js
300 ms
gpt.js
439 ms
edge.ca
549 ms
sdk.js
314 ms
g.gif
295 ms
id
197 ms
g.gif
171 ms
main-image_1140x657_edge.png
634 ms
hero_logo_380x170_edge.png
78 ms
edge-700x650-1.png
79 ms
nav-logo_210x70_edge.png
78 ms
edge_780x390_10K-Dog-Days-of-Spring_Rotator_v1.jpg
165 ms
Toronto_780x390_TorontoRockRadioRoundtable_v2.jpg
169 ms
Edge_780x390_Tucker-and-Maura-Showtime_v2.jpg
165 ms
Edge_780x390_EdgeInterviews_v2.jpg
153 ms
3-Quick-Question-.png
202 ms
insideedge_header_780x390.png
199 ms
blank.png
200 ms
ad-choices.png
201 ms
icons.ttf
191 ms
icons.ttf
192 ms
font
163 ms
CFNYFM_np.js
164 ms
CFNYFM_pl.js
164 ms
collect
37 ms
js
104 ms
sdk.js
52 ms
dest5.html
81 ms
s25113102444447
32 ms
600x600bb.jpg
376 ms
100x100bb.jpg
386 ms
100x100bb.jpg
398 ms
100x100bb.jpg
423 ms
100x100bb.jpg
463 ms
100x100bb.jpg
403 ms
ibs:dpid=411&dpuuid=ZjgiZAAAAJxNDwNz
125 ms
pubads_impl.js
40 ms
pixel
229 ms
pixel.gif
151 ms
container.html
27 ms
pixel
20 ms
ibs:dpid=771&dpuuid=CAESEKN4_84kXBiHX8ZY2Zn43Oo&google_cver=1
5 ms
chartbeat.js
24 ms
edge.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
edge.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
Missing source maps for large first-party JavaScript
edge.ca SEO score
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
EN
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edge.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 Edge.ca main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
edge.ca
Open Graph data is detected on the main page of Edge. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: