1.2 sec in total
84 ms
758 ms
384 ms
Visit history.duke.edu now to see the best up-to-date History Duke content for United States and also check out these interesting facts you probably never knew about history.duke.edu
Visit history.duke.eduWe analyzed History.duke.edu page load time and found that the first response time was 84 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
history.duke.edu performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value36.5 s
0/100
25%
Value5.7 s
50/100
10%
Value180 ms
92/100
30%
Value0.01
100/100
15%
Value9.5 s
30/100
10%
84 ms
137 ms
71 ms
67 ms
69 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 84% of them (41 requests) were addressed to the original History.duke.edu, 6% (3 requests) were made to Duke.edu and 4% (2 requests) were made to Alertbar.oit.duke.edu. The less responsive or slowest element that took the longest time to load (223 ms) belongs to the original domain History.duke.edu.
Page size can be reduced by 783.8 kB (55%)
1.4 MB
630.8 kB
In fact, the total size of History.duke.edu main page is 1.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. 45% of websites need less resources to load. Images take 498.6 kB which makes up the majority of the site volume.
Potential reduce by 57.9 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 57.9 kB or 80% of the original size.
Potential reduce by 22.9 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. History Duke images are well optimized though.
Potential reduce by 328.3 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 328.3 kB or 77% of the original size.
Potential reduce by 374.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. History.duke.edu needs all CSS files to be minified and compressed as it can save up to 374.8 kB or 90% of the original size.
Number of requests can be reduced by 14 (31%)
45
31
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of History 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 8 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
history.duke.edu
84 ms
alert.css
137 ms
css_9z683GZX4czRh45t5BXHjX9vrjU-dHy6XZ5A5XIF64A.css
71 ms
css_2vEBvmkaiBAGgM8Uipp4dVioT9xp3tlQU8Mp5gXBfoE.css
67 ms
css_HGqFjFyJ9aU2JTKpqjK9lU7sr8acyPBODUaYB-L5LYM.css
69 ms
css
68 ms
alert.css
83 ms
css_vcMcs_LQKGOejDHjMcVKsJz93xDGbkBbHpGoLWQnax4.css
69 ms
css_aVvOJTl9p45huutyNa_28IUP9EH43xTzAla2R1gh1x8.css
196 ms
css_pUTuF-U6kvdWUs69qNdMOINRsRWOcuTeHmrYgrHpV3M.css
68 ms
js_KPu2woAL851thW4-4xJE-0Ze4h3QvRYCeWPid7himXM.js
160 ms
js_obFUyTbqtcoGQtszVI46l1_oD927PzlDtlr_ilpYBqE.js
112 ms
js_FMIVJ0YijFtVI06NZz4Q3ulPWyMafumIJZRAD6kCczs.js
148 ms
js_LMoOINbOJS6mYRSlZTz6wYiAOwMl4jRw3fFNrshYSps.js
148 ms
js_YeTxCMb-HdHYHREAAEdRe2ARlUAvy6rqYW7g8dXFVP8.js
115 ms
alert.html
140 ms
js__JoTd9Oxwhsenh2V4oPwBopK_5ZERouXB3otHIn_MrM.js
161 ms
js_kVhMNj8le3n1K0vrEBIREUg5rXSZCEI5yxGR2pg3qxY.js
146 ms
alert.css
98 ms
alert.css
170 ms
analytics.js
75 ms
logo.png
211 ms
history-home-collage.jpg
223 ms
Petroski%20-%20The%20Road%20Taken.jpg
209 ms
marrow-of-tragedy-margaret-humphreys.200.299.s.png
211 ms
western-civilization-kristen-neuschel.200.256.s.jpg
206 ms
bull-city-survivor-simon-partner.200.300.s.jpg
208 ms
bonker-book-cover.200.302.s.jpg
211 ms
dubois-aftershocks-of-history-cover-1.200.301.s.jpg
211 ms
the-foundations-of-modern-terrorism-martin-miller.200.300.s.jpg
211 ms
the-making-of-romantic-love-william-reddy.200.301.s.jpg
212 ms
Roberts.jpg
212 ms
Ashton%20Merck_0.jpg
213 ms
history-books.jpg
214 ms
africahealth.jpg
215 ms
Hermes%20Trismegistus%201.jpg
215 ms
Dust-storm-Texas-1935.png
220 ms
ObamaandKid.jpg
216 ms
top-bg-banner.png
190 ms
search.png
190 ms
grey-brown-grid.gif
193 ms
grey-brown-lr-shadow.png
194 ms
band-black-gradient-rev.png
196 ms
band-grey-grid-fill.png
196 ms
band-black-gradient.png
196 ms
0680cd-left-shadow.png
197 ms
social-sprites.png
196 ms
collect
24 ms
ProximaNova-Reg-webfont.woff
51 ms
history.duke.edu accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
history.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
Browser errors were logged to the console
Page has valid source maps
history.duke.edu SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 History.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 History.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.
history.duke.edu
Open Graph description is not detected on the main page of History 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: