7.4 sec in total
669 ms
6.6 sec
225 ms
Click here to check amazing Digital U Dayton content for United States. Otherwise, check out these important facts you probably never knew about digital.udayton.edu
<p>eCommons, a service of the University Libraries, is a space for content produced by our diverse campus community. It is a permanent multimedia archive of the University's continuous pursuit of...
Visit digital.udayton.eduWe analyzed Digital.udayton.edu page load time and found that the first response time was 669 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
digital.udayton.edu performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value8.7 s
1/100
25%
Value14.6 s
1/100
10%
Value12,270 ms
0/100
30%
Value1.015
2/100
15%
Value22.2 s
1/100
10%
669 ms
14 ms
327 ms
332 ms
335 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Digital.udayton.edu, 12% (14 requests) were made to Maps.googleapis.com and 8% (9 requests) were made to Assets.bepress.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Assets.bepress.com.
Page size can be reduced by 737.0 kB (49%)
1.5 MB
777.6 kB
In fact, the total size of Digital.udayton.edu main page is 1.5 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. 65% of websites need less resources to load. Javascripts take 553.0 kB which makes up the majority of the site volume.
Potential reduce by 186.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. This page needs HTML code to be minified as it can gain 37.3 kB, which is 17% 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 186.9 kB or 83% of the original size.
Potential reduce by 20.8 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. Digital U Dayton images are well optimized though.
Potential reduce by 344.8 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 344.8 kB or 62% of the original size.
Potential reduce by 184.6 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. Digital.udayton.edu needs all CSS files to be minified and compressed as it can save up to 184.6 kB or 83% of the original size.
Number of requests can be reduced by 79 (72%)
110
31
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digital U Dayton. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
ecommons.udayton.edu
669 ms
yui-min.js
14 ms
ir-style.css
327 ms
ir-custom.css
332 ms
ir-local.css
335 ms
jsUtilities.js
336 ms
footnoteLinks.js
337 ms
dc-mobile-nav.js
472 ms
jquery.min.js
67 ms
mobile-scale.js
464 ms
fastclick.js
462 ms
scroll.js
468 ms
fixed-responsive-nav.js
482 ms
hide-nav.js
475 ms
jsapi
33 ms
gfslideshow.js
36 ms
d3.v2.js
1153 ms
sunburst.pack.js
819 ms
rdr.js
674 ms
floatbox.css
341 ms
floatbox.js
819 ms
gfslideshow.js
16 ms
bpbootstrap-20131105.pack.js
504 ms
ir-reset.css
350 ms
ir-layout.css
357 ms
ir-assets.css
507 ms
ir-left.css
515 ms
ir-submit.css
520 ms
ir-article.css
680 ms
ir-feed.css
682 ms
ir-network.css
686 ms
ir-adapt.css
692 ms
dc-mobile-nav.css
697 ms
grid.css
483 ms
ir-utilities.css
688 ms
ir-deprecate.css
342 ms
global-alert.css
336 ms
combo
11 ms
8e240588cf8cd3a028768d4294acd7d3.png
159 ms
3fa13ddb8a90123e1be67bcc75cc8ce2.png
166 ms
467c71ccc14bd8d24b0c8be98369a436.gif
170 ms
502c72b4789bbe4dc4a33c0940503efa.png
168 ms
a443ad2e19d6f1ccf9fcdd45570e66b9.gif
167 ms
1f4b26dfd7baa07fcd0b407410609a2f.gif
168 ms
e32fbf6c22085348bce98f778a27c2fe.gif
288 ms
fontawesome-webfont.woff
436 ms
responsivenav.ttf
318 ms
15 ms
default+en.css
3 ms
default+en.I.js
7 ms
5533975ef46621db91694fe087f77e91.gif
291 ms
orn.gif
292 ms
disciplines.json
424 ms
json
709 ms
e054f05274e6d9f93cbd3d3e47f89b9a.gif
369 ms
9887ef61d071562000d73d0fc018af21.gif
407 ms
b48bd7f463d2ee7d79c4e59181def21b.gif
411 ms
ga.js
14 ms
followable.css
451 ms
options.js
596 ms
__utm.gif
10 ms
DC_Logo_small.svg
165 ms
webservice-base-20131105.pack.js
175 ms
followable-20131105.pack.js
174 ms
combo
4 ms
combo
12 ms
ir-print.css
155 ms
combo
3 ms
combo
5 ms
followconfig.json
151 ms
index.html
161 ms
core_534.js
315 ms
readershipMap.css
148 ms
socket.io.js
636 ms
js
81 ms
readershipMap.embed.js
302 ms
tooltip_534.js
150 ms
analytics.js
23 ms
digitalcommons.png
178 ms
dc-embedsplash-09.png
1163 ms
Gfeeds
429 ms
common.js
31 ms
map.js
32 ms
us.png
213 ms
json
256 ms
fontawesome-webfont.woff
382 ms
util.js
21 ms
onion.js
41 ms
openhand_8_8.cur
46 ms
ViewportInfoService.GetViewportInfo
27 ms
stats.js
42 ms
controls.js
37 ms
blank.gif
196 ms
transparent.png
33 ms
vt
33 ms
css
91 ms
vt
57 ms
vt
58 ms
vt
57 ms
vt
63 ms
google4.png
44 ms
mapcnt6.png
40 ms
tmapctrl.png
54 ms
json
262 ms
AuthenticationService.Authenticate
28 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
32 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
40 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
43 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
48 ms
loader_black.gif
344 ms
pause.png
13 ms
fullsize.jpg
709 ms
pause.png
16 ms
179 ms
fullsize.jpg
589 ms
fullsize.jpg
927 ms
s12_r12_top.png
161 ms
s12_r12_right.png
200 ms
s12_r12_corner.png
176 ms
s12_r0_corner.png
174 ms
digital.udayton.edu accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
digital.udayton.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
digital.udayton.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 Digital.udayton.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 Digital.udayton.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.
digital.udayton.edu
Open Graph description is not detected on the main page of Digital U Dayton. 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: