Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ecases.us

eCases - All United States Court Cases Online

Page Load Speed

818 ms in total

First Response

116 ms

Resources Loaded

509 ms

Page Rendered

193 ms

ecases.us screenshot

About Website

Welcome to ecases.us homepage info - get ready to check ECases best content for United States right away, or after learning these important things about ecases.us

eCase is one of the world's most informative online sources for cases from different courts in United States' Federal and all states, and court cases will be updated continually - legalzone

Visit ecases.us

Key Findings

We analyzed Ecases.us page load time and found that the first response time was 116 ms and then it took 702 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

ecases.us performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.635

9/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

ecases.us

116 ms

city_master.css

76 ms

jquery-ui.min.css

98 ms

jquery-1.10.2.min.js

139 ms

jquery.cookie.js

84 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that all of those requests were addressed to Ecases.us and no external sources were called. The less responsive or slowest element that took the longest time to load (180 ms) belongs to the original domain Ecases.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 435.5 kB (60%)

Content Size

727.1 kB

After Optimization

291.7 kB

In fact, the total size of Ecases.us main page is 727.1 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. 35% of websites need less resources to load. Javascripts take 279.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 23.5 kB

  • Original 30.6 kB
  • After minification 27.9 kB
  • After compression 7.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. 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 23.5 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 7.6 kB

  • Original 187.4 kB
  • After minification 179.8 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. ECases images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 218.0 kB

  • Original 279.5 kB
  • After minification 180.1 kB
  • After compression 61.5 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 218.0 kB or 78% of the original size.

CSS Optimization

-81%

Potential reduce by 186.4 kB

  • Original 229.6 kB
  • After minification 200.3 kB
  • After compression 43.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. Ecases.us needs all CSS files to be minified and compressed as it can save up to 186.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (56%)

Requests Now

25

After Optimization

11

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECases. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

ecases.us accessibility score

52

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ecases.us best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ecases.us SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Ecases.us 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 Ecases.us 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 data is detected on the main page of ECases. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: