970 ms in total
143 ms
674 ms
153 ms
Welcome to sites.duke.edu homepage info - get ready to check Sites Duke best content for United States right away, or after learning these important things about sites.duke.edu
Visit sites.duke.eduWe analyzed Sites.duke.edu page load time and found that the first response time was 143 ms and then it took 827 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
sites.duke.edu performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value5.1 s
25/100
25%
Value3.2 s
91/100
10%
Value190 ms
91/100
30%
Value0.004
100/100
15%
Value5.0 s
76/100
10%
143 ms
107 ms
91 ms
185 ms
184 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 74% of them (28 requests) were addressed to the original Sites.duke.edu, 18% (7 requests) were made to Brandbar.oit.duke.edu and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (328 ms) belongs to the original domain Sites.duke.edu.
Page size can be reduced by 255.6 kB (39%)
650.7 kB
395.1 kB
In fact, the total size of Sites.duke.edu main page is 650.7 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. 25% of websites need less resources to load. Images take 303.2 kB which makes up the majority of the site volume.
Potential reduce by 17.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 2.7 kB, which is 11% 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 17.4 kB or 73% of the original size.
Potential reduce by 21.4 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. Sites Duke images are well optimized though.
Potential reduce by 170.9 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 170.9 kB or 64% of the original size.
Potential reduce by 45.8 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. Sites.duke.edu needs all CSS files to be minified and compressed as it can save up to 45.8 kB or 80% of the original size.
Number of requests can be reduced by 19 (51%)
37
18
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sites 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 14 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
sites.duke.edu
143 ms
style.css
107 ms
media-queries.css
91 ms
screen-globalHeader-nologo.css
185 ms
footer.css
184 ms
light_style.css
43 ms
polls-css.css
39 ms
addtoany.min.css
79 ms
jquery.js
155 ms
jquery-migrate.min.js
93 ms
fdfootnotes.js
83 ms
bar.html
222 ms
modernizr-1.7.min.js
115 ms
css_browser_selector.js
101 ms
script.js
122 ms
respond.min.js
116 ms
globalHeader.js
248 ms
collapse.js
144 ms
polls-js.js
138 ms
wp-embed.min.js
246 ms
wp-emoji-release.min.js
94 ms
bg-body-shadowBackground.png
70 ms
logo.png
68 ms
foodatduke-featured.png
328 ms
GlobalMedatDuke-GROW.jpg
272 ms
add_icon-25x24.png
273 ms
IHSS-featured.png
310 ms
bg-header.jpg
157 ms
bg-search-field.png
55 ms
btn-search-go.png
58 ms
background-nav.gif
156 ms
bg-header-global-nologo.jpg
154 ms
logo-print.png
48 ms
btn-headerGlobal.png
48 ms
logo-subFooter.png
148 ms
ga.js
46 ms
page.js
81 ms
__utm.gif
14 ms
sites.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-*] attributes do not match their roles
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
sites.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
sites.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sites.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 Sites.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.
sites.duke.edu
Open Graph description is not detected on the main page of Sites 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: