1.8 sec in total
77 ms
1.5 sec
188 ms
Visit lib.uwaterloo.ca now to see the best up-to-date Lib U Waterloo content for Canada and also check out these interesting facts you probably never knew about lib.uwaterloo.ca
Visit lib.uwaterloo.caWe analyzed Lib.uwaterloo.ca page load time and found that the first response time was 77 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
lib.uwaterloo.ca performance score
name
value
score
weighting
Value15.0 s
0/100
10%
Value15.6 s
0/100
25%
Value17.1 s
0/100
10%
Value450 ms
63/100
30%
Value0.343
32/100
15%
Value19.6 s
2/100
10%
77 ms
34 ms
56 ms
55 ms
38 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 83% of them (134 requests) were addressed to the original Lib.uwaterloo.ca, 7% (12 requests) were made to Use.typekit.net and 3% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (325 ms) belongs to the original domain Lib.uwaterloo.ca.
Page size can be reduced by 79.9 kB (35%)
228.0 kB
148.1 kB
In fact, the total size of Lib.uwaterloo.ca main page is 228.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. 65% of websites need less resources to load. Javascripts take 100.7 kB which makes up the majority of the site volume.
Potential reduce by 57.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. This page needs HTML code to be minified as it can gain 11.5 kB, which is 16% 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 57.7 kB or 82% of the original size.
Potential reduce by 1.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, Lib U Waterloo needs image optimization as it can save up to 1.4 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 18.5 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. Lib.uwaterloo.ca needs all CSS files to be minified and compressed as it can save up to 18.5 kB or 35% of the original size.
Number of requests can be reduced by 135 (94%)
143
8
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lib U Waterloo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 124 to 1 for CSS and as a result speed up the page load time.
lib.uwaterloo.ca
77 ms
index.php
34 ms
56 ms
js
55 ms
google_tag.script.js
38 ms
google_tag.script.js
116 ms
normalize.css
117 ms
normalize-fixes.css
127 ms
ajax-progress.module.css
187 ms
align.module.css
186 ms
autocomplete-loading.module.css
187 ms
fieldgroup.module.css
185 ms
container-inline.module.css
142 ms
clearfix.module.css
187 ms
details.module.css
251 ms
hidden.module.css
252 ms
item-list.module.css
250 ms
js.module.css
251 ms
nowrap.module.css
250 ms
position-container.module.css
248 ms
progress.module.css
274 ms
reset-appearance.module.css
268 ms
resize.module.css
273 ms
sticky-header.module.css
270 ms
system-status-counter.css
267 ms
system-status-report-counters.css
268 ms
system-status-report-general-info.css
288 ms
tabledrag.module.css
287 ms
tablesort.module.css
288 ms
tree-child.module.css
290 ms
core.css
294 ms
tabs.css
291 ms
onecol.css
306 ms
radix_layouts.css
308 ms
theme.css
310 ms
blocktabs.css
313 ms
nice_menus.css
312 ms
nice_menus_default.css
315 ms
elements.css
325 ms
mvh4dfd.css
239 ms
font-awesome.min.css
98 ms
jquery.min.js
29 ms
hours_today.js
250 ms
load_chat.php
248 ms
layout.css
320 ms
action-links.css
308 ms
js
95 ms
analytics.js
44 ms
breadcrumb.css
230 ms
button.css
228 ms
collapse-processed.css
221 ms
container-inline.css
213 ms
collect
77 ms
details.css
172 ms
exposed-filters.css
178 ms
field.css
180 ms
form.css
180 ms
icons.css
183 ms
inline-form.css
126 ms
item-list.css
127 ms
link.css
134 ms
p.css
27 ms
links.css
136 ms
menu.css
137 ms
more-link.css
142 ms
pager.css
127 ms
tabledrag.css
128 ms
tableselect.css
136 ms
tablesort.css
141 ms
tabs.css
138 ms
textarea.css
144 ms
ui-dialog.css
128 ms
messages.css
128 ms
node.css
136 ms
block.css
146 ms
book.css
144 ms
breadcrumb.css
146 ms
captions.css
132 ms
comments.css
132 ms
contextual.css
137 ms
demo-block.css
141 ms
dropbutton.component.css
144 ms
featured-top.css
140 ms
feed-icon.css
133 ms
field.css
131 ms
form.css
136 ms
forum.css
142 ms
header.css
141 ms
help.css
141 ms
highlighted.css
134 ms
item-list.css
134 ms
list-group.css
135 ms
list.css
143 ms
main-content.css
142 ms
menu.css
140 ms
messages.css
135 ms
node.css
134 ms
node-preview.css
135 ms
page-title.css
145 ms
pager.css
139 ms
panel.css
139 ms
primary-menu.css
138 ms
search-form.css
137 ms
search-results.css
134 ms
secondary-menu.css
139 ms
shortcut.css
144 ms
skip-link.css
139 ms
sidebar.css
136 ms
site-branding.css
138 ms
site-footer.css
134 ms
table.css
135 ms
tablesort-indicator.css
137 ms
tabs.css
136 ms
text-formatted.css
138 ms
ask-us
136 ms
toolbar.css
130 ms
featured-bottom.css
130 ms
password-suggestions.css
138 ms
ui.widget.css
138 ms
vertical-tabs.component.css
140 ms
views.css
140 ms
buttons.css
141 ms
image-button.css
133 ms
ui-dialog.css
137 ms
site-footer.css
138 ms
colors.css
138 ms
header_footer.css
139 ms
otherpages.css
139 ms
uw-library-old.css
136 ms
homepage.css
135 ms
admin-e288aca8adb119b2cf479efb809461a1.css
139 ms
events-26f835c7cc3e402c2eabfd2fa8cd8792.css
142 ms
home_page_customizations-657be82df814bcf2e0c5b359faa18c2c.css
140 ms
libchat_widget_styling-2f32feba674f9e5bad89dccce907dc3a.css
138 ms
nome_page_alerts_link-075d7aa3247b86cf2a63586edbae1e0a.css
138 ms
pandemic_changes_frontpage-e162722e35255744d9ab9803f9e43352.css
134 ms
reference_shelf_header-84c85d006c9012600646fbd5a1d933ee.css
138 ms
tmp-a356098e07c9b66220f199ce7067ff7f.css
140 ms
js_Vn6Q6x6yy5k_F9tmB06-D9MlgyHYroi44oD0l3EhfWs.js
160 ms
js_7Dkqhkz0Zu3XMhbMa2DwffDtLOY061MdBrn_K3fTDqg.js
141 ms
logo_uw.svg
139 ms
ask-us.png
136 ms
print.css
25 ms
index.php
31 ms
33 ms
gtm.js
98 ms
gtm.js
157 ms
today
65 ms
fontawesome-webfont.woff
64 ms
d
55 ms
d
69 ms
d
141 ms
d
139 ms
d
144 ms
d
147 ms
d
145 ms
d
139 ms
d
141 ms
d
142 ms
d
145 ms
js
104 ms
lib.uwaterloo.ca accessibility score
lib.uwaterloo.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
Browser errors were logged to the console
lib.uwaterloo.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lib.uwaterloo.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 Lib.uwaterloo.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.
lib.uwaterloo.ca
Open Graph description is not detected on the main page of Lib U Waterloo. 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: