Tools & Wizards About Us
nfg.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

nfg.com

Working Harder to Be Your Carrier of Choice | Nassau

Page Load Speed

1.4 sec in total

First Response

11 ms

Resources Loaded

1 sec

Page Rendered

321 ms

nfg.com screenshot

About Website

Click here to check amazing Nfg content for United States. Otherwise, check out these important facts you probably never knew about nfg.com

For over 165 years, we have been helping people protect their families and provide for the income they will need in retirement. We are building a new company to last the next 100 years.

Visit nfg.com

Key Findings

We analyzed Nfg.com page load time and found that the first response time was 11 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

nfg.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

nfg.com

11 ms

nfg.com

86 ms

css

94 ms

extras.min.css

10 ms

bootstrap.min.css

60 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 50% of them (22 requests) were addressed to the original Nfg.com, 7% (3 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (575 ms) relates to the external source Gen-ai-app-builder.appspot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.9 kB (42%)

Content Size

535.0 kB

After Optimization

312.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Nfg.com main page is 535.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 245.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 54.4 kB

  • Original 64.8 kB
  • After minification 48.5 kB
  • After compression 10.4 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 16.3 kB, which is 25% 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 54.4 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 26.5 kB

  • Original 245.9 kB
  • After minification 219.4 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, Nfg needs image optimization as it can save up to 26.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 142.0 kB

  • Original 224.3 kB
  • After minification 224.3 kB
  • After compression 82.3 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 142.0 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (53%)

Requests Now

36

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nfg.com

nfg.com

11 ms

nfg.com

nfg.com

86 ms

css

css

94 ms

extras.min.css

extras.min.css

10 ms

bootstrap.min.css

bootstrap.min.css

60 ms

theme.min.css

theme.min.css

25 ms

cookieconsent.min.css

cookieconsent.min.css

59 ms

corporate.min.css

corporate.min.css

23 ms

css2

css2

112 ms

client

client

575 ms

cookieconsent.min.js

cookieconsent.min.js

58 ms

theme.min.js

theme.min.js

74 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

73 ms

gtm.js

gtm.js

58 ms

diffuser.js

diffuser.js

48 ms

retirement_savings_index_promo.jpg

retirement_savings_index_promo.jpg

10 ms

puzzle-pieces-coming-together.jpg

puzzle-pieces-coming-together.jpg

14 ms

nassau-hammer.png

nassau-hammer.png

13 ms

nassau-thumbsup.png

nassau-thumbsup.png

8 ms

nassau-helment.png

nassau-helment.png

11 ms

nassau-trophy.png

nassau-trophy.png

12 ms

prism.app-us1.com

prism.app-us1.com

196 ms

js

js

98 ms

analytics.js

analytics.js

85 ms

destination

destination

156 ms

insight.min.js

insight.min.js

151 ms

siteanalyze_6019378.js

siteanalyze_6019378.js

186 ms

fbevents.js

fbevents.js

36 ms

collect

collect

84 ms

insight_tag_errors.gif

insight_tag_errors.gif

242 ms

collect

collect

40 ms

ga-audiences

ga-audiences

198 ms

boat_building.webp

boat_building.webp

81 ms

beach-family-running.webp

beach-family-running.webp

69 ms

font

font

37 ms

fa-solid-900.woff

fa-solid-900.woff

160 ms

fa-regular-400.woff

fa-regular-400.woff

71 ms

fa-light-300.woff

fa-light-300.woff

136 ms

font

font

47 ms

font

font

47 ms

nsre.woff

nsre.woff

10 ms

fa-brands-400.woff

fa-brands-400.woff

185 ms

21666102.js

21666102.js

70 ms

image.aspx

image.aspx

65 ms

Accessibility Review

nfg.com accessibility score

87

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

nfg.com SEO score

81

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

Links do not have descriptive text

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

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

nfg.com

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