4.7 sec in total
259 ms
3.6 sec
865 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 259 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
dhvi.duke.edu performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value10.3 s
0/100
25%
Value16.1 s
0/100
10%
Value63,840 ms
0/100
30%
Value0.002
100/100
15%
Value81.8 s
0/100
10%
259 ms
156 ms
143 ms
202 ms
201 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 64% of them (63 requests) were addressed to the original Dhvi.duke.edu, 8% (8 requests) were made to Youtube.com and 7% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (852 ms) relates to the external source Alertbar.oit.duke.edu.
Page size can be reduced by 687.5 kB (51%)
1.3 MB
661.7 kB
In fact, the total size of Dhvi.duke.edu main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 713.8 kB which makes up the majority of the site volume.
Potential reduce by 37.8 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.3 kB, which is 16% 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 37.8 kB or 81% of the original size.
Potential reduce by 40.0 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 26.2 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 26.2 kB or 23% of the original size.
Potential reduce by 583.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 583.4 kB or 82% of the original size.
Number of requests can be reduced by 57 (65%)
88
31
The browser has sent 88 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 21 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
dhvi.duke.edu
259 ms
js
156 ms
ajax-progress.module.css
143 ms
align.module.css
202 ms
autocomplete-loading.module.css
201 ms
fieldgroup.module.css
272 ms
container-inline.module.css
272 ms
clearfix.module.css
270 ms
details.module.css
268 ms
hidden.module.css
274 ms
item-list.module.css
280 ms
js.module.css
398 ms
nowrap.module.css
397 ms
position-container.module.css
397 ms
progress.module.css
397 ms
reset-appearance.module.css
395 ms
resize.module.css
378 ms
sticky-header.module.css
418 ms
system-status-counter.css
418 ms
system-status-report-counters.css
414 ms
system-status-report-general-info.css
422 ms
tabledrag.module.css
418 ms
tablesort.module.css
412 ms
tree-child.module.css
516 ms
views.module.css
511 ms
oembed.formatter.css
512 ms
filter.caption.css
512 ms
filter.caption.css
509 ms
addtoany.css
481 ms
paragraphs.unpublished.css
513 ms
node.css
513 ms
breadcrumb.css
514 ms
bootstrap.min.css
275 ms
all.css
481 ms
messages-light.css
513 ms
style.css
550 ms
alert.css
460 ms
alert.html
472 ms
jquery.min.js
515 ms
drupalSettingsLoader.js
516 ms
drupal.js
518 ms
page.js
335 ms
bootstrap.bundle.min.js
335 ms
drupal.init.js
480 ms
picturefill.min.js
443 ms
addtoany.js
386 ms
analytics.js
184 ms
google_analytics.js
316 ms
popper.min.js
317 ms
bootstrap.min.js
424 ms
global.js
327 ms
collect
181 ms
dhvi-logo-white.svg
173 ms
home-slide.jpg
176 ms
dhvi-home-callout-1.jpeg
178 ms
dhvi-home-callout-2.jpeg
177 ms
dhvi-home-callout-3_0.jpeg
178 ms
hiv-icon.jpg
178 ms
09.12.2022-cryo.screens.png
180 ms
hivlab.02.web_.jpg
176 ms
dhvi-logo-blue.svg
174 ms
css2
90 ms
collect
800 ms
bg-alert-2.png
852 ms
pattern-dark.png
825 ms
oembed
819 ms
oembed
759 ms
oembed
754 ms
btn-alert_orange.png
684 ms
pattern-light.png
669 ms
fb-icon.svg
670 ms
twitter-icon.svg
685 ms
instagram-icon.svg
683 ms
linkedin-icon.svg
687 ms
home-slide.jpg
140 ms
eso.e18d3993.js
99 ms
sm.23.html
132 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
148 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff
229 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff
269 ms
fa-solid-900.woff
265 ms
fa-regular-400.woff
454 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RUAA.woff
347 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff
265 ms
oembed.frame.css
57 ms
E9gfeUV8YEM
224 ms
GezlHXfhCBA
189 ms
aL6FC3wBZ24
185 ms
www-player.css
118 ms
www-embed-player.js
116 ms
base.js
225 ms
fetch-polyfill.js
114 ms
ad_status.js
521 ms
WmYtwbYsvJeTDmsuIOmqRAOrqYQ4FznKv6GQB7SOtoo.js
529 ms
embed.js
131 ms
id
301 ms
KFOmCnqEu92Fr1Mu4mxM.woff
61 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
66 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
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: