1.3 sec in total
73 ms
951 ms
309 ms
Welcome to history.ca homepage info - get ready to check HISTORY best content for Canada right away, or after learning these important things about history.ca
HISTORY Canada - access show times and episode guides; watch Vikings and Forged in Fire online for free in Canada.
Visit history.caWe analyzed History.ca page load time and found that the first response time was 73 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
history.ca performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value13.0 s
0/100
25%
Value10.7 s
7/100
10%
Value2,020 ms
8/100
30%
Value0.059
98/100
15%
Value20.1 s
2/100
10%
73 ms
314 ms
50 ms
45 ms
75 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 39% of them (24 requests) were addressed to the original History.ca, 16% (10 requests) were made to Fonts.smdg.ca and 16% (10 requests) were made to Media.history.ca. The less responsive or slowest element that took the longest time to load (314 ms) belongs to the original domain History.ca.
Page size can be reduced by 569.9 kB (32%)
1.8 MB
1.2 MB
In fact, the total size of History.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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 32.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. This page needs HTML code to be minified as it can gain 7.4 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 32.8 kB or 81% of the original size.
Potential reduce by 39.2 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. HISTORY images are well optimized though.
Potential reduce by 422.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 422.2 kB or 73% of the original size.
Potential reduce by 75.7 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. History.ca needs all CSS files to be minified and compressed as it can save up to 75.7 kB or 78% of the original size.
Number of requests can be reduced by 22 (47%)
47
25
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HISTORY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
history.ca
73 ms
www.history.ca
314 ms
mvh6eev.js
50 ms
global.css
45 ms
button.css
75 ms
featureditems.css
99 ms
heroimage.css
76 ms
titleandtext.css
74 ms
todayinhistory.css
84 ms
provider-picker-bundle.css
98 ms
jquery.min.js
57 ms
176 ms
shawUH.min.js
22 ms
stylesheet.css
262 ms
shawUH.responsive.min.css
21 ms
todayinhistory.js
260 ms
114 ms
page.js
114 ms
provider-picker-bundle.js
268 ms
auth-lockedvideos.js
137 ms
mvh6eev-k.css
20 ms
gpt.js
73 ms
forged-in-fire-hero-2.jpg
143 ms
history_channelbuttonnew.jpg
137 ms
vikings-300x600.jpg
139 ms
american-restoration-new-cast-320-180.jpg
137 ms
pawn-stars-footer.jpg
139 ms
americanpickers-footer.jpg
136 ms
historica-canada.png
100 ms
ShawConnectLogo_127x33.png
37 ms
header-sheer-featurenav.jpg
106 ms
header-sheer-ad.jpg
73 ms
header-sheer-mainnav.jpg
72 ms
sprite.png
229 ms
hero-fade-left.png
69 ms
hero-fade-right.png
74 ms
stripes.png
103 ms
icon-arrow-n.svg
31 ms
p.gif
72 ms
on_this_day
236 ms
pubads_impl_81.js
45 ms
analytics.js
65 ms
UIYMwGx0LuWrDD3emvxaFPrUhyg43RStBk7HR2IeLLCffHPsgsMWeMJ6Mk6f5Mb.woff
30 ms
9MY4rQst_yoewQrO5EaaLiOcO1gbP2x0Qd522fn64tvffH-sgsMWeMJ6Mk6f5Mj.woff
152 ms
gPj0djVu1JBjQJslz39e6n4fQZxyz6--jy1-K-qqan6ff4kQgsMWeMJ6Mk6f5MS.woff
150 ms
sn3Ar76jjmEEwd616xGCGtorLY3PVyPpuJTqw5xhmpSffH7sgsMWeMJ6Mk6f5M6.woff
188 ms
xdTJgGPceUw_jFpWRob1HPV55RdyT8Hr5R78KovHzbCffHAsgsMWeMJ6Mk6f5Mt.woff
188 ms
E0hxi_3hn3_v25wAnBK7VXzXJf3GrqgFJAqINWBglwJffHpsgsMWeMJ6Mk6f5gM.woff
189 ms
GqUjmkyqKQcm0icQyT-IsnhRG4KRG7qtlyh3R_PVrjIffHcsgsMWeMJ6Mk6f5gI.woff
189 ms
RsHQf0iNJKynQPdU_pevh0XUPFUJNIAfWNJu8aI2uCjffH0sgsMWeMJ6Mk6f5gJ.woff
185 ms
History-Regular.woff
149 ms
fontawesome-webfont.woff
152 ms
History-Light.woff
28 ms
shaw_medium-webfont.woff
27 ms
shaw.bold-webfont.woff
149 ms
show_companion_ad.js
164 ms
container.html
127 ms
collect
81 ms
american-restoration-600-335-update.jpg
26 ms
billion%20dollar%20102.png
34 ms
firstevent
20 ms
r2
4 ms
history.ca accessibility score
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
history.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
history.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise History.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 History.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.
history.ca
Open Graph data is detected on the main page of HISTORY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: