3.4 sec in total
224 ms
3 sec
174 ms
Welcome to torontoglobe.com homepage info - get ready to check Torontoglobe best content right away, or after learning these important things about torontoglobe.com
Visit torontoglobe.comWe analyzed Torontoglobe.com page load time and found that the first response time was 224 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
torontoglobe.com performance score
224 ms
60 ms
352 ms
348 ms
217 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 28% of them (17 requests) were addressed to the original Torontoglobe.com, 46% (28 requests) were made to Static.xx.fbcdn.net and 16% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (825 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 114.5 kB (42%)
272.2 kB
157.7 kB
In fact, the total size of Torontoglobe.com main page is 272.2 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. 40% of websites need less resources to load. Javascripts take 150.1 kB which makes up the majority of the site volume.
Potential reduce by 11.0 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 1.7 kB, which is 11% 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 11.0 kB or 74% of the original size.
Potential reduce by 2.3 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. Torontoglobe images are well optimized though.
Potential reduce by 101.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 101.2 kB or 67% of the original size.
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 Torontoglobe. 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 12 to 1 for CSS and as a result speed up the page load time.
torontoglobe.com
224 ms
platform.js
60 ms
wp-emoji-release.min.js
352 ms
dashicons.min.css
348 ms
thickbox.css
217 ms
plugin.css
216 ms
nivo-slider.css
236 ms
default.css
246 ms
style.css
614 ms
jquery.js
670 ms
jquery-migrate.min.js
456 ms
jquery.ticker.js
489 ms
js.js
576 ms
thickbox.js
544 ms
jquery.nivo.slider.pack.js
709 ms
sprite.png
194 ms
icon-sprite.png
178 ms
loadingAnimation.gif
179 ms
likebox.php
338 ms
UThj8VI7Xhd.css
287 ms
FL1kvZ1wVUz.css
359 ms
7HwxA8gVs6-.css
429 ms
XDFRGGOuyy0.css
489 ms
cuTBFFsHWNo.css
574 ms
ljoX-PyMzJF.css
562 ms
q68gy-v_YMF.js
622 ms
FJmpeSpHpjS.js
622 ms
0wM5s1Khldu.js
493 ms
1bNoFZUdlYZ.js
554 ms
njO1TPvGzoR.js
584 ms
OloiM1PZafe.js
660 ms
LTv6ZK-5zxz.js
825 ms
1FCa-btixu2.js
693 ms
Oagsvfb4VWi.js
694 ms
pObvZSrFc_4.js
690 ms
Kt4tkgSRvHH.js
690 ms
H3EKDTObx05.js
692 ms
eR-qA8bp1RM.js
762 ms
1QuX41zDRrx.js
761 ms
11953043_10153642804613653_4939115120789648641_n.jpg
352 ms
safe_image.php
288 ms
safe_image.php
348 ms
safe_image.php
415 ms
safe_image.php
546 ms
11029650_10153602170588653_1373898592510838530_n.jpg
407 ms
11027961_10153437064659510_3088053666895972655_n.jpg
475 ms
10270391_1375196989451977_7414766872274348046_n.jpg
540 ms
12894_897168877014638_8249801137036219736_n.jpg
548 ms
1236744_485298944899715_1508274699_n.jpg
548 ms
12705671_505496016299317_2290561311593761834_n.jpg
555 ms
11012809_907138262671212_3240178536799225969_n.jpg
543 ms
248487_921622111284890_194011614700991034_n.jpg
602 ms
12802882_10153997140693653_5532841049983870641_n.jpg
607 ms
wL6VQj7Ab77.png
119 ms
s7jcwEQH7Sx.png
119 ms
QDwYpIaRyfG.png
119 ms
sSwLTfB7PfP.png
120 ms
K00K-UgnsKu.png
120 ms
gxbPuQdXIZP.png
71 ms
I6-MnjEovm5.js
71 ms
pQrUxxo5oQp.js
137 ms
torontoglobe.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torontoglobe.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 Torontoglobe.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.
torontoglobe.com
Open Graph description is not detected on the main page of Torontoglobe. 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: