Tools & Wizards About Us
publicrecords.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

publicrecords.com

Public Records - People Search, Background Checks & Phone Number Lookup

Page Load Speed

20.8 sec in total

First Response

232 ms

Resources Loaded

15.2 sec

Page Rendered

5.5 sec

publicrecords.com screenshot

About Website

Visit publicrecords.com now to see the best up-to-date Public Records content for United States and also check out these interesting facts you probably never knew about publicrecords.com

Find people instantly. Search for someone by their name, phone number or address. Inteilus provides phone numbers, previous addresses and background checks.

Visit publicrecords.com

Key Findings

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

Performance Metrics

publicrecords.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value1,690 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

publicrecords.com

232 ms

www.publicrecords.com

1056 ms

193729286.js

1089 ms

all.css

440 ms

form.css

927 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 43% of them (18 requests) were addressed to the original Publicrecords.com, 7% (3 requests) were made to Platform.twitter.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Platform.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 605.4 kB (51%)

Content Size

1.2 MB

After Optimization

573.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Publicrecords.com main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 896.6 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 23.5 kB

  • Original 35.8 kB
  • After minification 33.1 kB
  • After compression 12.3 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 66% of the original size.

Image Optimization

-3%

Potential reduce by 7.5 kB

  • Original 218.3 kB
  • After minification 210.7 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. Public Records images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 551.4 kB

  • Original 896.6 kB
  • After minification 861.1 kB
  • After compression 345.2 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 551.4 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 23.0 kB

  • Original 27.8 kB
  • After minification 19.7 kB
  • After compression 4.8 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. Publicrecords.com needs all CSS files to be minified and compressed as it can save up to 23.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (61%)

Requests Now

38

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 13 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

publicrecords.com

publicrecords.com

232 ms

www.publicrecords.com

www.publicrecords.com

1056 ms

193729286.js

193729286.js

1089 ms

all.css

all.css

440 ms

form.css

form.css

927 ms

form.js

form.js

926 ms

plusone.js

plusone.js

927 ms

conversion.js

conversion.js

989 ms

girl_in_jeans_113730115_200x500.png

girl_in_jeans_113730115_200x500.png

746 ms

geo2.js

geo2.js

1332 ms

event

event

2453 ms

analytics.js

analytics.js

2323 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

307 ms

sdk.js

sdk.js

3528 ms

widgets.js

widgets.js

4631 ms

bg-wrapper-holder.gif

bg-wrapper-holder.gif

3260 ms

bg-separator-navbar.gif

bg-separator-navbar.gif

3205 ms

bg-logo.gif

bg-logo.gif

3204 ms

bg-sprites.png

bg-sprites.png

3176 ms

bg-nav.gif

bg-nav.gif

4389 ms

bg-input-text.gif

bg-input-text.gif

4389 ms

button-blue-search-4.jpg

button-blue-search-4.jpg

4625 ms

bg-top.png

bg-top.png

4625 ms

bg-left.png

bg-left.png

4368 ms

bg-right.png

bg-right.png

4540 ms

bg-bottom.png

bg-bottom.png

4561 ms

bg-separator-footer.gif

bg-separator-footer.gif

4561 ms

3758 ms

event

event

2309 ms

collect

collect

1808 ms

collect

collect

1938 ms

1838 ms

2744 ms

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

310 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

2439 ms

follow_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

follow_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

493 ms

nr-1044.min.js

nr-1044.min.js

1591 ms

jot

jot

1514 ms

like.php

like.php

860 ms

37742fa2de

37742fa2de

1187 ms

0zf7krTbbuX.js

0zf7krTbbuX.js

1310 ms

lH1ibRl5GKq.png

lH1ibRl5GKq.png

1214 ms

Accessibility Review

publicrecords.com accessibility score

96

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.

Best Practices

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

publicrecords.com SEO score

82

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

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 Publicrecords.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 Publicrecords.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

publicrecords.com

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