5.1 sec in total
188 ms
4.4 sec
561 ms
Visit dhvi.duke.edu now to see the best up-to-date Dhvi Duke content for United States and also check out these interesting facts you probably never knew about dhvi.duke.edu
Visit dhvi.duke.eduWe analyzed Dhvi.duke.edu page load time and found that the first response time was 188 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
dhvi.duke.edu performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value13.0 s
0/100
25%
Value20.3 s
0/100
10%
Value8,860 ms
0/100
30%
Value0.212
59/100
15%
Value32.1 s
0/100
10%
188 ms
33 ms
63 ms
99 ms
99 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 68% of them (67 requests) were addressed to the original Dhvi.duke.edu, 9% (9 requests) were made to Youtube.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Dhvi.duke.edu.
Page size can be reduced by 518.2 kB (14%)
3.7 MB
3.1 MB
In fact, the total size of Dhvi.duke.edu main page is 3.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. 70% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 46.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 7.7 kB, which is 14% 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 46.1 kB or 82% of the original size.
Potential reduce by 195.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. Dhvi Duke images are well optimized though.
Potential reduce by 3.5 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.
Potential reduce by 273.4 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. Dhvi.duke.edu needs all CSS files to be minified and compressed as it can save up to 273.4 kB or 66% of the original size.
Number of requests can be reduced by 57 (64%)
89
32
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dhvi 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 20 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.
dhvi.duke.edu
188 ms
google_tag.script.js
33 ms
ajax-progress.module.css
63 ms
align.module.css
99 ms
autocomplete-loading.module.css
99 ms
fieldgroup.module.css
99 ms
container-inline.module.css
98 ms
clearfix.module.css
286 ms
details.module.css
286 ms
hidden.module.css
124 ms
item-list.module.css
124 ms
js.module.css
124 ms
nowrap.module.css
186 ms
position-container.module.css
185 ms
progress.module.css
186 ms
reset-appearance.module.css
186 ms
resize.module.css
211 ms
sticky-header.module.css
384 ms
system-status-counter.css
285 ms
system-status-report-counters.css
485 ms
system-status-report-general-info.css
238 ms
tabledrag.module.css
486 ms
tablesort.module.css
484 ms
tree-child.module.css
384 ms
views.module.css
310 ms
oembed.formatter.css
483 ms
filter.caption.css
485 ms
filter.caption.css
483 ms
addtoany.css
683 ms
paragraphs.unpublished.css
582 ms
node.css
582 ms
mb.YTPlayer.min.css
583 ms
breadcrumb.css
584 ms
bootstrap.min.css
33 ms
all.css
42 ms
messages-light.css
781 ms
style.css
2486 ms
alert.css
176 ms
alert.html
179 ms
jquery.min.js
1202 ms
page.js
61 ms
bootstrap.bundle.min.js
43 ms
drupalSettingsLoader.js
605 ms
drupal.js
584 ms
drupal.init.js
624 ms
addtoany.js
588 ms
popper.min.js
989 ms
bootstrap.min.js
888 ms
global.js
787 ms
mb.YTPlayer.min.js
1163 ms
youtube.js
1062 ms
css2
38 ms
dhvi-logo-white.svg
184 ms
postdoccareerbanner189in.png
1426 ms
programsandcentersgraphic.png
135 ms
makeadifferencegraphic.png
200 ms
opportunityawaitsgraphic.png
231 ms
Bart%20Haynes%20USE.jpg
183 ms
faucinewsphoto.jpg
345 ms
kshitijwaghphoto.jpg
268 ms
danielwrapp-cropped2.png
340 ms
ln2-freezers-accessioningunit-freezerfarm.png
508 ms
dhvi-logo-blue.svg
444 ms
pattern-dark.png
429 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
118 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
119 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
182 ms
oembed
460 ms
oembed
457 ms
oembed
889 ms
oembed
563 ms
oembed
890 ms
fb-icon.svg
477 ms
twitter-icon.svg
607 ms
instagram-icon.svg
608 ms
linkedin-icon.svg
608 ms
fa-solid-900.woff
84 ms
fa-regular-400.woff
130 ms
gtm.js
115 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf
79 ms
sm.25.html
59 ms
eso.D0Uc7kY6.js
77 ms
oembed.frame.css
337 ms
H_-ksKxCXKk
126 ms
kdgLGwd7Tr8
495 ms
aL6FC3wBZ24
432 ms
www-player.css
5 ms
www-embed-player.js
36 ms
base.js
65 ms
ad_status.js
590 ms
Xal8RkuvyCiU6W_GOvwH_DuhE1BN-1S9Ky9af2kVVy4.js
539 ms
embed.js
211 ms
E9gfeUV8YEM
372 ms
GezlHXfhCBA
370 ms
id
279 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
231 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
231 ms
id
85 ms
dhvi.duke.edu accessibility score
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
ARIA IDs are not unique
dhvi.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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
dhvi.duke.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Dhvi.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 Dhvi.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.
dhvi.duke.edu
Open Graph description is not detected on the main page of Dhvi Duke. 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: