Tools & Wizards About Us
coronavirus.miami.edu screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

coronavirus.miami.edu

Information for Employees | Coronavirus (COVID-19) Information | University of Miami

Page Load Speed

2 sec in total

First Response

50 ms

Resources Loaded

1.7 sec

Page Rendered

324 ms

coronavirus.miami.edu screenshot

About Website

Click here to check amazing Coronavirus Miami content for United States. Otherwise, check out these important facts you probably never knew about coronavirus.miami.edu

Review answers to some of the most frequently asked questions related to COVID-19 from members of the University community. This is a rapidly evolving event and responses below are based on currently ...

Visit coronavirus.miami.edu

Key Findings

We analyzed Coronavirus.miami.edu page load time and found that the first response time was 50 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

coronavirus.miami.edu performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.4

25/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

coronavirus.miami.edu

50 ms

index.html

136 ms

css

53 ms

css

73 ms

3f4f72c343.js

79 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Coronavirus.miami.edu, 67% (33 requests) were made to Cdn.miami.edu and 12% (6 requests) were made to Hr.miami.edu. The less responsive or slowest element that took the longest time to load (934 ms) relates to the external source Cdn.miami.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 161.1 kB (28%)

Content Size

583.5 kB

After Optimization

422.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Coronavirus.miami.edu main page is 583.5 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. 65% of websites need less resources to load. Javascripts take 300.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 127.0 kB

  • Original 148.3 kB
  • After minification 96.2 kB
  • After compression 21.4 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 52.1 kB, which is 35% 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 127.0 kB or 86% of the original size.

Image Optimization

-15%

Potential reduce by 3.5 kB

  • Original 23.4 kB
  • After minification 19.9 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, Coronavirus Miami needs image optimization as it can save up to 3.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 9.2 kB

  • Original 300.7 kB
  • After minification 300.1 kB
  • After compression 291.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. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 21.4 kB

  • Original 111.1 kB
  • After minification 109.0 kB
  • After compression 89.7 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. Coronavirus.miami.edu needs all CSS files to be minified and compressed as it can save up to 21.4 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (76%)

Requests Now

41

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

coronavirus.miami.edu

coronavirus.miami.edu

50 ms

index.html

index.html

136 ms

css

css

53 ms

css

css

73 ms

3f4f72c343.js

3f4f72c343.js

79 ms

foundation-6.css

foundation-6.css

544 ms

legacy.css

legacy.css

558 ms

slick-6.css

slick-6.css

561 ms

foundation-icons.css

foundation-icons.css

573 ms

jquery.reject.css

jquery.reject.css

575 ms

umiami.css

umiami.css

626 ms

generic.css

generic.css

701 ms

beautifuldata.css

beautifuldata.css

632 ms

site.css

site.css

29 ms

theme.css

theme.css

38 ms

modernizr.js

modernizr.js

647 ms

js

js

123 ms

page.js

page.js

54 ms

jquery-3.js

jquery-3.js

809 ms

jquery-migrate.js

jquery-migrate.js

691 ms

foundation-6.js

foundation-6.js

934 ms

what-input.js

what-input.js

809 ms

slick-6.js

slick-6.js

813 ms

beautifuldata.js

beautifuldata.js

814 ms

jquery.reject.js

jquery.reject.js

814 ms

reject-browsers.js

reject-browsers.js

815 ms

jquery.xdomainrequest.min.js

jquery.xdomainrequest.min.js

816 ms

core-library-6.js

core-library-6.js

872 ms

um-navigation.js

um-navigation.js

871 ms

related-content.js

related-content.js

872 ms

nav-scripts.js

nav-scripts.js

37 ms

gtm.js

gtm.js

134 ms

logo_hr_329x77.svg

logo_hr_329x77.svg

65 ms

btn-over-15.png

btn-over-15.png

177 ms

icon-eye-open-white.svg

icon-eye-open-white.svg

177 ms

um-print-logo.png

um-print-logo.png

179 ms

um-logo-gray-bg.png

um-logo-gray-bg.png

180 ms

logo_hr_216x52.svg

logo_hr_216x52.svg

60 ms

sm.25.html

sm.25.html

87 ms

eso.Ep5bSEmr.js

eso.Ep5bSEmr.js

88 ms

x-twitter-w.svg

x-twitter-w.svg

317 ms

StagSans-Light.woff

StagSans-Light.woff

256 ms

StagSans-Bold.woff

StagSans-Bold.woff

254 ms

StagSans-Book.woff

StagSans-Book.woff

256 ms

Stag-Light.woff

Stag-Light.woff

97 ms

StagSans-Medium.woff

StagSans-Medium.woff

95 ms

foundation-icons.woff

foundation-icons.woff

138 ms

js

js

145 ms

print.css

print.css

71 ms

Accessibility Review

coronavirus.miami.edu accessibility score

75

Accessibility Issues

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.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

coronavirus.miami.edu best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

coronavirus.miami.edu SEO score

82

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

    EN

  • Encoding

    UTF-8

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

coronavirus.miami.edu

Open Graph data is detected on the main page of Coronavirus Miami. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: