818 ms in total
116 ms
509 ms
193 ms
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.usWe 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.
ecases.us performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value5.6 s
18/100
25%
Value3.7 s
85/100
10%
Value30 ms
100/100
30%
Value0.635
9/100
15%
Value4.4 s
83/100
10%
116 ms
76 ms
98 ms
139 ms
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 size can be reduced by 435.5 kB (60%)
727.1 kB
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.
Potential reduce by 23.5 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.
Potential reduce by 7.6 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.
Potential reduce by 218.0 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.
Potential reduce by 186.4 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.
Number of requests can be reduced by 14 (56%)
25
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.
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
jquery.simplemodal-1.4.4.js
111 ms
font-awesome.css
113 ms
ruleformat.css
109 ms
modernizr-2.7.2.js
152 ms
jquery.artDialog.source.js
137 ms
crosssessionID
95 ms
skelpanel.min.js
180 ms
resinit.js
146 ms
main.css
141 ms
blue.css
36 ms
logo-elaws.png
39 ms
app_store_btn.jpg
44 ms
meun_icons.png
35 ms
Search.png
34 ms
bg_eCases.jpg
43 ms
bannerfont_eCases.png
44 ms
block01.jpg
81 ms
block02.jpg
82 ms
facebook.png
87 ms
city_master-w1024-.css
49 ms
city_master-w800-1024.css
64 ms
ecases.us accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ecases.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
ecases.us SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
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.
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: