Tools & Wizards About Us
case.edu screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

case.edu

Case Western Reserve University: One of the nation's best

Page Load Speed

1.9 sec in total

First Response

243 ms

Resources Loaded

1.2 sec

Page Rendered

542 ms

case.edu screenshot

About Website

Click here to check amazing Case content for United States. Otherwise, check out these important facts you probably never knew about case.edu

Explore Case Western Reserve University: the top-ranked school in Ohio and one of the best research universities in the U.S. Located in Cleveland, Ohio.

Visit case.edu

Key Findings

We analyzed Case.edu page load time and found that the first response time was 243 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

case.edu performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.24

52/100

15%

TTI (Time to Interactive)

Value27.7 s

0/100

10%

Network Requests Diagram

case.edu

243 ms

gtm.js

96 ms

analytics.js

21 ms

collect

17 ms

css

71 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 15% of them (5 requests) were addressed to the original Case.edu, 18% (6 requests) were made to Case.blueconic.net and 12% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (382 ms) relates to the external source Webapps.case.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 338.8 kB (62%)

Content Size

547.0 kB

After Optimization

208.2 kB

  • HTML
  • JavaScript

In fact, the total size of Case.edu main page is 547.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 436.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 81.0 kB

  • Original 110.9 kB
  • After minification 110.6 kB
  • After compression 29.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. 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 81.0 kB or 73% of the original size.

JavaScript Optimization

-59%

Potential reduce by 257.8 kB

  • Original 436.0 kB
  • After minification 436.0 kB
  • After compression 178.2 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 257.8 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (60%)

Requests Now

30

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 19 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

case.edu

case.edu

243 ms

gtm.js

gtm.js

96 ms

analytics.js

analytics.js

21 ms

collect

collect

17 ms

css

css

71 ms

add_banner

add_banner

382 ms

app-8e21b69dde4a7a30488d.js

app-8e21b69dde4a7a30488d.js

147 ms

framework-85c7f7f9a70052e81118.js

framework-85c7f7f9a70052e81118.js

304 ms

webpack-runtime-f5ce0c32383338c26c02.js

webpack-runtime-f5ce0c32383338c26c02.js

69 ms

cwru_logo_primary_white.svg

cwru_logo_primary_white.svg

80 ms

cwru_acronym_white.svg

cwru_acronym_white.svg

78 ms

js

js

99 ms

linkid.js

linkid.js

43 ms

insight.min.js

insight.min.js

280 ms

destination

destination

193 ms

hotjar-2954518.js

hotjar-2954518.js

278 ms

ping

ping

57 ms

ping

ping

186 ms

case.js

case.js

82 ms

fbevents.js

fbevents.js

57 ms

adp.min.js

adp.min.js

186 ms

collect

collect

47 ms

collect

collect

152 ms

1024

1024

103 ms

mtc.js

mtc.js

355 ms

pattern-443ea79283f04c32791ec68cb70e07df.svg

pattern-443ea79283f04c32791ec68cb70e07df.svg

80 ms

modules.404c8789d11e259a4872.js

modules.404c8789d11e259a4872.js

33 ms

insight_tag_errors.gif

insight_tag_errors.gif

227 ms

58bc76974374e19a1aa44afece8fc0b9

58bc76974374e19a1aa44afece8fc0b9

8 ms

78bea229f65f26e759b44c401b3dac17

78bea229f65f26e759b44c401b3dac17

7 ms

LB-Zone-3

LB-Zone-3

14 ms

1024

1024

11 ms

cs

cs

5 ms

Accessibility Review

case.edu accessibility score

93

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Form elements do not have associated labels

Best Practices

case.edu best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

case.edu SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.

Social Sharing Optimization

case.edu

Open Graph description is not detected on the main page of 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: