2.3 sec in total
94 ms
1.5 sec
720 ms
Click here to check amazing ECE Toronto content for China. Otherwise, check out these important facts you probably never knew about ece.toronto.edu
The Edward S. Rogers Sr. Department of Electrical & Computer Engineering (ECE) at the University of Toronto. The future starts here.
Visit ece.toronto.eduWe analyzed Ece.toronto.edu page load time and found that the first response time was 94 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ece.toronto.edu performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value16.1 s
0/100
25%
Value5.4 s
57/100
10%
Value110 ms
98/100
30%
Value0.036
100/100
15%
Value9.7 s
28/100
10%
94 ms
608 ms
139 ms
44 ms
76 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ece.toronto.edu, 78% (69 requests) were made to Ece.utoronto.ca and 11% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (608 ms) relates to the external source Ece.utoronto.ca.
Page size can be reduced by 150.2 kB (5%)
2.8 MB
2.6 MB
In fact, the total size of Ece.toronto.edu main page is 2.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 2.4 MB which makes up the majority of the site volume.
Potential reduce by 135.4 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 135.4 kB or 83% of the original size.
Potential reduce by 3.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. ECE Toronto images are well optimized though.
Potential reduce by 7.4 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 4.2 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. Ece.toronto.edu has all CSS files already compressed.
Number of requests can be reduced by 54 (75%)
72
18
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECE Toronto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
ece.toronto.edu
94 ms
www.ece.utoronto.ca
608 ms
js
139 ms
wp-emoji-release.min.js
44 ms
ece.css
76 ms
tribe-events-pro-mini-calendar-block.min.css
105 ms
style.min.css
137 ms
all.min.css
113 ms
foundation-icons.css
74 ms
733-layout.css
107 ms
ladda.min.css
104 ms
picker.classic.css
145 ms
picker.classic.date.css
151 ms
intlTelInput.css
146 ms
bookly-main.css
156 ms
customer-profile.css
149 ms
tablepress-combined.min.css
159 ms
bootstrap.min.css
168 ms
font-awesome.min.css
177 ms
UofT-Engineering-main.css
180 ms
css
73 ms
animate.min.css
160 ms
css
98 ms
jquery.min.js
223 ms
jquery-migrate.min.js
198 ms
ajax-cart.js
197 ms
frontend-gtag.min.js
197 ms
imagesloaded.min.js
197 ms
spin.min.js
240 ms
ladda.min.js
244 ms
hammer.min.js
245 ms
jquery.hammer.min.js
243 ms
picker.js
248 ms
picker.date.js
249 ms
bookly.min.js
262 ms
intlTelInput.min.js
251 ms
customer-profile.js
251 ms
variables-skeleton.min.css
255 ms
common-skeleton.min.css
255 ms
widget-events-list-skeleton.min.css
257 ms
variables-full.min.css
255 ms
common-full.min.css
361 ms
widget-events-list-full.min.css
334 ms
widget-events-list-skeleton.min.css
301 ms
widget-events-list-full.min.css
272 ms
733-layout.js
266 ms
bootstrap.min.js
259 ms
analytics.js
68 ms
UofT-Engineering.js
245 ms
wp-embed.min.js
234 ms
tribe-common.min.js
231 ms
query-string.js
229 ms
underscore-before.js
229 ms
underscore.min.js
223 ms
underscore-after.js
222 ms
manager.js
215 ms
breakpoints.js
201 ms
linkid.js
8 ms
collect
43 ms
background-shadow.jpg
72 ms
uoft_fase_wordmark_2020.svg
105 ms
Header-image-web.jpg
510 ms
pixel.png
72 ms
IBET-fellowship-300x200.jpeg
72 ms
internet-router-2021-08-30-06-17-35-utc_900x600-650x430-1-300x198.jpeg
83 ms
Paper-brain_650x430-300x198.jpg
83 ms
RossPeters_900x600-650x433-1-300x200.jpeg
83 ms
Josh-San-Miguel_400x500.jpg
237 ms
PeterLehn45.jpeg
237 ms
27632865788_7ac6cb7c66_o-scaled.jpg
444 ms
Sig_Dept_ECE_Standard_White.svg
380 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
162 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
304 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
310 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
352 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
352 ms
fontawesome-webfont.woff
309 ms
fa-solid-900.woff
309 ms
fa-regular-400.woff
352 ms
Prospective-wallpaper-1.jpg
365 ms
MicrosoftTeams-image.jpg
366 ms
people-BKG-tile.jpg
365 ms
foundation-icons.woff
191 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
191 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf
190 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf
206 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf
207 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf
207 ms
ece.toronto.edu accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s are not contained by their required parent element
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
ece.toronto.edu 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
ece.toronto.edu SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Ece.toronto.edu 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 Ece.toronto.edu 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.
ece.toronto.edu
Open Graph data is detected on the main page of ECE Toronto. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: