2.7 sec in total
197 ms
2.3 sec
192 ms
Welcome to giving.case.edu homepage info - get ready to check Giving Case best content for United States right away, or after learning these important things about giving.case.edu
Visit giving.case.eduWe analyzed Giving.case.edu page load time and found that the first response time was 197 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
giving.case.edu performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value8.2 s
2/100
25%
Value7.4 s
28/100
10%
Value710 ms
42/100
30%
Value0
100/100
15%
Value13.0 s
13/100
10%
197 ms
233 ms
21 ms
23 ms
24 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 84% of them (32 requests) were addressed to the original Giving.case.edu, 8% (3 requests) were made to Securelb.imodules.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Case.edu.
Page size can be reduced by 795.7 kB (62%)
1.3 MB
485.1 kB
In fact, the total size of Giving.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. 60% of websites need less resources to load. Javascripts take 930.0 kB which makes up the majority of the site volume.
Potential reduce by 17.2 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 17.2 kB or 68% of the original size.
Potential reduce by 4.9 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. Giving Case images are well optimized though.
Potential reduce by 689.4 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 689.4 kB or 74% of the original size.
Potential reduce by 84.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. Giving.case.edu needs all CSS files to be minified and compressed as it can save up to 84.2 kB or 86% of the original size.
Number of requests can be reduced by 25 (74%)
34
9
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Giving 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 17 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
giving.case.edu
197 ms
index.aspx
233 ms
cwru_all.css
21 ms
style.css
23 ms
style_overwrite_global.css
24 ms
WebResource.axd
24 ms
WebResource.axd
26 ms
calendar.min.css
40 ms
jquery.fancybox.css
44 ms
cms_menubar_v2.min.css
42 ms
compiled.min.css
62 ms
WebResource.axd
61 ms
DefaultPageBundle.debug.js
61 ms
javascript.js
60 ms
enc-18167.js
65 ms
ScriptResource.axd
67 ms
ScriptResource.axd
64 ms
ScriptResource.axd
65 ms
ScriptResource.axd
63 ms
ScriptResource.axd
64 ms
ScriptResource.axd
88 ms
ScriptResource.axd
58 ms
ScriptResource.axd
60 ms
ScriptResource.axd
82 ms
ScriptResource.axd
81 ms
imodbase.css
59 ms
ga.js
149 ms
cwru-logo.png
39 ms
empty.gif
40 ms
campaign_banner.png
40 ms
TitilliumMaps26L003.otf
97 ms
TitilliumMaps26L001.otf
98 ms
__utm.gif
43 ms
orizontal_line.gif
38 ms
XdmSessionProvider.aspx
142 ms
1475 ms
imodules_common_1_0_2.js
11 ms
easyXDM.min.js
21 ms
giving.case.edu accessibility score
giving.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
Page has valid source maps
giving.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Giving.case.edu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Giving.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.
giving.case.edu
Open Graph description is not detected on the main page of Giving 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: