Tools & Wizards About Us
search.library.utoronto.ca screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

search.library.utoronto.ca

University of Toronto Libraries

Page Load Speed

746 ms in total

First Response

153 ms

Resources Loaded

465 ms

Page Rendered

128 ms

search.library.utoronto.ca screenshot

About Website

Click here to check amazing Search Library U Toronto content for Canada. Otherwise, check out these important facts you probably never knew about search.library.utoronto.ca

Visit search.library.utoronto.ca

Key Findings

We analyzed Search.library.utoronto.ca page load time and found that the first response time was 153 ms and then it took 593 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

search.library.utoronto.ca performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.2 s

100/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

search.library.utoronto.ca

153 ms

search.library.utoronto.ca

128 ms

styles2.css

23 ms

utl-logo-white-correct.png

161 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 75% of them (3 requests) were addressed to the original Search.library.utoronto.ca, 25% (1 request) were made to Content.library.utoronto.ca. The less responsive or slowest element that took the longest time to load (161 ms) relates to the external source Content.library.utoronto.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.9 kB (14%)

Content Size

27.2 kB

After Optimization

23.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Search.library.utoronto.ca main page is 27.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 25.1 kB which makes up the majority of the site volume.

HTML Optimization

-56%

Potential reduce by 853 B

  • Original 1.5 kB
  • After minification 1.5 kB
  • After compression 673 B

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 853 B or 56% of the original size.

Image Optimization

-12%

Potential reduce by 2.9 kB

  • Original 25.1 kB
  • After minification 22.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. Obviously, Search Library U Toronto needs image optimization as it can save up to 2.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-12%

Potential reduce by 61 B

  • Original 524 B
  • After minification 524 B
  • After compression 463 B

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. Search.library.utoronto.ca needs all CSS files to be minified and compressed as it can save up to 61 B or 12% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

  • Images
  • CSS

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Search Library U Toronto. According to our analytics all requests are already optimized.

Network Requests Diagram

search.library.utoronto.ca

search.library.utoronto.ca

153 ms

search.library.utoronto.ca

search.library.utoronto.ca

128 ms

styles2.css

styles2.css

23 ms

utl-logo-white-correct.png

utl-logo-white-correct.png

161 ms

Accessibility Review

search.library.utoronto.ca accessibility score

93

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

search.library.utoronto.ca best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

search.library.utoronto.ca SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Search.library.utoronto.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Search.library.utoronto.ca main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

search.library.utoronto.ca

Open Graph description is not detected on the main page of Search Library U Toronto. 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: