1.3 sec in total
168 ms
931 ms
201 ms
Click here to check amazing Ti Uottawa content for Canada. Otherwise, check out these important facts you probably never knew about ti.uottawa.ca
Bienvenue sur le site Web des Technologies de l’information! De l’information en profondeur et des ressources utiles sont à votre disposition. Nous sommes là pour répondre à vos besoins technologiques...
Visit ti.uottawa.caWe analyzed Ti.uottawa.ca page load time and found that the first response time was 168 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.
ti.uottawa.ca performance score
name
value
score
weighting
Value13.9 s
0/100
10%
Value29.0 s
0/100
25%
Value15.3 s
1/100
10%
Value190 ms
91/100
30%
Value1.039
2/100
15%
Value18.3 s
3/100
10%
168 ms
120 ms
122 ms
122 ms
114 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 90% of them (104 requests) were addressed to the original Ti.uottawa.ca, 3% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (295 ms) relates to the external source It.uottawa.ca.
Page size can be reduced by 425.1 kB (40%)
1.1 MB
630.1 kB
In fact, the total size of Ti.uottawa.ca main page is 1.1 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. 50% of websites need less resources to load. Images take 511.4 kB which makes up the majority of the site volume.
Potential reduce by 91.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. 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 91.0 kB or 85% of the original size.
Potential reduce by 12.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. Ti Uottawa images are well optimized though.
Potential reduce by 195.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 195.2 kB or 69% of the original size.
Potential reduce by 126.8 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. Ti.uottawa.ca needs all CSS files to be minified and compressed as it can save up to 126.8 kB or 82% of the original size.
Number of requests can be reduced by 94 (86%)
109
15
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ti Uottawa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 51 to 1 for CSS and as a result speed up the page load time.
ti.uottawa.ca
168 ms
system.base.css
120 ms
system.messages.css
122 ms
system.theme.css
122 ms
ldap_user.css
114 ms
date.css
119 ms
datepicker.1.7.css
113 ms
field.css
134 ms
node.css
151 ms
search.css
148 ms
views.css
149 ms
ctools.css
147 ms
ldap_servers.admin.css
153 ms
panels.css
166 ms
uottawa_m.css
168 ms
uottawa_c.css
171 ms
openlayers.css
170 ms
uottawa_hours.css
172 ms
uottawa_b.css
176 ms
openlayers_behavior_geofield.css
197 ms
uottawa_bh.css
196 ms
view-modes-common._HiMnbgMtG7lcvqqMnwHQUwnlKA7YUNT-mtwdp4fJW4.css
198 ms
corporate.css
195 ms
page_structure.css
196 ms
uz_dirs.css
200 ms
uz_paddings.css
215 ms
uz_widths.css
220 ms
uz_krumo.css
214 ms
uz_polyfill_details.css
220 ms
uza_legacy.css
217 ms
uza_base.css
221 ms
uza_icons.css
234 ms
uza_typography.css
238 ms
uza_node.css
245 ms
uza_forms.css
241 ms
OpenLayers.js
56 ms
js
26 ms
webfont.js
29 ms
uza_tables.css
163 ms
ldap_user.css
124 ms
uza_events.css
144 ms
uza_lists.css
149 ms
uza_common.css
172 ms
uza_back_top.css
151 ms
uza_global_header.css
174 ms
uza_global_navigation.css
141 ms
user.css
102 ms
uza_site_id.css
128 ms
uza_local_navigation.css
140 ms
uza_contact_footer.css
147 ms
uza_global_footer.css
149 ms
uza_inpage_navigation.css
146 ms
uza_corp_home.css
141 ms
rainbow.bfHoIvOh_x2FAcoKOl-24bFhbgYPV7d81r5n9nzTn0Q.css
144 ms
print.css
142 ms
jquery.min.js
223 ms
jquery.once.js
146 ms
drupal.js
158 ms
jquery.cookie.js
131 ms
jquery.form.min.js
132 ms
ajax.js
155 ms
jquery_update.js
142 ms
fr_d5KhnZ1Ai3brJjqu89Jmambx_HnWeY1lFvai0mQldX0.js
151 ms
panels.js
150 ms
uottawa_core.js
139 ms
custom_search.js
143 ms
openlayers.js
151 ms
openlayers_layer_type_google.js
155 ms
progress.js
150 ms
openlayers_behavior_keyboarddefaults.js
152 ms
openlayers_behavior_permalink.js
157 ms
openlayers_behavior_navigation.js
208 ms
ajax_loader.js
206 ms
openlayers_behavior_zoompanel.js
207 ms
openlayers_behavior_layerswitcher.js
203 ms
openlayers_behavior_attribution.js
203 ms
openlayers_behavior_geofield.js
201 ms
openlayers_layer_type_raw.js
201 ms
uottawa_auth.js
191 ms
gnSearchPrimo.js
188 ms
jquery.mobile.custom.min.js
187 ms
jquery.hoverIntent.minified.js
183 ms
uo_supports_css.js
168 ms
uz_polyfill_details.js
168 ms
uo_details_plus.js
163 ms
uza_base.js
168 ms
uza_global_header.js
172 ms
uza_site_id.js
172 ms
uza_global_navigation.js
163 ms
uza_local_navigation.js
160 ms
uza_corp_home.js
157 ms
uza_back_top.js
154 ms
konami.js
152 ms
rainbow.js
155 ms
uottawa_core_styles_grouping.js
151 ms
uza_google_fonts.js
147 ms
css
28 ms
ga.js
107 ms
uottawa_site_icons.png
109 ms
marian-poster-fr.png
295 ms
uOttawa-logo.png
93 ms
icons-spritesheet.png
95 ms
assets_images_dark_grey_texture.png
94 ms
assets_images_light_grey_texture.png
93 ms
it_home_cropped-sm.jpg
159 ms
request_help-sm.jpg
161 ms
back-to-top.png
70 ms
uottawa_site_icons.svg
100 ms
swoosh.png
71 ms
throbber-active.gif
71 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
20 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
25 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
26 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
26 ms
__utm.gif
35 ms
ti.uottawa.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ti.uottawa.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ti.uottawa.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ti.uottawa.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Ti.uottawa.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.
ti.uottawa.ca
Open Graph description is not detected on the main page of Ti Uottawa. 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: