Tools & Wizards About Us
ecases.us screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ecases.us

eCases - All United States Court Cases Online

Page Load Speed

5 sec in total

First Response

2.1 sec

Resources Loaded

2.8 sec

Page Rendered

147 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 2.1 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

ecases.us performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.691

7/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

ecases.us

2099 ms

city_master.css

243 ms

jquery-ui.min.css

262 ms

jquery-1.10.2.min.js

364 ms

jquery.cookie.js

149 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 96% of them (26 requests) were addressed to the original Ecases.us, 4% (1 request) were made to Elaws.us. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Ecases.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.3 kB (71%)

Content Size

32.9 kB

After Optimization

9.6 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Ecases.us main page is 32.9 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. 15% of websites need less resources to load. HTML takes 29.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 22.8 kB

  • Original 29.8 kB
  • After minification 27.5 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 22.8 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 905 B
  • After minification 905 B

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.

CSS Optimization

-26%

Potential reduce by 554 B

  • Original 2.2 kB
  • After minification 2.1 kB
  • After compression 1.6 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 554 B or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (50%)

Requests Now

26

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ecases.us

ecases.us

2099 ms

city_master.css

city_master.css

243 ms

jquery-ui.min.css

jquery-ui.min.css

262 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

364 ms

jquery.cookie.js

jquery.cookie.js

149 ms

jquery.simplemodal-1.4.4.js

jquery.simplemodal-1.4.4.js

251 ms

font-awesome.css

font-awesome.css

147 ms

modernizr-2.7.2.js

modernizr-2.7.2.js

348 ms

jquery.artDialog.source.js

jquery.artDialog.source.js

229 ms

crosssessionID

crosssessionID

127 ms

skelpanel.min.js

skelpanel.min.js

312 ms

resinit.js

resinit.js

246 ms

main.css

main.css

192 ms

blue.css

blue.css

70 ms

android88.png

android88.png

63 ms

apple88.png

apple88.png

76 ms

logo.png

logo.png

67 ms

beta.png

beta.png

71 ms

meun_icons.png

meun_icons.png

82 ms

Search.png

Search.png

49 ms

bg_eCases.jpg

bg_eCases.jpg

233 ms

bannerfont_eCases.png

bannerfont_eCases.png

188 ms

block01.jpg

block01.jpg

134 ms

block02.jpg

block02.jpg

126 ms

facebook.png

facebook.png

160 ms

city_master-w1024-.css

city_master-w1024-.css

108 ms

city_master-w800-1024.css

city_master-w800-1024.css

187 ms

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

ecases.us

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: