Tools & Wizards About Us
e-records.us screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

e-records.us

e-records.us

Page Load Speed

7.2 sec in total

First Response

187 ms

Resources Loaded

5.8 sec

Page Rendered

1.2 sec

e-records.us screenshot

About Website

Welcome to e-records.us homepage info - get ready to check E Records best content for United States right away, or after learning these important things about e-records.us

This domain may be for sale!

Visit e-records.us

Key Findings

We analyzed E-records.us page load time and found that the first response time was 187 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

e-records.us performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value2,840 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

e-records.us

187 ms

gtm.js

330 ms

css

328 ms

bootstrap.min.css

305 ms

ssn-index.css

531 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original E-records.us, 14% (7 requests) were made to Files.s3-plus.com and 12% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Front.optimonk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.0 kB (33%)

Content Size

215.6 kB

After Optimization

143.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-records.us main page is 215.6 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. 55% of websites need less resources to load. Javascripts take 152.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 29.4 kB

  • Original 38.1 kB
  • After minification 30.6 kB
  • After compression 8.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.4 kB, which is 20% 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 29.4 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 1.2 kB

  • Original 23.0 kB
  • After minification 21.8 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. E Records images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 41.1 kB

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

CSS Optimization

-12%

Potential reduce by 305 B

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 2.2 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. E-records.us needs all CSS files to be minified and compressed as it can save up to 305 B or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (73%)

Requests Now

44

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-records.us

e-records.us

187 ms

gtm.js

gtm.js

330 ms

css

css

328 ms

bootstrap.min.css

bootstrap.min.css

305 ms

ssn-index.css

ssn-index.css

531 ms

jquery.min.js

jquery.min.js

586 ms

j.php

j.php

486 ms

norton.png

norton.png

268 ms

img_package@x2.jpg

img_package@x2.jpg

453 ms

icon-pc.svg

icon-pc.svg

450 ms

icon-send.svg

icon-send.svg

547 ms

icon-letter.svg

icon-letter.svg

552 ms

checkmark.png

checkmark.png

537 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

1190 ms

seal.min.js

seal.min.js

1461 ms

bat.js

bat.js

939 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

947 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

968 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

1228 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

1247 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

2178 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

2176 ms

js

js

416 ms

preload.js

preload.js

2556 ms

hotjar-1835446.js

hotjar-1835446.js

1127 ms

pa-5ea9a288229e930008000a65.js

pa-5ea9a288229e930008000a65.js

1129 ms

v.gif

v.gif

234 ms

tag-30d32611c03aa5bfdbf090b55256d940.js

tag-30d32611c03aa5bfdbf090b55256d940.js

475 ms

analytics.js

analytics.js

1537 ms

js

js

599 ms

js

js

578 ms

js

js

575 ms

26039919.js

26039919.js

1445 ms

settings.js

settings.js

1173 ms

modules.bcd9ade6b0bb9bdd0789.js

modules.bcd9ade6b0bb9bdd0789.js

1382 ms

conversion_async.js

conversion_async.js

1596 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

683 ms

js

js

363 ms

26039919

26039919

597 ms

collect

collect

272 ms

656 ms

727 ms

650 ms

clarity.js

clarity.js

597 ms

collect

collect

612 ms

233 ms

175 ms

174 ms

ga-audiences

ga-audiences

166 ms

settings.js

settings.js

224 ms

c.gif

c.gif

9 ms

Accessibility Review

e-records.us accessibility score

65

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

Image elements do not have [alt] attributes

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

e-records.us 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

e-records.us SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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 E-records.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 E-records.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.

Social Sharing Optimization

e-records.us

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