1.4 sec in total
129 ms
818 ms
501 ms
Visit coronavirus.duke.edu now to see the best up-to-date Coronavirus Duke content for United States and also check out these interesting facts you probably never knew about coronavirus.duke.edu
Get the latest updates and information about the 2019 Novel Coronavirus (COVID-19) and changes that affect the Duke community.
Visit coronavirus.duke.eduWe analyzed Coronavirus.duke.edu page load time and found that the first response time was 129 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
coronavirus.duke.edu performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value5.4 s
20/100
25%
Value3.5 s
87/100
10%
Value110 ms
98/100
30%
Value0.025
100/100
15%
Value4.7 s
80/100
10%
129 ms
118 ms
100 ms
77 ms
75 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 67% of them (26 requests) were addressed to the original Coronavirus.duke.edu, 10% (4 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Assets.styleguide.duke.edu. The less responsive or slowest element that took the longest time to load (333 ms) belongs to the original domain Coronavirus.duke.edu.
Page size can be reduced by 117.6 kB (5%)
2.4 MB
2.3 MB
In fact, the total size of Coronavirus.duke.edu main page is 2.4 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. 35% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 49.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. 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 49.1 kB or 77% of the original size.
Potential reduce by 59.2 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. Coronavirus Duke images are well optimized though.
Potential reduce by 941 B
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.
Potential reduce by 8.3 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.duke.edu needs all CSS files to be minified and compressed as it can save up to 8.3 kB or 17% of the original size.
Number of requests can be reduced by 19 (68%)
28
9
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coronavirus Duke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
coronavirus.duke.edu
129 ms
coronavirus.duke.edu
118 ms
js
100 ms
style.min.css
77 ms
duke-alertbar-public.css
75 ms
alert.css
217 ms
fonts.css
75 ms
genericons.min.css
80 ms
style.css
84 ms
style.css
80 ms
style.css
180 ms
frontend-gtag.min.js
183 ms
jquery.min.js
203 ms
jquery-migrate.min.js
183 ms
duke-alertbar-public.js
183 ms
doubletaptogo.min.js
189 ms
duke.css
218 ms
alert.html
212 ms
global.js
333 ms
new-tab.js
333 ms
accessibility.js
332 ms
css
34 ms
css
46 ms
css
23 ms
cropped-046818_few_003-2.jpg
124 ms
20200908_1styrdesigneng014.jpg
87 ms
20210217_covidtestpath006.jpg
88 ms
20210601_gardensopen001b.jpg
88 ms
20200820_masksstudysd041.jpg
89 ms
duke_wordmark-white.svg
102 ms
20200908_1styrdesigneng014.jpg
170 ms
20210217_covidtestpath006.jpg
198 ms
20210601_gardensopen001b.jpg
219 ms
20200820_masksstudysd041.jpg
225 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
26 ms
font
60 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
41 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
47 ms
duke-icons.ttf
105 ms
coronavirus.duke.edu accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Form elements do not have associated labels
coronavirus.duke.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
coronavirus.duke.edu SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coronavirus.duke.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.duke.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.
coronavirus.duke.edu
Open Graph data is detected on the main page of Coronavirus Duke. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: