2.7 sec in total
132 ms
2.3 sec
175 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 132 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
digital.udayton.edu performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value11.8 s
0/100
25%
Value7.7 s
25/100
10%
Value870 ms
33/100
30%
Value0.947
3/100
15%
Value12.1 s
16/100
10%
132 ms
273 ms
55 ms
49 ms
51 ms
Our browser made a total of 145 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, 34% (50 requests) were made to Ecommons.udayton.edu and 4% (6 requests) were made to Assets.bepress.com. The less responsive or slowest element that took the longest time to load (495 ms) relates to the external source Resources.bepress.com.
Page size can be reduced by 450.5 kB (39%)
1.2 MB
706.5 kB
In fact, the total size of Digital.udayton.edu main page is 1.2 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. HTML takes 428.1 kB which makes up the majority of the site volume.
Potential reduce by 353.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. This page needs HTML code to be minified as it can gain 62.3 kB, which is 15% 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 353.6 kB or 83% of the original size.
Potential reduce by 16.2 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 49.9 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 49.9 kB or 12% of the original size.
Potential reduce by 30.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. Digital.udayton.edu needs all CSS files to be minified and compressed as it can save up to 30.8 kB or 41% of the original size.
Number of requests can be reduced by 115 (85%)
135
20
The browser has sent 135 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 90 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
ecommons.udayton.edu
132 ms
ecommons.udayton.edu
273 ms
yui-min.js
55 ms
jquery.min.js
49 ms
launch-d525bb0064d8.min.js
51 ms
nr_browser_production.js
110 ms
ir-style.css
123 ms
ir-custom.css
189 ms
ir-local.css
247 ms
jsUtilities.js
271 ms
footnoteLinks.js
296 ms
dc-responsive-nav.js
278 ms
dc-mobile-nav.js
277 ms
rdr.js
298 ms
d3.v2.js
404 ms
sunburst.pack.js
303 ms
floatbox.css
302 ms
floatbox.js
347 ms
js
116 ms
bpbootstrap-20160726.pack.js
348 ms
AppMeasurement.min.js
29 ms
otSDKStub.js
45 ms
ir-reset.css
230 ms
ir-layout.css
236 ms
ir-assets.css
245 ms
ir-left.css
272 ms
ir-submit.css
280 ms
ir-article.css
282 ms
ir-feed.css
296 ms
ir-network.css
304 ms
ir-adapt.css
333 ms
dc-mobile-nav.css
343 ms
243605e3-552c-483b-b139-00f1727d7599-test.json
105 ms
css
41 ms
location
51 ms
otBannerSdk.js
22 ms
grid.css
109 ms
ir-utilities.css
112 ms
ir-deprecate.css
113 ms
global-alert.css
85 ms
css
21 ms
css
26 ms
ir-print.css
159 ms
oop-min.js
128 ms
event-custom-base-min.js
132 ms
dom-core-min.js
131 ms
dom-base-min.js
180 ms
selector-native-min.js
138 ms
selector-min.js
158 ms
node-core-min.js
138 ms
node-base-min.js
156 ms
event-base-min.js
156 ms
event-delegate-min.js
178 ms
node-event-delegate-min.js
178 ms
pluginhost-base-min.js
177 ms
pluginhost-config-min.js
178 ms
node-pluginhost-min.js
177 ms
dom-style-min.js
179 ms
dom-screen-min.js
256 ms
node-screen-min.js
250 ms
node-style-min.js
178 ms
cookie-min.js
255 ms
3c3f0656392b58c852c0c4eb80d8c6bc.png
274 ms
5fc2b27a17b7b6e258fcd1cfd3876d7c.gif
275 ms
8e240588cf8cd3a028768d4294acd7d3.png
274 ms
881593bff7112e6ae4601147398699c0.png
304 ms
2ed18949443cea4d599bd47e11f8b451.png
274 ms
c3379f67506ba3a30e49436246dddea8.gif
275 ms
cf1e60b6ab93bff127a9eca3244a962c.gif
252 ms
f4f27c3587ddda7a52a9991485f1023b.gif
254 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8JoA.woff
113 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoA.woff
191 ms
fontawesome-webfont.woff
442 ms
responsivenav.ttf
256 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff
183 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xo.woff
184 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xo.woff
183 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZqFCTx8cM.woff
184 ms
json
495 ms
disciplines.json
253 ms
a766e64935ecd7e9ec25aef5cdf5a8f6.gif
170 ms
fbOptions.js
192 ms
followable.css
220 ms
core.js
138 ms
DC_Logo_small.svg
86 ms
event-custom-complex-min.js
53 ms
event-synthetic-min.js
54 ms
event-mousewheel-min.js
54 ms
event-mouseenter-min.js
51 ms
event-key-min.js
53 ms
event-focus-min.js
51 ms
event-resize-min.js
53 ms
event-hover-min.js
55 ms
event-outside-min.js
53 ms
event-touch-min.js
54 ms
event-move-min.js
53 ms
event-flick-min.js
55 ms
event-valuechange-min.js
54 ms
webservice-base-20131105.pack.js
79 ms
followable-20160726.pack.js
80 ms
blank.gif
64 ms
wait.gif
64 ms
widget-base.css
26 ms
widget-stack.css
17 ms
overlay.css
16 ms
index.html
66 ms
querystring-stringify-simple-min.js
23 ms
io-base-min.js
13 ms
json-parse-min.js
22 ms
json-stringify-min.js
10 ms
jsonp-min.js
11 ms
attribute-core-min.js
14 ms
attribute-events-min.js
22 ms
attribute-extras-min.js
29 ms
attribute-base-min.js
27 ms
attribute-complex-min.js
23 ms
base-core-min.js
34 ms
base-base-min.js
36 ms
base-pluginhost-min.js
32 ms
classnamemanager-min.js
42 ms
widget-base-min.js
42 ms
widget-htmlparser-min.js
42 ms
widget-skin-min.js
42 ms
widget-uievents-min.js
50 ms
base-build-min.js
51 ms
widget-stdmod-min.js
49 ms
widget-position-min.js
51 ms
widget-position-align-min.js
55 ms
widget-stack-min.js
52 ms
widget-position-constrain-min.js
59 ms
overlay-min.js
67 ms
anim-base-min.js
65 ms
plugin-min.js
62 ms
widget-anim-min.js
63 ms
substitute-min.js
67 ms
querystring-parse-simple-min.js
70 ms
dump-min.js
75 ms
readershipMap.css
67 ms
socket.io.js
266 ms
js
71 ms
readershipMap.embed.js
68 ms
followconfig.json
62 ms
analytics.js
29 ms
dc-embedsplash-09.png
311 ms
nr-spa-1216.min.js
25 ms
digital.udayton.edu accessibility score
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
Browser errors were logged to the console
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: