1.1 sec in total
58 ms
1 sec
74 ms
Visit torstar.com now to see the best up-to-date TORSTAR content for Canada and also check out these interesting facts you probably never knew about torstar.com
Visit torstar.comWe analyzed Torstar.com page load time and found that the first response time was 58 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
torstar.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value5.6 s
17/100
25%
Value3.4 s
89/100
10%
Value250 ms
85/100
30%
Value0.262
47/100
15%
Value7.0 s
53/100
10%
58 ms
359 ms
35 ms
77 ms
97 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 63% of them (40 requests) were addressed to the original Torstar.com, 21% (13 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (359 ms) belongs to the original domain Torstar.com.
Page size can be reduced by 880.1 kB (68%)
1.3 MB
420.3 kB
In fact, the total size of Torstar.com main page is 1.3 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. 55% of websites need less resources to load. CSS take 712.1 kB which makes up the majority of the site volume.
Potential reduce by 45.1 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 45.1 kB or 80% of the original size.
Potential reduce by 16 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. TORSTAR images are well optimized though.
Potential reduce by 233.3 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 233.3 kB or 56% of the original size.
Potential reduce by 601.6 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. Torstar.com needs all CSS files to be minified and compressed as it can save up to 601.6 kB or 84% of the original size.
Number of requests can be reduced by 35 (80%)
44
9
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TORSTAR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
torstar.com
58 ms
torstar.com
359 ms
font-awesome-5.min.css
35 ms
font-awesome-v4-shims.css
77 ms
animate.min.css
97 ms
sppagebuilder.css
122 ms
js_slider.css
69 ms
content.min.css
58 ms
css
37 ms
css
53 ms
bootstrap.min.css
88 ms
joomla-fontawesome.min.css
104 ms
font-awesome-v4-shims.min.css
103 ms
template.css
109 ms
preset2.css
108 ms
custom.css
108 ms
pagebuilder.css
129 ms
frontend-edit.css
130 ms
addtoany.css
135 ms
core.min.js
134 ms
jquery.min.js
147 ms
jquery-noconflict.min.js
143 ms
finder.min.js
142 ms
common.js
156 ms
jquery.parallax.js
158 ms
sppagebuilder.js
169 ms
js_slider.js
176 ms
text_block.js
164 ms
bootstrap.min.js
168 ms
jquery.sticky.js
171 ms
main.js
178 ms
frontend-edit.js
183 ms
page.js
36 ms
js
61 ms
js
107 ms
fastfont.js
233 ms
torstar.jpg
62 ms
20grad.png
56 ms
slider-1.jpg
55 ms
slider-2.jpg
57 ms
slider-3.jpg
56 ms
analytics.js
141 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff
202 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff
239 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff
248 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrc.woff
250 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff
250 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff
249 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff
250 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrc.woff
248 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff
250 ms
sm.25.html
104 ms
eso.BRQnzO8v.js
169 ms
fa-solid-900.woff
92 ms
fa-solid-900.woff
146 ms
fa-regular-400.woff
91 ms
fa-regular-400.woff
90 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rl.woff
205 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rl.woff
206 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rl.woff
207 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rl.woff
207 ms
collect
68 ms
icons.38.svg.js
44 ms
torstar.com accessibility score
torstar.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
torstar.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 Torstar.com 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 Torstar.com 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.
torstar.com
Open Graph description is not detected on the main page of TORSTAR. 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: