Tools & Wizards About Us
courtlistener.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

courtlistener.com

Non-Profit Free Legal Search Engine and Alert System – CourtListener.com

Page Load Speed

5.5 sec in total

First Response

237 ms

Resources Loaded

4.9 sec

Page Rendered

303 ms

courtlistener.com screenshot

About Website

Click here to check amazing Court Listener content for United States. Otherwise, check out these important facts you probably never knew about courtlistener.com

Create alerts, search for and browse the latest court opinions, PACER documents, judges, and oral arguments. Updated automatically with the latest court documents. An initiative of Free Law Project.

Visit courtlistener.com

Key Findings

We analyzed Courtlistener.com page load time and found that the first response time was 237 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

courtlistener.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

courtlistener.com

237 ms

courtlistener.com

368 ms

www.courtlistener.com

3555 ms

font-awesome.min.css

24 ms

plottable.css

160 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 91% of them (20 requests) were addressed to the original Courtlistener.com, 9% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Courtlistener.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 335.4 kB (85%)

Content Size

393.3 kB

After Optimization

57.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Courtlistener.com main page is 393.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. 30% of websites need less resources to load. HTML takes 298.9 kB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 280.3 kB

  • Original 298.9 kB
  • After minification 149.4 kB
  • After compression 18.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 149.5 kB, which is 50% 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 280.3 kB or 94% of the original size.

Image Optimization

-14%

Potential reduce by 2.4 kB

  • Original 17.6 kB
  • After minification 15.2 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. Obviously, Court Listener needs image optimization as it can save up to 2.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 35.7 kB

  • Original 54.9 kB
  • After minification 54.9 kB
  • After compression 19.1 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 35.7 kB or 65% of the original size.

CSS Optimization

-77%

Potential reduce by 17.0 kB

  • Original 22.0 kB
  • After minification 22.0 kB
  • After compression 5.0 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. Courtlistener.com needs all CSS files to be minified and compressed as it can save up to 17.0 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

18

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

courtlistener.com

courtlistener.com

237 ms

courtlistener.com

courtlistener.com

368 ms

www.courtlistener.com

www.courtlistener.com

3555 ms

font-awesome.min.css

font-awesome.min.css

24 ms

plottable.css

plottable.css

160 ms

bootstrap.min.css

bootstrap.min.css

245 ms

hopscotch.css

hopscotch.css

254 ms

override.css

override.css

254 ms

logo-large.png

logo-large.png

306 ms

logo-initials-only.png

logo-initials-only.png

304 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

247 ms

bootstrap.min.js

bootstrap.min.js

232 ms

hopscotch.min.js

hopscotch.min.js

237 ms

base.js

base.js

236 ms

d3.min.js

d3.min.js

406 ms

plottable.min.js

plottable.min.js

327 ms

jquery.bootstrap-growl.min.js

jquery.bootstrap-growl.min.js

309 ms

visualization_tools.js

visualization_tools.js

314 ms

scotus_map.js

scotus_map.js

317 ms

donate-button.png

donate-button.png

322 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2 ms

piwik.js

piwik.js

259 ms

Accessibility Review

courtlistener.com accessibility score

92

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.

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

Links do not have a discernible name

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

courtlistener.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

courtlistener.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

courtlistener.com

Open Graph data is detected on the main page of Court Listener. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: