Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

map.wisc.edu

Campus Map | University of Wisconsin–Madison

Page Load Speed

855 ms in total

First Response

164 ms

Resources Loaded

551 ms

Page Rendered

140 ms

map.wisc.edu screenshot

About Website

Click here to check amazing Map Wisc content for United States. Otherwise, check out these important facts you probably never knew about map.wisc.edu

Visit map.wisc.edu

Key Findings

We analyzed Map.wisc.edu page load time and found that the first response time was 164 ms and then it took 691 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

map.wisc.edu performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

map.wisc.edu

164 ms

application-0eb1e5479b8a7213cf5293e88dc6e8d7.css

119 ms

rwd-min-880-d5a7ab09a184ca2ee981aaaeb387d816.css

68 ms

jquery.min.js

34 ms

application-9ec42fe51ed52e4515457d6bbe84ae83.js

257 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 80% of them (16 requests) were addressed to the original Map.wisc.edu, 10% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (257 ms) belongs to the original domain Map.wisc.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 335.0 kB (66%)

Content Size

508.9 kB

After Optimization

173.9 kB

In fact, the total size of Map.wisc.edu main page is 508.9 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. 15% of websites need less resources to load. Javascripts take 348.2 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 6.9 kB

  • Original 10.6 kB
  • After minification 10.6 kB
  • After compression 3.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. 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 6.9 kB or 65% of the original size.

Image Optimization

-0%

Potential reduce by 121 B

  • Original 27.5 kB
  • After minification 27.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. Map Wisc images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 234.8 kB

  • Original 348.2 kB
  • After minification 348.2 kB
  • After compression 113.4 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 234.8 kB or 67% of the original size.

CSS Optimization

-76%

Potential reduce by 93.1 kB

  • Original 122.6 kB
  • After minification 122.6 kB
  • After compression 29.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. Map.wisc.edu needs all CSS files to be minified and compressed as it can save up to 93.1 kB or 76% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Map Wisc. According to our analytics all requests are already optimized.

Accessibility Review

map.wisc.edu accessibility score

93

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

map.wisc.edu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

SEO Factors

map.wisc.edu SEO score

90

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

    N/A

  • Encoding

    UTF-8

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