2.8 sec in total
140 ms
1.2 sec
1.5 sec
Click here to check amazing Duke content for United States. Otherwise, check out these important facts you probably never knew about duke.edu
Visit duke.eduWe analyzed Duke.edu page load time and found that the first response time was 140 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
duke.edu performance score
name
value
score
weighting
Value2.2 s
76/100
10%
Value12.9 s
0/100
25%
Value5.8 s
49/100
10%
Value400 ms
68/100
30%
Value0.043
99/100
15%
Value10.0 s
26/100
10%
140 ms
29 ms
33 ms
221 ms
313 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 57% of them (20 requests) were addressed to the original Duke.edu, 9% (3 requests) were made to I1.ytimg.com and 6% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (753 ms) belongs to the original domain Duke.edu.
Page size can be reduced by 261.5 kB (6%)
4.1 MB
3.9 MB
In fact, the total size of Duke.edu main page is 4.1 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. 50% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 75.0 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 75.0 kB or 77% of the original size.
Potential reduce by 186.3 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. Duke images are well optimized though.
Potential reduce by 46 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 82 B
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. Duke.edu has all CSS files already compressed.
Number of requests can be reduced by 4 (12%)
34
30
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 5 to 1 for JavaScripts and as a result speed up the page load time.
duke.edu
140 ms
cookieconsent.min.css
29 ms
cookieconsent.min.js
33 ms
alert.html
221 ms
duke.js
313 ms
gtm.js
62 ms
chapel-hat-toss2024.jpg
451 ms
mqdefault.jpg
35 ms
441264444_832340935419730_8860894116847027358_n.jpg
73 ms
441093199_1581921125986377_2864786036850208735_n.jpg
34 ms
440899428_809933867136770_8234337904752849074_n.jpg
70 ms
441238370_1172395633952282_5703095120168784373_n.jpg
72 ms
mqdefault.jpg
34 ms
duke-centennial-white.svg
171 ms
chapel-hat-toss2024.jpg
370 ms
duketoday-logo.svg
173 ms
2xfitz_hero.jpg
284 ms
1x1.png
177 ms
fencing-20150219164439-r-q100-m1535739917.png
361 ms
chapel-fall-r-q100-m1699555863.png
486 ms
home-page-highlight-lucky-strike-r-q100-m1652986150.png
485 ms
dukeeduwestcampusfooter-r-q100-m1509537650.jpg
753 ms
dukelogo_white.svg
443 ms
js
90 ms
ga.js
31 ms
__utm.gif
117 ms
sddefault.jpg
31 ms
anti-racism-tile.jpg
134 ms
sustainability-tile.jpg
161 ms
arts-tile.jpg
240 ms
research-tile.jpg
253 ms
coronavirus-respsonse-tile.jpg
293 ms
for-the-media-tile.jpg
295 ms
fitz_hero.jpg
288 ms
duke.css
99 ms
duke.edu accessibility score
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
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
Missing source maps for large first-party JavaScript
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 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 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.
duke.edu
Open Graph description is not detected on the main page of 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: