Tools & Wizards About Us
eversafe.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

eversafe.com

Protecting a Lifetime of Savings | EverSafe

Page Load Speed

5.5 sec in total

First Response

83 ms

Resources Loaded

3.9 sec

Page Rendered

1.6 sec

eversafe.com screenshot

About Website

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

It’s Your Money...Let’s Keep It That Way. EverSafe® guards against fraud, identity theft, and age-related issues.

Visit eversafe.com

Key Findings

We analyzed Eversafe.com page load time and found that the first response time was 83 ms and then it took 5.4 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

eversafe.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.75

6/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

eversafe.com

83 ms

index.html

183 ms

2222980934.js

35 ms

theme.css

183 ms

animate.css

130 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 46% of them (46 requests) were addressed to the original Eversafe.com, 11% (11 requests) were made to Fonts.gstatic.com and 8% (8 requests) were made to Static.olark.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Eversafe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 969.8 kB (68%)

Content Size

1.4 MB

After Optimization

449.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eversafe.com main page is 1.4 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. 70% of websites need less resources to load. Javascripts take 775.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 61.2 kB

  • Original 75.0 kB
  • After minification 50.4 kB
  • After compression 13.8 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 24.6 kB, which is 33% 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 61.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 104.3 kB
  • After minification 104.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. Ever Safe images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 501.8 kB

  • Original 775.3 kB
  • After minification 740.7 kB
  • After compression 273.5 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 501.8 kB or 65% of the original size.

CSS Optimization

-88%

Potential reduce by 406.7 kB

  • Original 464.3 kB
  • After minification 384.4 kB
  • After compression 57.6 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. Eversafe.com needs all CSS files to be minified and compressed as it can save up to 406.7 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (59%)

Requests Now

83

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eversafe.com

eversafe.com

83 ms

index.html

index.html

183 ms

2222980934.js

2222980934.js

35 ms

theme.css

theme.css

183 ms

animate.css

animate.css

130 ms

entypo.css

entypo.css

144 ms

font-awesome.min.css

font-awesome.min.css

128 ms

buttons-secure.css

buttons-secure.css

125 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

161 ms

bootstrap.min.js

bootstrap.min.js

169 ms

theme.js

theme.js

147 ms

choosePlan.js

choosePlan.js

171 ms

enrollment.js

enrollment.js

235 ms

ajax.js

ajax.js

232 ms

form.js

form.js

467 ms

elderscan.js

elderscan.js

234 ms

dialog.js

dialog.js

477 ms

riveted.min.js

riveted.min.js

477 ms

jquery.scrolldepth.min.js

jquery.scrolldepth.min.js

467 ms

conversion.js

conversion.js

127 ms

analytics.min.js

analytics.min.js

210 ms

hotjar-105814.js

hotjar-105814.js

446 ms

0e50b065fd8846d9ae5023709474771ca87c1169c2f94599bf543cd2f168fcb2

0e50b065fd8846d9ae5023709474771ca87c1169c2f94599bf543cd2f168fcb2

202 ms

fbds.js

fbds.js

469 ms

bootstrap.min.css

bootstrap.min.css

271 ms

css

css

298 ms

css

css

298 ms

css

css

320 ms

css

css

419 ms

core.js

core.js

326 ms

p

p

1087 ms

conversion_async.js

conversion_async.js

53 ms

bat.js

bat.js

486 ms

analytics.js

analytics.js

484 ms

w.js

w.js

655 ms

roundtrip.js

roundtrip.js

532 ms

modules-71ae35a1942a0c77d1b9d5e6b4768074.js

modules-71ae35a1942a0c77d1b9d5e6b4768074.js

640 ms

666 ms

logo.png

logo.png

288 ms

seal

seal

789 ms

logo-i.png

logo-i.png

286 ms

blank.png

blank.png

287 ms

loading3c.gif

loading3c.gif

286 ms

wsj.png

wsj.png

286 ms

ConsumerReports.png

ConsumerReports.png

285 ms

forbes.png

forbes.png

549 ms

kiplinger-red.png

kiplinger-red.png

549 ms

usnews_logo.png

usnews_logo.png

549 ms

npr-color.png

npr-color.png

548 ms

americanbankerfull.png

americanbankerfull.png

547 ms

ourstory.jpg

ourstory.jpg

547 ms

liz_whcoa.png

liz_whcoa.png

866 ms

feature1.png

feature1.png

726 ms

vault.png

vault.png

628 ms

feature2.png

feature2.png

726 ms

bbbreg.png

bbbreg.png

639 ms

aplus_rating.png

aplus_rating.png

638 ms

norton.png

norton.png

784 ms

fb.png

fb.png

776 ms

social-tw.png

social-tw.png

777 ms

loader0.js

loader0.js

593 ms

trk

trk

2933 ms

bg30.jpg

bg30.jpg

905 ms

home-grad2.png

home-grad2.png

855 ms

bgg.png

bgg.png

856 ms

RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf

RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf

545 ms

ZvcMqxEwPfh2qDWBPxn6ngV_pQ1T3xN3K1c3sB361us.ttf

ZvcMqxEwPfh2qDWBPxn6ngV_pQ1T3xN3K1c3sB361us.ttf

654 ms

ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf

ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf

737 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

805 ms

4cKlrioa77J2iqTqBgkRWg.ttf

4cKlrioa77J2iqTqBgkRWg.ttf

814 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

814 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

805 ms

zJY4gsxBiSo5L7tNutxFNg.ttf

zJY4gsxBiSo5L7tNutxFNg.ttf

813 ms

So5lHxHT37p2SS4-t60SlCtfYakCkPqOMDce0h_3gD8.ttf

So5lHxHT37p2SS4-t60SlCtfYakCkPqOMDce0h_3gD8.ttf

804 ms

EYh7Vl4ywhowqULgRdYwIH3uxQAI1Bvm-GxtFNy4yl0.ttf

EYh7Vl4ywhowqULgRdYwIH3uxQAI1Bvm-GxtFNy4yl0.ttf

838 ms

EYh7Vl4ywhowqULgRdYwICxQL91WRy8t8mPvAX_dIgA.ttf

EYh7Vl4ywhowqULgRdYwICxQL91WRy8t8mPvAX_dIgA.ttf

838 ms

entypo.ttf

entypo.ttf

651 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

718 ms

collect

collect

232 ms

api.min.js

api.min.js

621 ms

collect

collect

197 ms

619 ms

57ccee77b23d89e468c8dc40

57ccee77b23d89e468c8dc40

355 ms

376 ms

7520-272-10-8541.js

7520-272-10-8541.js

198 ms

325 ms

c

c

333 ms

jquery.min.js

jquery.min.js

176 ms

ga-audiences

ga-audiences

105 ms

304809

304809

48 ms

visit-data

visit-data

214 ms

application2.js

application2.js

15 ms

storage.html

storage.html

4 ms

storage.js

storage.js

5 ms

visits

visits

438 ms

jquery.js

jquery.js

221 ms

0eb2d68e5e55419611e14368e9565d21.css

0eb2d68e5e55419611e14368e9565d21.css

257 ms

s

s

148 ms

buttons-light.png

buttons-light.png

31 ms

57ccee77b23d89e468c8dc40

57ccee77b23d89e468c8dc40

207 ms

20 ms

Accessibility Review

eversafe.com accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

eversafe.com SEO score

96

Search Engine Optimization Advices

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

eversafe.com

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