3.8 sec in total
105 ms
3.2 sec
475 ms
Click here to check amazing Research Case content for United States. Otherwise, check out these important facts you probably never knew about research.case.edu
Case Western Reserve University's Office of Research and Technology Management provides support to seek out grant funding, to facilitate industrial sponsorship, and to transfer university technol...
Visit research.case.eduWe analyzed Research.case.edu page load time and found that the first response time was 105 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
research.case.edu performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value16.1 s
0/100
25%
Value7.4 s
28/100
10%
Value1,060 ms
25/100
30%
Value0.045
99/100
15%
Value13.4 s
11/100
10%
105 ms
62 ms
313 ms
88 ms
315 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Research.case.edu, 62% (58 requests) were made to Case.edu and 5% (5 requests) were made to Case.blueconic.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Case.edu.
Page size can be reduced by 150.8 kB (12%)
1.3 MB
1.1 MB
In fact, the total size of Research.case.edu main page is 1.3 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. 70% of websites need less resources to load. Images take 933.0 kB which makes up the majority of the site volume.
Potential reduce by 71.1 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 15.2 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 71.1 kB or 81% of the original size.
Potential reduce by 49.0 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. Research Case images are well optimized though.
Potential reduce by 30.7 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 30.7 kB or 17% of the original size.
Potential reduce by 52 B
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. Research.case.edu has all CSS files already compressed.
Number of requests can be reduced by 67 (76%)
88
21
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Research Case. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
research.case.edu
105 ms
62 ms
313 ms
gtm.js
88 ms
css_2AsxVb3WiIW2ric4mQTjvdl3Hbr7GrczdHRlK2Lsu20.css
315 ms
css_cHfx9aoE0aVJGAVE9lb1uE3SWaEvbnK-JGXmniJGcdc.css
518 ms
jsonp.pl
582 ms
jquery-2.2.4.min.js
345 ms
globalize.min.js
318 ms
jquery.gcal_flow.js
317 ms
blazy.polyfill.min.js
313 ms
jquery.min.js
569 ms
underscore-min.js
638 ms
blazy.classlist.min.js
704 ms
blazy.promise.min.js
704 ms
blazy.raf.min.js
690 ms
drupalSettingsLoader.js
742 ms
drupal.js
906 ms
drupal.init.js
906 ms
debounce.js
911 ms
dblazy.min.js
912 ms
blazy.dataset.min.js
913 ms
blazy.viewport.min.js
1076 ms
blazy.dom.min.js
1257 ms
blazy.xlazy.min.js
1256 ms
blazy.observer.min.js
1255 ms
blazy.loading.min.js
1251 ms
blazy.webp.min.js
1251 ms
blazy.base.min.js
1314 ms
blazy.min.js
1369 ms
bio.min.js
1444 ms
slick.min.js
1444 ms
bio.media.min.js
1446 ms
blazy.drupal.min.js
1446 ms
blazy.load.min.js
1479 ms
drupal.bootstrap.js
1540 ms
attributes.js
1580 ms
theme.js
1591 ms
app.js
1598 ms
affix.js
1596 ms
alert.js
1637 ms
button.js
1696 ms
optimize.js
371 ms
1063.js
395 ms
insight.min.js
348 ms
conversion_async.js
390 ms
js
105 ms
carousel.js
1393 ms
collapse.js
1455 ms
dropdown.js
1391 ms
modal.js
1463 ms
css
191 ms
font-awesome.min.css
187 ms
tooltip.js
1243 ms
popover.js
1224 ms
analytics.js
39 ms
scrollspy.js
1221 ms
131 ms
case.edu.json
62 ms
collect
63 ms
tab.js
1187 ms
ieshim.js
40 ms
transition.js
1219 ms
popover.js
1164 ms
collect
47 ms
tooltip.js
1132 ms
logo-print.jpg
42 ms
cwru-logo.svg
157 ms
cwru-logo-formal.svg
165 ms
pin-icon.svg
164 ms
192 ms
fontawesome-webfont.woff
116 ms
slick.load.min.js
990 ms
datalayer.js
1035 ms
banner_1122x340_welcomeVPR.png
1414 ms
banner_1122x340_TTO-wires.jpg
1202 ms
ping
129 ms
ping
128 ms
case.js
171 ms
fbevents.js
141 ms
subfeature_344x172_industry.jpg
1086 ms
subfeature_344x172_faculty%26staff.jpg
979 ms
285202632763628
132 ms
130
152 ms
subfeature_344x172_students.jpg
877 ms
oiex-logo_web.png
837 ms
ResearchMattersFall2019.JPG
916 ms
2c6773d0b73a84980c84ed944d0ee5d1
44 ms
5f846a264115f82d9b419b85def8dce1
12 ms
LB-Zone-3
60 ms
18 ms
130
80 ms
events
200 ms
nr-1216.min.js
12 ms
research.case.edu accessibility score
research.case.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
research.case.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Research.case.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 Research.case.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.
research.case.edu
Open Graph description is not detected on the main page of Research Case. 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: