Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

library.wisc.edu

UW-Madison Libraries

Page Load Speed

1.2 sec in total

First Response

115 ms

Resources Loaded

787 ms

Page Rendered

297 ms

library.wisc.edu screenshot

About Website

Welcome to library.wisc.edu homepage info - get ready to check Library Wisc best content for United States right away, or after learning these important things about library.wisc.edu

Visit library.wisc.edu

Key Findings

We analyzed Library.wisc.edu page load time and found that the first response time was 115 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.

Performance Metrics

library.wisc.edu performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

library.wisc.edu

115 ms

www.library.wisc.edu

178 ms

site-c3a8add91e5a951676946ac0dda03494.css

119 ms

default.min.css

67 ms

jetpack.css

72 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 71% of them (24 requests) were addressed to the original Library.wisc.edu, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (320 ms) belongs to the original domain Library.wisc.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 673.3 kB (45%)

Content Size

1.5 MB

After Optimization

825.7 kB

In fact, the total size of Library.wisc.edu main page is 1.5 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. 45% of websites need less resources to load. Images take 652.5 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 50.8 kB

  • Original 73.6 kB
  • After minification 71.9 kB
  • After compression 22.8 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 50.8 kB or 69% of the original size.

Image Optimization

-6%

Potential reduce by 38.4 kB

  • Original 652.5 kB
  • After minification 614.1 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. Library Wisc images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 336.6 kB

  • Original 474.8 kB
  • After minification 474.7 kB
  • After compression 138.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 336.6 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 247.5 kB

  • Original 298.1 kB
  • After minification 295.7 kB
  • After compression 50.6 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. Library.wisc.edu needs all CSS files to be minified and compressed as it can save up to 247.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (32%)

Requests Now

22

After Optimization

15

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

Accessibility Review

library.wisc.edu accessibility score

100

Accessibility Issues

Best Practices

library.wisc.edu best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

library.wisc.edu SEO score

89

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Library.wisc.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 Library.wisc.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.

Social Sharing Optimization

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