Tools & Wizards About Us
provost.umd.edu screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

provost.umd.edu

Office of the Provost

Page Load Speed

588 ms in total

First Response

53 ms

Resources Loaded

251 ms

Page Rendered

284 ms

provost.umd.edu screenshot

About Website

Welcome to provost.umd.edu homepage info - get ready to check Provost Umd best content for United States right away, or after learning these important things about provost.umd.edu

Visit provost.umd.edu

Key Findings

We analyzed Provost.umd.edu page load time and found that the first response time was 53 ms and then it took 535 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

provost.umd.edu performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value330 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.196

63/100

15%

TTI (Time to Interactive)

Value8.4 s

40/100

10%

Network Requests Diagram

provost.umd.edu

53 ms

main.min.js

29 ms

screen2movebanner.css

6 ms

coursera.css

11 ms

jquery-1.11.3.min

21 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 82% of them (14 requests) were addressed to the original Provost.umd.edu, 6% (1 request) were made to S3.amazonaws.com and 6% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (53 ms) belongs to the original domain Provost.umd.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.8 kB (44%)

Content Size

346.6 kB

After Optimization

194.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Provost.umd.edu main page is 346.6 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. 35% of websites need less resources to load. Images take 212.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 9.5 kB

  • Original 12.6 kB
  • After minification 10.1 kB
  • After compression 3.1 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 2.5 kB, which is 20% 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 9.5 kB or 75% of the original size.

Image Optimization

-34%

Potential reduce by 72.4 kB

  • Original 212.2 kB
  • After minification 139.8 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, Provost Umd needs image optimization as it can save up to 72.4 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 56.2 kB

  • Original 105.3 kB
  • After minification 102.5 kB
  • After compression 49.1 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 56.2 kB or 53% of the original size.

CSS Optimization

-83%

Potential reduce by 13.7 kB

  • Original 16.5 kB
  • After minification 10.7 kB
  • After compression 2.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. Provost.umd.edu needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (27%)

Requests Now

15

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

provost.umd.edu

provost.umd.edu

53 ms

main.min.js

main.min.js

29 ms

screen2movebanner.css

screen2movebanner.css

6 ms

coursera.css

coursera.css

11 ms

jquery-1.11.3.min

jquery-1.11.3.min

21 ms

interface.js

interface.js

22 ms

jquery.url.packed.js

jquery.url.packed.js

22 ms

jquery.min.js

jquery.min.js

36 ms

ga.js

ga.js

49 ms

body-bg.gif

body-bg.gif

9 ms

mallshotforprovost.jpg

mallshotforprovost.jpg

47 ms

masthead_extend_swerve_fearless.png

masthead_extend_swerve_fearless.png

17 ms

background-repeater.jpg

background-repeater.jpg

16 ms

background-bottom.jpg

background-bottom.jpg

16 ms

background-top.jpg

background-top.jpg

41 ms

mpower_cut_middle.png

mpower_cut_middle.png

39 ms

background-footer.gif

background-footer.gif

39 ms

Accessibility Review

provost.umd.edu accessibility score

100

Accessibility Issues

Best Practices

provost.umd.edu best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

provost.umd.edu SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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 Provost.umd.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 Provost.umd.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

provost.umd.edu

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