Tools & Wizards About Us
research.umn.edu screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

research.umn.edu

RIO | RIO

Page Load Speed

3.9 sec in total

First Response

578 ms

Resources Loaded

3.2 sec

Page Rendered

137 ms

research.umn.edu screenshot

About Website

Visit research.umn.edu now to see the best up-to-date Research Umn content for United States and also check out these interesting facts you probably never knew about research.umn.edu

The OVPR guides U of M faculty in their research and promotes partnerships with business and industry.

Visit research.umn.edu

Key Findings

We analyzed Research.umn.edu page load time and found that the first response time was 578 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

research.umn.edu performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

research.umn.edu

578 ms

reset.css

715 ms

text_new.css

738 ms

ovpr_style.css

762 ms

ovpr_new.css

736 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 64% of them (36 requests) were addressed to the original Research.umn.edu, 13% (7 requests) were made to Apis.google.com and 7% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Research.umn.edu.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

935.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Research.umn.edu main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 755.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 121.4 kB

  • Original 160.3 kB
  • After minification 158.2 kB
  • After compression 38.9 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 121.4 kB or 76% of the original size.

Image Optimization

-11%

Potential reduce by 80.0 kB

  • Original 717.9 kB
  • After minification 637.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, Research Umn needs image optimization as it can save up to 80.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 502.1 kB

  • Original 755.1 kB
  • After minification 752.5 kB
  • After compression 253.0 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 502.1 kB or 66% of the original size.

CSS Optimization

-79%

Potential reduce by 21.2 kB

  • Original 26.8 kB
  • After minification 19.4 kB
  • After compression 5.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. Research.umn.edu needs all CSS files to be minified and compressed as it can save up to 21.2 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (49%)

Requests Now

53

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

research.umn.edu

research.umn.edu

578 ms

reset.css

reset.css

715 ms

text_new.css

text_new.css

738 ms

ovpr_style.css

ovpr_style.css

762 ms

ovpr_new.css

ovpr_new.css

736 ms

optional.css

optional.css

737 ms

default.css

default.css

714 ms

nivo-slider.css

nivo-slider.css

714 ms

searchfield.js

searchfield.js

736 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

866 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

718 ms

addthis_widget.js

addthis_widget.js

19 ms

ga.js

ga.js

30 ms

bg_header.gif

bg_header.gif

363 ms

__utm.gif

__utm.gif

21 ms

logo_uofm_D2D.gif

logo_uofm_D2D.gif

546 ms

btn_onestop.gif

btn_onestop.gif

547 ms

btn_myu.gif

btn_myu.gif

546 ms

search_field.gif

search_field.gif

546 ms

search_button.gif

search_button.gif

353 ms

home.jpg

home.jpg

1011 ms

research.jpg

research.jpg

1037 ms

business.jpg

business.jpg

987 ms

news.jpg

news.jpg

1258 ms

about.jpg

about.jpg

1257 ms

background.jpg

background.jpg

1061 ms

loading.gif

loading.gif

1233 ms

MN-IP_button.jpg

MN-IP_button.jpg

1436 ms

5YF_button.jpg

5YF_button.jpg

1430 ms

cc_button2.jpg

cc_button2.jpg

1435 ms

smMwdmk.gif

smMwdmk.gif

541 ms

BlackHole.jpg

BlackHole.jpg

787 ms

capitol.jpg

capitol.jpg

813 ms

family.jpg

family.jpg

814 ms

spouts.jpg

spouts.jpg

812 ms

MnDRIVE.jpg

MnDRIVE.jpg

787 ms

300lo.json

300lo.json

50 ms

plusone.js

plusone.js

47 ms

counter.8eb9e83b9fa0d4af1e4f.js

counter.8eb9e83b9fa0d4af1e4f.js

5 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

28 ms

shares.json

shares.json

29 ms

layers.3643cb2e25fb91c29386.js

layers.3643cb2e25fb91c29386.js

19 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

54 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

69 ms

fastbutton

fastbutton

167 ms

postmessageRelay

postmessageRelay

35 ms

pixel

pixel

21 ms

pixel

pixel

25 ms

api.js

api.js

35 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

75 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

29 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

41 ms

about_title_roll.jpg

about_title_roll.jpg

169 ms

arrows.png

arrows.png

368 ms

bullets.png

bullets.png

367 ms

Accessibility Review

research.umn.edu accessibility score

97

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

research.umn.edu best practices score

75

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

Browser errors were logged to the console

SEO Factors

research.umn.edu SEO score

78

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Research.umn.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 Research.umn.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

research.umn.edu

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