11.2 sec in total
823 ms
10.1 sec
279 ms
Visit scholarworks.wmich.edu now to see the best up-to-date Scholar Works Wmich content for United States and also check out these interesting facts you probably never knew about scholarworks.wmich.edu
A digital showcase of the research, scholarly and creative output of the faculty, students and staff of Western Michigan University community. The ScholarWorks repository is administered by WMU Librar...
Visit scholarworks.wmich.eduWe analyzed Scholarworks.wmich.edu page load time and found that the first response time was 823 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
scholarworks.wmich.edu performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value15.6 s
0/100
25%
Value8.8 s
15/100
10%
Value1,150 ms
22/100
30%
Value0.425
22/100
15%
Value14.1 s
9/100
10%
823 ms
9 ms
472 ms
470 ms
477 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 57% of them (76 requests) were addressed to the original Scholarworks.wmich.edu, 11% (14 requests) were made to Maps.googleapis.com and 7% (9 requests) were made to Assets.bepress.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Scholarworks.wmich.edu.
Page size can be reduced by 862.6 kB (43%)
2.0 MB
1.1 MB
In fact, the total size of Scholarworks.wmich.edu main page is 2.0 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. Images take 847.8 kB which makes up the majority of the site volume.
Potential reduce by 263.8 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 263.8 kB or 81% of the original size.
Potential reduce by 37.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. Scholar Works Wmich images are well optimized though.
Potential reduce by 376.6 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 376.6 kB or 64% of the original size.
Potential reduce by 184.5 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. Scholarworks.wmich.edu needs all CSS files to be minified and compressed as it can save up to 184.5 kB or 83% of the original size.
Number of requests can be reduced by 81 (65%)
124
43
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Scholar Works Wmich. 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.
scholarworks.wmich.edu
823 ms
yui-min.js
9 ms
ir-style.css
472 ms
ir-custom.css
470 ms
ir-local.css
477 ms
jsUtilities.js
477 ms
footnoteLinks.js
477 ms
dc-mobile-nav.js
709 ms
jquery.min.js
91 ms
mobile-scale.js
693 ms
fastclick.js
937 ms
scroll.js
700 ms
fixed-responsive-nav.js
706 ms
hide-nav.js
706 ms
jsapi
67 ms
gfslideshow.js
83 ms
rdr.js
979 ms
d3.v2.js
2342 ms
sunburst.pack.js
1182 ms
floatbox.css
524 ms
floatbox.js
1181 ms
bpbootstrap-20131105.pack.js
727 ms
ir-reset.css
478 ms
ir-layout.css
709 ms
ir-assets.css
719 ms
ir-left.css
720 ms
ir-submit.css
946 ms
ir-article.css
950 ms
ir-feed.css
951 ms
ir-network.css
957 ms
ir-adapt.css
958 ms
dc-mobile-nav.css
1180 ms
grid.css
472 ms
ir-utilities.css
478 ms
ir-deprecate.css
475 ms
global-alert.css
250 ms
combo
13 ms
13d782736d608e106487e396590f2152.gif
249 ms
8e240588cf8cd3a028768d4294acd7d3.png
491 ms
7c4b44c065f03e023f765c484b418dec.gif
1039 ms
9639085661102e8df635f9bb192b5246.jpg
2414 ms
56850f631b444beb579be5b3bacd46a5.gif
254 ms
cf1e60b6ab93bff127a9eca3244a962c.gif
450 ms
7e14e8896cf3cc98444f5ee9b3d92978.gif
496 ms
fontawesome-webfont.woff
2401 ms
responsivenav.ttf
692 ms
19 ms
default+en.css
4 ms
default+en.I.js
7 ms
json
1048 ms
790c3765673462938c34b5a742ed33bf.gif
697 ms
disciplines.json
948 ms
332d0229ce2845c2fad5ad57f48c4136.gif
299 ms
81befb428dd49214da5c8d3582ad2801.gif
338 ms
analytics.js
23 ms
followable.css
526 ms
options.js
557 ms
collect
12 ms
collect
21 ms
index.html
232 ms
webservice-base-20131105.pack.js
230 ms
followable-20131105.pack.js
231 ms
combo
4 ms
readershipMap.css
222 ms
socket.io.js
984 ms
js
81 ms
readershipMap.embed.js
441 ms
core_534.js
714 ms
combo
3 ms
combo
12 ms
combo
4 ms
followconfig.json
240 ms
DC_Logo_small.svg
235 ms
tooltip_534.js
258 ms
analytics.js
57 ms
digitalcommons.png
220 ms
dc-embedsplash-09.png
2193 ms
ir-print.css
247 ms
Gfeeds
289 ms
common.js
73 ms
map.js
94 ms
us.png
266 ms
json
1525 ms
fontawesome-webfont.woff
1044 ms
blank.gif
294 ms
util.js
27 ms
onion.js
26 ms
openhand_8_8.cur
127 ms
ViewportInfoService.GetViewportInfo
103 ms
stats.js
50 ms
controls.js
99 ms
pause.png
85 ms
transparent.png
55 ms
css
251 ms
pause.png
307 ms
preview.jpg
571 ms
vt
141 ms
vt
231 ms
google4.png
231 ms
vt
106 ms
vt
278 ms
vt
200 ms
mapcnt6.png
202 ms
preview.jpg
772 ms
preview.jpg
2391 ms
preview.jpg
771 ms
preview.jpg
309 ms
tmapctrl.png
117 ms
loader_black.gif
294 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
114 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
107 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
151 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
153 ms
json
808 ms
AuthenticationService.Authenticate
37 ms
s12_r12_top.png
255 ms
preview.jpg
729 ms
preview.jpg
507 ms
preview.jpg
694 ms
preview.jpg
694 ms
s12_r12_right.png
250 ms
preview.jpg
488 ms
preview.jpg
525 ms
preview.jpg
904 ms
preview.jpg
663 ms
256 ms
s12_r12_corner.png
267 ms
preview.jpg
513 ms
preview.jpg
732 ms
preview.jpg
253 ms
s12_r0_corner.png
378 ms
s12_r12_bottom.png
239 ms
s12_r12_left.png
271 ms
scholarworks.wmich.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.
scholarworks.wmich.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
scholarworks.wmich.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 Scholarworks.wmich.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 Scholarworks.wmich.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.
scholarworks.wmich.edu
Open Graph description is not detected on the main page of Scholar Works Wmich. 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: