Report Summary

  • 73

    Performance

    Renders faster than
    83% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

records-search.net

Research Public Records - Vital Records Online - Records-Search.net

Page Load Speed

2.7 sec in total

First Response

87 ms

Resources Loaded

2.3 sec

Page Rendered

283 ms

records-search.net screenshot

About Website

Visit records-search.net now to see the best up-to-date Records Search content and also check out these interesting facts you probably never knew about records-search.net

FindVitalRecords,net : Look up all types of local public records including official copies of birth certificates, death records, property deeds, and more.

Visit records-search.net

Key Findings

We analyzed Records-search.net page load time and found that the first response time was 87 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

records-search.net performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value7.0 s

52/100

10%

Network Requests Diagram

records-search.net

87 ms

records-search.net

141 ms

www.records-search.net

72 ms

www.records-search.net

1671 ms

style.css

51 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 53% of them (8 requests) were addressed to the original Records-search.net, 13% (2 requests) were made to Pagead2.googlesyndication.com and 13% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Records-search.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.0 kB (15%)

Content Size

479.8 kB

After Optimization

406.8 kB

In fact, the total size of Records-search.net main page is 479.8 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. 40% of websites need less resources to load. Javascripts take 388.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.8 kB

  • Original 35.1 kB
  • After minification 33.2 kB
  • After compression 8.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 26.8 kB or 76% of the original size.

Image Optimization

-52%

Potential reduce by 3.6 kB

  • Original 6.9 kB
  • After minification 3.3 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, Records Search needs image optimization as it can save up to 3.6 kB or 52% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 233 B

  • Original 388.1 kB
  • After minification 388.1 kB
  • After compression 387.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-85%

Potential reduce by 42.3 kB

  • Original 49.7 kB
  • After minification 42.9 kB
  • After compression 7.3 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. Records-search.net needs all CSS files to be minified and compressed as it can save up to 42.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (45%)

Requests Now

11

After Optimization

6

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

Accessibility Review

records-search.net accessibility score

67

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

records-search.net best practices score

75

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

High

Page has valid source maps

SEO Factors

records-search.net SEO score

80

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