Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

401k.com

Fidelity NetBenefits | Employee Benefits

Page Load Speed

628 ms in total

First Response

70 ms

Resources Loaded

558 ms

Page Rendered

0 ms

401k.com screenshot

About Website

Welcome to 401k.com homepage info - get ready to check 401 K best content for United States right away, or after learning these important things about 401k.com

If your employer offers benefits through Fidelity, log in to Fidelity NetBenefits to see your 401(k), 403(b), health benefits, stock plans, and more.

Visit 401k.com

Key Findings

We analyzed 401k.com page load time and found that the first response time was 70 ms and then it took 558 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

401k.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.9 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value3,140 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

401k.com

70 ms

401k.com

22 ms

home

220 ms

fonts.css

88 ms

styles.ap119043-bundle.css

82 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original 401k.com, 44% (7 requests) were made to Nb.fidelity.com and 31% (5 requests) were made to Assets.fidelity.com. The less responsive or slowest element that took the longest time to load (220 ms) relates to the external source Nb.fidelity.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.4 kB (32%)

Content Size

133.9 kB

After Optimization

91.5 kB

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

HTML Optimization

-87%

Potential reduce by 42.4 kB

  • Original 48.9 kB
  • After minification 48.4 kB
  • After compression 6.5 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 42.4 kB or 87% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 85.1 kB
  • After minification 85.1 kB
  • After compression 85.1 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.

Requests Breakdown

Number of requests can be reduced by 9 (69%)

Requests Now

13

After Optimization

4

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

Accessibility Review

401k.com accessibility score

93

Accessibility Issues

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

401k.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

401k.com SEO score

76

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

High

robots.txt is not valid

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 401k.com 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 401k.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 Graph description is not detected on the main page of 401 K. 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: