Tools & Wizards About Us
open-public-records.com screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

open-public-records.com

Open Public Search for Criminal Records, Arrests and Court Filings

Page Load Speed

892 ms in total

First Response

69 ms

Resources Loaded

709 ms

Page Rendered

114 ms

open-public-records.com screenshot

About Website

Welcome to open-public-records.com homepage info - get ready to check Open Public Records best content for United States right away, or after learning these important things about open-public-records.com

Search public records of criminal and civil court filings, view current reports of police arrests, free open look up of U.S. bankruptcies and federal cases.

Visit open-public-records.com

Key Findings

We analyzed Open-public-records.com page load time and found that the first response time was 69 ms and then it took 823 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

open-public-records.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

open-public-records.com

69 ms

www.open-public-records.com

315 ms

normalize.css

58 ms

style_new_design.css

87 ms

ajax.js

64 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that all of those requests were addressed to Open-public-records.com and no external sources were called. The less responsive or slowest element that took the longest time to load (341 ms) belongs to the original domain Open-public-records.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 600.4 kB (80%)

Content Size

755.0 kB

After Optimization

154.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Open-public-records.com main page is 755.0 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. Only 10% of websites need less resources to load. Javascripts take 617.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 37.7 kB

  • Original 45.4 kB
  • After minification 37.7 kB
  • After compression 7.7 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 7.7 kB, which is 17% 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 37.7 kB or 83% of the original size.

Image Optimization

-36%

Potential reduce by 4.8 kB

  • Original 13.2 kB
  • After minification 8.4 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, Open Public Records needs image optimization as it can save up to 4.8 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-80%

Potential reduce by 492.5 kB

  • Original 617.2 kB
  • After minification 452.3 kB
  • After compression 124.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 492.5 kB or 80% of the original size.

CSS Optimization

-83%

Potential reduce by 65.4 kB

  • Original 79.1 kB
  • After minification 59.0 kB
  • After compression 13.7 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. Open-public-records.com needs all CSS files to be minified and compressed as it can save up to 65.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (43%)

Requests Now

14

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

open-public-records.com

open-public-records.com

69 ms

www.open-public-records.com

www.open-public-records.com

315 ms

normalize.css

normalize.css

58 ms

style_new_design.css

style_new_design.css

87 ms

ajax.js

ajax.js

64 ms

ajax-dynamic-list.js

ajax-dynamic-list.js

63 ms

jquery-1.2.2.pack.js

jquery-1.2.2.pack.js

93 ms

ddaccordion.js

ddaccordion.js

113 ms

jquery-2.1.0.min.js

jquery-2.1.0.min.js

201 ms

readmore.js

readmore.js

119 ms

jquery-ui.js

jquery-ui.js

341 ms

jquery-ui.css

jquery-ui.css

173 ms

oprlogo.gif

oprlogo.gif

31 ms

down-arrow-v2.png

down-arrow-v2.png

58 ms

btn_bg.jpg

btn_bg.jpg

60 ms

ui-bg_highlight-soft_100_eeeeee_1x100.png

ui-bg_highlight-soft_100_eeeeee_1x100.png

59 ms

Accessibility Review

open-public-records.com accessibility score

84

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

Form elements do not have associated labels

Best Practices

open-public-records.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

open-public-records.com SEO score

88

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Open-public-records.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Open-public-records.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

open-public-records.com

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