Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

catalog.case.edu

Case and Affiliate Libraries Catalog

Page Load Speed

860 ms in total

First Response

140 ms

Resources Loaded

557 ms

Page Rendered

163 ms

catalog.case.edu screenshot

About Website

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

Visit catalog.case.edu

Key Findings

We analyzed Catalog.case.edu page load time and found that the first response time was 140 ms and then it took 720 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

catalog.case.edu performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

59/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

catalog.case.edu

140 ms

ProStyles.css

87 ms

styles.css

139 ms

elcontent.js

102 ms

common.js

156 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 77% of them (20 requests) were addressed to the original Catalog.case.edu, 8% (2 requests) were made to Translate.googleapis.com and 4% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (172 ms) belongs to the original domain Catalog.case.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.9 kB (54%)

Content Size

77.3 kB

After Optimization

35.5 kB

In fact, the total size of Catalog.case.edu main page is 77.3 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. 20% of websites need less resources to load. HTML takes 53.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 41.7 kB

  • Original 53.9 kB
  • After minification 49.0 kB
  • After compression 12.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 41.7 kB or 77% of the original size.

JavaScript Optimization

-1%

Potential reduce by 153 B

  • Original 19.9 kB
  • After minification 19.9 kB
  • After compression 19.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 70 B

  • Original 3.6 kB
  • After minification 3.6 kB
  • After compression 3.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. Catalog.case.edu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (44%)

Requests Now

25

After Optimization

14

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

Accessibility Review

catalog.case.edu accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

catalog.case.edu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

catalog.case.edu SEO score

82

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Catalog.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 Catalog.case.edu main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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