6.4 sec in total
1.6 sec
4.4 sec
330 ms
Welcome to toronto.usconsulate.gov homepage info - get ready to check Toronto U S Consulate best content for Hong Kong right away, or after learning these important things about toronto.usconsulate.gov
Welcome to the U.S. Consulate General Toronto The U.S. Consulate General Toronto is located downtown at 360 University Avenue, on the west side, between Dundas and Queen Street, midway between the St....
Visit toronto.usconsulate.govWe analyzed Toronto.usconsulate.gov page load time and found that the first response time was 1.6 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
toronto.usconsulate.gov performance score
1647 ms
72 ms
88 ms
98 ms
208 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Toronto.usconsulate.gov, 13% (14 requests) were made to Maps.googleapis.com and 11% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Ca.usembassy.gov.
Page size can be reduced by 1.8 MB (47%)
3.8 MB
2.0 MB
In fact, the total size of Toronto.usconsulate.gov main page is 3.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. 80% 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 197.7 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 197.7 kB or 80% of the original size.
Potential reduce by 339.4 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. Obviously, Toronto U S Consulate needs image optimization as it can save up to 339.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.2 MB
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 1.2 MB or 67% of the original size.
Potential reduce by 26.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. Toronto.usconsulate.gov needs all CSS files to be minified and compressed as it can save up to 26.7 kB or 78% of the original size.
Number of requests can be reduced by 52 (58%)
90
38
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Toronto U S Consulate. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
1647 ms
analytics.js
72 ms
wp-emoji-release.min.js
88 ms
css
98 ms
208 ms
301 ms
jquery.js
116 ms
jquery-migrate.min.js
85 ms
federated-analytics.js
85 ms
addthis_widget.js
80 ms
152 ms
js
114 ms
156 ms
collect
31 ms
collect
47 ms
collect
50 ms
collect
24 ms
remote.loader.js
453 ms
10014524-10015207.js
411 ms
dos-logo-light.png
757 ms
travel_photo_no_text_243x115px_360.png
167 ms
obama-trudeau-750x350.jpg
136 ms
work_with_us_no_text_244x116px_360.png
169 ms
smith-kiki-750x450.jpg
137 ms
default-blog-seal.png
192 ms
dhs-goodale-750x450.jpg
191 ms
1908982-750x450.jpg
166 ms
1803799-750x450.jpg
493 ms
amb-naismith-750x450.jpg
775 ms
AP_909309733101-750x450.jpg
752 ms
AP_134544230327-750x450.jpg
492 ms
to-mayfield-750x450.jpg
751 ms
130611074931business_grants-50x50.jpg
843 ms
AdobeComparison-50x50.png
841 ms
us-flag-logo.png
842 ms
sdk.js
134 ms
gtm.js
214 ms
header-bg.png
914 ms
arrowdown.png
913 ms
embed
737 ms
sayt.css
127 ms
sayt_loader_libs.js
711 ms
stats.js
881 ms
arrows.png
880 ms
5M21SdFLkD52QavfmHs6cA.ttf
766 ms
97uahxiqZRoncBaCEI3aW6CWcynf_cDxXwCLxiixG1c.ttf
765 ms
AWM5wXtMJeRP-AcRTgT4qQ.ttf
678 ms
dI-qzxlKVQA6TUC5RKSb36CWcynf_cDxXwCLxiixG1c.ttf
708 ms
fontawesome-webfont.woff
936 ms
fontawesome-webfont.woff
863 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
784 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
707 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
707 ms
728 ms
widgets.js
706 ms
xd_arbiter.php
777 ms
hotjar-164237.js
603 ms
300lo.json
331 ms
sh.8e5f85691f9aaa082472a194.html
64 ms
js
146 ms
init_embed.js
301 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
30 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
181 ms
682298381033697285
548 ms
common.js
97 ms
map.js
114 ms
google4.png
155 ms
overlay.js
146 ms
util.js
174 ms
onion.js
151 ms
search_impl.js
151 ms
StaticMapService.GetMapImage
412 ms
layers.e5ea973510bf60b3db41.js
108 ms
stats.js
85 ms
openhand_8_8.cur
46 ms
ViewportInfoService.GetViewportInfo
289 ms
ViewportInfoService.GetViewportInfo
40 ms
kh
301 ms
transparent.png
34 ms
ViewportInfoService.GetViewportInfo
28 ms
controls.js
40 ms
proxy.jpg
337 ms
proxy.jpg
197 ms
ui-bg_flat_75_ffffff_40x100.png
130 ms
css
95 ms
entity11.png
95 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
48 ms
vt
108 ms
vt
224 ms
vt
205 ms
vt
208 ms
vt
205 ms
mapcnt6.png
56 ms
sv5.png
56 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
46 ms
M1VBSza3_normal.jpg
198 ms
oxerX_GS_normal.jpeg
208 ms
tmapctrl.png
138 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
120 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
131 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
34 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
34 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
34 ms
toronto.usconsulate.gov SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toronto.usconsulate.gov 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 Toronto.usconsulate.gov 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.
toronto.usconsulate.gov
Open Graph data is detected on the main page of Toronto U S Consulate. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: