Umn.edu University of Minnesota Twin Cities
The University of Minnesota is a highly ranked public research university offering a wide range of undergraduate and graduate programs. We change live...
umn.edu Desktop Performance
64/100
These metrics represent real-world Chrome users experience viewing umn.edu web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
First Input Delay
First Contentful Paint
Cumulative Layout Shift
Largest Contentful Paint
Metrics
Cumulative Layout Shift24/100 0.416
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Largest Contentful Paint39/100 2.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint48/100 1.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index54/100 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive86/100 2.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time100/100 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Should Fix (18)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Properly size images
Potential savings of 839 KiB
1,040 ms
Serve images in next-gen formats
Potential savings of 896 KiB
1,030 ms
Eliminate render-blocking resources
Potential savings of 990 ms
990 ms
Avoid multiple page redirects
Potential savings of 380 ms
380 ms
Efficiently encode images
Potential savings of 108 KiB
320 ms
Remove unused JavaScript
Potential savings of 328 KiB
160 ms
Minify JavaScript
Potential savings of 29 KiB
80 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Ensure text remains visible during webfont load
Avoid `document.write()`
Serve static assets with an efficient cache policy
47 resources found
Avoid enormous network payloads
Total size was 3,878 KiB
Avoid an excessive DOM size
865 elements
Avoid long main-thread tasks
2 long tasks found
Keep request counts low and transfer sizes small
94 requests • 3,878 KiB
Avoid large layout shifts
5 elements found
Largest Contentful Paint element
1 element found
Avoid chaining critical requests
25 chains found
Passed Audits (11)
Preload key requests
JavaScript execution time
0.3 s
Minimizes main-thread work
1.0 s
Minimize third-party usage
Third-party code blocked the main thread for 0 ms
Preconnect to required origins
Use video formats for animated content
Defer offscreen images
Remove unused CSS
Potential savings of 25 KiB
Enable text compression
Minify CSS
Potential savings of 5 KiB
Initial server response time was short
Root document took 280 ms
umn.edu Desktop SEO
100/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Passed Audits (12)
Document has a `<title>` element
Document has a valid `hreflang`
Image elements have `[alt]` attributes
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document has a meta description
Page has successful HTTP status code
robots.txt is valid
Links have descriptive text
Links are crawlable
Document has a valid `rel=canonical`
Document avoids plugins
Page isn’t blocked from indexing
umn.edu Desktop Best Practices
69/100
These checks highlight opportunities to improve the overall code health of umn.edu page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
General
Browser errors were logged to the console
Trust and Safety
Does not use HTTPS
2 insecure requests found
Links to cross-origin destinations are unsafe
Includes front-end JavaScript libraries with known security vulnerabilities
7 vulnerabilities detected
Passed Audits (10)
Detected JavaScript libraries
Page has the HTML doctype
Displays images with correct aspect ratio
Allows users to paste into password fields
Avoids requesting the geolocation permission on page load
Avoids Application Cache
Avoids deprecated APIs
Avoids requesting the notification permission on page load
Properly defines charset
Serves images with appropriate resolution
umn.edu Desktop Progressive Web App
19/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (10)
PWA Optimized
Is not configured for a custom splash screen
Manifest doesn't have a maskable icon
Does not provide a valid `apple-touch-icon`
Does not set a theme color for the address bar.
Installable
Does not use HTTPS
2 insecure requests found
Does not register a service worker that controls page and `start_url`
Web app manifest does not meet the installability requirements
Fast and reliable
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 19.2 s
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
Passed Audits (3)
Redirects HTTP traffic to HTTPS
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Contains some content when JavaScript is not available
umn.edu Desktop Accessibility
75/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (6)
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes do not have valid values
`[role]`s do not have all required `[aria-*]` attributes
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.
Form elements do not have associated labels
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (20)
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-*]` attributes are valid and not misspelled
Heading elements appear in a sequentially-descending order
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]` values are valid
Document has a `<title>` element
`<video>` elements contain a `<track>` element with `[kind="description"]`
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Image elements have `[alt]` attributes
`<html>` element has a `[lang]` attribute
ARIA IDs are unique
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`[aria-hidden="true"]` elements do not contain focusable descendents
No element has a `[tabindex]` value greater than 0
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[role]`s are contained by their required parent element
The page contains a heading, skip link, or landmark region
`[aria-*]` attributes match their roles
`<html>` element has a valid value for its `[lang]` attribute
`[aria-hidden="true"]` is not present on the document `<body>`
Desktop Speed
59/100
These checks analyze the performance of umn.edu on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (5)
Optimize images
Avoid landing page redirects
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Minify JavaScript
Leverage browser caching
Passed Audits (5)
Enable compression
Reduce server response time
Minify CSS
Minify HTML
Prioritize visible content
www.umn.com
www.umn.net
www.umn.org
www.umn.info
www.umn.biz
www.umn.us
www.umn.mobi
www.mn.edu
www.umn.edu
www.ymn.edu
www.uymn.edu
www.yumn.edu
www.hmn.edu
www.uhmn.edu
www.humn.edu
www.jmn.edu
www.ujmn.edu
www.jumn.edu
www.imn.edu
www.uimn.edu
www.iumn.edu
www.un.edu
www.unn.edu
www.umnn.edu
www.unmn.edu
www.ujn.edu
www.umjn.edu
www.ukn.edu
www.umkn.edu
www.ukmn.edu
www.um.edu
www.umb.edu
www.umnb.edu
www.umbn.edu
www.umh.edu
www.umnh.edu
www.umhn.edu
www.umj.edu
www.umnj.edu
www.umm.edu
www.umnm.edu
www.ummn.edu
www.umn.net
www.umn.org
www.umn.info
www.umn.biz
www.umn.us
www.umn.mobi
www.mn.edu
www.umn.edu
www.ymn.edu
www.uymn.edu
www.yumn.edu
www.hmn.edu
www.uhmn.edu
www.humn.edu
www.jmn.edu
www.ujmn.edu
www.jumn.edu
www.imn.edu
www.uimn.edu
www.iumn.edu
www.un.edu
www.unn.edu
www.umnn.edu
www.unmn.edu
www.ujn.edu
www.umjn.edu
www.ukn.edu
www.umkn.edu
www.ukmn.edu
www.um.edu
www.umb.edu
www.umnb.edu
www.umbn.edu
www.umh.edu
www.umnh.edu
www.umhn.edu
www.umj.edu
www.umnj.edu
www.umm.edu
www.umnm.edu
www.ummn.edu