962 ms in total
167 ms
616 ms
179 ms
Welcome to library.duke.edu homepage info - get ready to check Library Duke best content for United States right away, or after learning these important things about library.duke.edu
Visit library.duke.eduWe analyzed Library.duke.edu page load time and found that the first response time was 167 ms and then it took 795 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.
library.duke.edu performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value10.1 s
0/100
25%
Value7.2 s
30/100
10%
Value270 ms
82/100
30%
Value0.082
94/100
15%
Value10.8 s
22/100
10%
167 ms
74 ms
54 ms
40 ms
40 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 22% of them (17 requests) were addressed to the original Library.duke.edu, 58% (45 requests) were made to Libcms.oit.duke.edu and 8% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (199 ms) relates to the external source Blogs.library.duke.edu.
Page size can be reduced by 560.4 kB (60%)
931.6 kB
371.2 kB
In fact, the total size of Library.duke.edu main page is 931.6 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. 40% of websites need less resources to load. CSS take 326.9 kB which makes up the majority of the site volume.
Potential reduce by 67.7 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 67.7 kB or 84% of the original size.
Potential reduce by 16.6 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. Library Duke images are well optimized though.
Potential reduce by 203.0 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 203.0 kB or 73% of the original size.
Potential reduce by 273.2 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. Library.duke.edu needs all CSS files to be minified and compressed as it can save up to 273.2 kB or 84% of the original size.
Number of requests can be reduced by 46 (61%)
76
30
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Library 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 34 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
library.duke.edu
167 ms
jquery.trln.autocomplete.js
74 ms
jquery.trln.autosuggest.js
54 ms
trln_init.js
40 ms
DUKE_autosuggest_home.css
40 ms
jquery.gritter.css
39 ms
jquery.gritter.min.js
49 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
101 ms
css_aE6HmKcex--4gHeMkP4MUsGXdtR3PtbJ_uRF24-ev5U.css
105 ms
css_RyKEw8ebogxFgRsrNWP0khiyo7LVYRk8_1jyW0Qmdl4.css
104 ms
css_4R-soHnWxCZPeWNsqlctEi1KhYbdiatD0PACPrM8ff4.css
116 ms
css_7QX0ofF3CfPhhm6-PW7UoPK3ORcEa8CUuqVeCQ03AtY.css
109 ms
jquery.min.js
35 ms
jquery.once.js
106 ms
drupal.js
143 ms
jquery.cookie.js
140 ms
jquery.colorbox-min.js
141 ms
colorbox.js
141 ms
colorbox_style.js
142 ms
colorbox_load.js
143 ms
colorbox_inline.js
144 ms
jcaption.js
144 ms
themekey_redirect.js
145 ms
googleanalytics.js
146 ms
jquery.formalize.js
146 ms
omega-mediaqueries.js
147 ms
jquery.rwdImageMaps.min.js
148 ms
bootstrap.min.js
151 ms
init.js
149 ms
respond.min.js
149 ms
megamenu_plugins.js
149 ms
megamenu.js
162 ms
js_injector_13.js
164 ms
js_injector_20.js
164 ms
js_injector_31.js
177 ms
js_injector_32.js
165 ms
js_injector_45.js
176 ms
js_injector_47.js
166 ms
js_injector_65.js
175 ms
js_injector_91.js
181 ms
js_injector_93.js
187 ms
alert.html
68 ms
analytics.js
21 ms
collect
119 ms
collect
112 ms
collect
112 ms
collect
113 ms
collect
114 ms
library_logo_print.png
101 ms
palfrey600x360-260x180.jpg
199 ms
80x15.png
178 ms
ripolinuns600x360-260x180.jpg
153 ms
classof2020book600x360-260x180.jpg
157 ms
Women-at-Duke-Book-cover-260x180.jpg
160 ms
women_filmmakers600x360-260x180.jpg
143 ms
papyrus600x360-260x180.jpg
159 ms
bg-body-shadowBackground-1240.png
65 ms
bg-header-dukeblend-960-180b.jpg
62 ms
glyphicons-halflings-white.png
63 ms
discovery_icons_sprite.png
64 ms
dropdown-b.png
61 ms
arrowdrop-green-padded-sm.png
62 ms
library-background-blue.jpg
77 ms
search-arrow-light-v2b.png
79 ms
striped-grey.png
79 ms
quick_nav_icon_sprite.png
75 ms
footer_icon_sprite_2015.png
78 ms
logo.png
70 ms
find.jpg
68 ms
using-library-alumni.jpg
71 ms
research-student.jpg
68 ms
course-support.jpg
68 ms
libraries.jpg
68 ms
about.jpg
96 ms
devillogo-60pct-60.png
98 ms
dukelogo_vert_60pct_140.png
97 ms
css_2bMj_EayKQzvvtvPPwWhl9khtStacntuSBN0WbMJR30.css
24 ms
library.duke.edu accessibility score
library.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
library.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
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 Library.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 Library.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.
library.duke.edu
Open Graph description is not detected on the main page of Library 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: