1.2 sec in total
176 ms
853 ms
140 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 176 ms and then it took 993 ms 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.
library.duke.edu performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value9.9 s
0/100
25%
Value6.4 s
40/100
10%
Value380 ms
70/100
30%
Value0.234
53/100
15%
Value10.5 s
24/100
10%
176 ms
29 ms
89 ms
110 ms
112 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 55% of them (30 requests) were addressed to the original Library.duke.edu, 13% (7 requests) were made to Fonts.gstatic.com and 11% (6 requests) were made to Blogs.library.duke.edu. The less responsive or slowest element that took the longest time to load (283 ms) relates to the external source Blogs.library.duke.edu.
Page size can be reduced by 75.6 kB (5%)
1.6 MB
1.5 MB
In fact, the total size of Library.duke.edu main page is 1.6 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 931.6 kB which makes up the majority of the site volume.
Potential reduce by 53.6 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 53.6 kB or 81% of the original size.
Potential reduce by 20.7 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 91 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 1.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 has all CSS files already compressed.
Number of requests can be reduced by 15 (34%)
44
29
The browser has sent 44 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 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
library.duke.edu
176 ms
css_g4w8g77BNWLStL60t3U3Fxxlf68U3RcrfId9VdgFouk.css
29 ms
css_CQcE0y99jlHhgvFPijCEEDAXuKMWfWfItqYhXkLJZg4.css
89 ms
css__ZOUihsxRWTcrNJQUZPEnxw002Kcwhw30jqi-I_2BqE.css
110 ms
js_R58HD4-8iB38rS_QGLFRN4DQyGE3ZVm54hSZWvcbTcI.js
112 ms
matomo_tracking-e5d5c75cf518bf406481f121af6a0e6e.js
111 ms
js_NakFScdT9zlXc2bSAQl4Fx7__0hQs1kaOVbsIG2TItA.js
215 ms
alert.css
164 ms
alert.html
167 ms
js_WVEw5vHdKs1xWREqamAmNHbj9Aqq_-CxLuSzaN4khQU.js
110 ms
load-masthead.js.php
115 ms
js_qAi46ENzUzFj9Gx0XxX0Wv6sBVwvo4vjMjE5oC7UFJM.js
116 ms
css
39 ms
css2
55 ms
matomo.js
224 ms
GeoRef-Dont-Miss-Database-600x360-1.jpg
239 ms
dukeref@chat.libraryh3lp.com
213 ms
80x15.png
140 ms
Lilly-Renovation-Update-May-8-2024.jpg
260 ms
LMBC-Don-Quixote-600x360-1.jpg
257 ms
Daniel-Walker-Video-Duke-Workday-600x360-1.jpg
283 ms
Open-Monograph-Award-600x360-1.jpg
259 ms
Lilly-Renovation-Exterior-Rendering-600x360-1.jpg
257 ms
search-222.png
39 ms
user-94AFED-17x16.png
39 ms
comment-94AFED-18x15.png
39 ms
logo.png
34 ms
search-resources-back.jpg
38 ms
devillogo-60pct-60.png
38 ms
dukelogo_vert_60pct_140.png
91 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3aPw.ttf
48 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
101 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkA.ttf
137 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf
152 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
152 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkA.ttf
153 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
152 ms
libraryh3lp.js
143 ms
fa-solid-900.woff
104 ms
fa-regular-400.woff
51 ms
fa-brands-400.woff
103 ms
masthead-responsive.css
50 ms
matomo.php
122 ms
available
3 ms
libraryh3lp_jid.js
3 ms
embedded.js
8 ms
find.jpg
25 ms
using-library-alumni.jpg
27 ms
research-student.jpg
25 ms
course-support-textbooks.jpg
26 ms
libraries.jpg
24 ms
about.jpg
26 ms
search-222.png
30 ms
user-94AFED-17x16.png
47 ms
comment-94AFED-18x15.png
46 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: