Tools & Wizards About Us
fis.utoronto.ca screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fis.utoronto.ca

Default Web Site Page

Page Load Speed

2.8 sec in total

First Response

65 ms

Resources Loaded

2.6 sec

Page Rendered

162 ms

fis.utoronto.ca screenshot

About Website

Visit fis.utoronto.ca now to see the best up-to-date Fis Utoronto content for Canada and also check out these interesting facts you probably never knew about fis.utoronto.ca

Visit fis.utoronto.ca

Key Findings

We analyzed Fis.utoronto.ca page load time and found that the first response time was 65 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

fis.utoronto.ca performance score

0

Network Requests Diagram

fis.utoronto.ca

65 ms

current.ischool.utoronto.ca

132 ms

aggregator.css

46 ms

book.css

48 ms

node.css

53 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fis.utoronto.ca, 96% (72 requests) were made to Current.ischool.utoronto.ca and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Current.ischool.utoronto.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 346.1 kB (37%)

Content Size

947.0 kB

After Optimization

600.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fis.utoronto.ca main page is 947.0 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. 30% of websites need less resources to load. Images take 534.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 35.5 kB

  • Original 43.9 kB
  • After minification 39.2 kB
  • After compression 8.3 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 4.6 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 35.5 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 32.5 kB

  • Original 534.9 kB
  • After minification 502.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. Fis Utoronto images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 169.2 kB

  • Original 237.1 kB
  • After minification 185.0 kB
  • After compression 67.9 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 169.2 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 108.9 kB

  • Original 131.2 kB
  • After minification 83.5 kB
  • After compression 22.3 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. Fis.utoronto.ca needs all CSS files to be minified and compressed as it can save up to 108.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (75%)

Requests Now

73

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fis Utoronto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fis.utoronto.ca

fis.utoronto.ca

65 ms

current.ischool.utoronto.ca

current.ischool.utoronto.ca

132 ms

aggregator.css

aggregator.css

46 ms

book.css

book.css

48 ms

node.css

node.css

53 ms

defaults.css

defaults.css

51 ms

system.css

system.css

54 ms

system-menus.css

system-menus.css

57 ms

user.css

user.css

69 ms

content-module.css

content-module.css

70 ms

ckeditor.css

ckeditor.css

73 ms

date.css

date.css

74 ms

ui.datepicker.css

ui.datepicker.css

77 ms

jquery.timeentry.css

jquery.timeentry.css

79 ms

dhtml_menu.css

dhtml_menu.css

88 ms

filefield.css

filefield.css

91 ms

lightbox_alt.css

lightbox_alt.css

95 ms

views_slideshow.css

views_slideshow.css

95 ms

views_slideshow.css

views_slideshow.css

96 ms

views_table_highlighter.css

views_table_highlighter.css

98 ms

farbtastic.css

farbtastic.css

111 ms

calendar.css

calendar.css

114 ms

fieldgroup.css

fieldgroup.css

115 ms

views.css

views.css

116 ms

nivo-slider.css

nivo-slider.css

117 ms

custom-nivo-slider.css

custom-nivo-slider.css

122 ms

style.css

style.css

134 ms

typography.css

typography.css

137 ms

superfish.css

superfish.css

138 ms

superfish-navbar.css

superfish-navbar.css

140 ms

superfish-vertical.css

superfish-vertical.css

141 ms

fusion-ischool.css

fusion-ischool.css

173 ms

grid24-1008.css

grid24-1008.css

157 ms

jquery.min.js

jquery.min.js

187 ms

drupal.js

drupal.js

164 ms

dhtml_menu.js

dhtml_menu.js

165 ms

lightbox.js

lightbox.js

186 ms

no_colons.js

no_colons.js

172 ms

spamspan.compressed.js

spamspan.compressed.js

171 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

169 ms

views_slideshow.js

views_slideshow.js

167 ms

views_slideshow.js

views_slideshow.js

167 ms

base.js

base.js

166 ms

ajax_view.js

ajax_view.js

171 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

160 ms

views_nivo_slider.js

views_nivo_slider.js

160 ms

jquery.bgiframe.min.js

jquery.bgiframe.min.js

160 ms

hoverIntent.js

hoverIntent.js

164 ms

supposition.js

supposition.js

166 ms

supersubs.js

supersubs.js

172 ms

superfish.js

superfish.js

160 ms

script.js

script.js

162 ms

jquery.equalheights.js

jquery.equalheights.js

163 ms

ga.js

ga.js

119 ms

logo.png

logo.png

94 ms

block-bg-sprite.png

block-bg-sprite.png

94 ms

ischool-logo-25height.png

ischool-logo-25height.png

94 ms

body-tree-background.png

body-tree-background.png

95 ms

twitter.png

twitter.png

862 ms

youtube.png

youtube.png

858 ms

facebook.png

facebook.png

700 ms

linkedin.png

linkedin.png

852 ms

flickr-2.png

flickr-2.png

839 ms

blog-icon-box-rev-32.png

blog-icon-box-rev-32.png

968 ms

register-herobox.jpg

register-herobox.jpg

1473 ms

irenokeydatescurrenthero.jpg

irenokeydatescurrenthero.jpg

1688 ms

instaj.jpg

instaj.jpg

1709 ms

currentpreserveboundless.jpg

currentpreserveboundless.jpg

1811 ms

herobox-715x320.jpg

herobox-715x320.jpg

1801 ms

isi-logo.gif

isi-logo.gif

1757 ms

ipsi_208x66white.gif

ipsi_208x66white.gif

2046 ms

kmdi_logo.gif

kmdi_logo.gif

2101 ms

image.gif

image.gif

1737 ms

bullets9.png

bullets9.png

1674 ms

__utm.gif

__utm.gif

12 ms

SEO Factors

fis.utoronto.ca SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fis.utoronto.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 Fis.utoronto.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.

Social Sharing Optimization

fis.utoronto.ca

Open Graph description is not detected on the main page of Fis Utoronto. 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: