Tools & Wizards About Us

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

research.case.edu

Office of Research and Technology Management | Case Western Reserve University

Page Load Speed

2.3 sec in total

First Response

109 ms

Resources Loaded

1.4 sec

Page Rendered

752 ms

About Website

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.edu

Key Findings

We analyzed Research.case.edu page load time and found that the first response time was 109 ms and then it took 2.1 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.

Performance Metrics

research.case.edu performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value2,550 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

research.case.edu

109 ms

53 ms

gtm.js

137 ms

node.module.css

20 ms

entity-form.css

27 ms

Our browser made a total of 176 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, 81% (143 requests) were made to Case.edu and 9% (16 requests) were made to Dudbm6bcnmy8e.cloudfront.net. The less responsive or slowest element that took the longest time to load (319 ms) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.2 kB (16%)

Content Size

1.2 MB

After Optimization

980.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Research.case.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. Only a small number of websites need less resources to load. Images take 468.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 101.0 kB

  • Original 118.6 kB
  • After minification 101.4 kB
  • After compression 17.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 17.2 kB, which is 14% 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 101.0 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 5.6 kB

  • Original 468.5 kB
  • After minification 462.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. Research Case images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 51.7 kB

  • Original 403.9 kB
  • After minification 400.3 kB
  • After compression 352.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 51.7 kB or 13% of the original size.

CSS Optimization

-19%

Potential reduce by 34.9 kB

  • Original 182.1 kB
  • After minification 180.2 kB
  • After compression 147.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. Research.case.edu needs all CSS files to be minified and compressed as it can save up to 34.9 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 140 (86%)

Requests Now

162

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 162 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 99 to 1 for JavaScripts and from 43 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

research.case.edu accessibility score

100

Accessibility Issues

Best Practices

research.case.edu best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

research.case.edu SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 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.

Social Sharing Optimization

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: