Tools & Wizards About Us
nwagent.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

nwagent.com

Insurance and Financial Services Company – Nationwide

Page Load Speed

1.7 sec in total

First Response

167 ms

Resources Loaded

1.3 sec

Page Rendered

248 ms

nwagent.com screenshot

About Website

Welcome to nwagent.com homepage info - get ready to check Nwagent best content right away, or after learning these important things about nwagent.com

Nationwide offers insurance, retirement and investing products that protect your many sides. Get home and auto insurance quotes online or find a local agent.

Visit nwagent.com

Key Findings

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

nwagent.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value38.2 s

0/100

25%

SI (Speed Index)

Value32.9 s

0/100

10%

TBT (Total Blocking Time)

Value48,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.109

87/100

15%

TTI (Time to Interactive)

Value63.0 s

0/100

10%

Network Requests Diagram

nwagent.com

167 ms

agency.nationwide.com

94 ms

5597e09a93ceb0b69174a52cc331dab3-def.global.css

32 ms

0c5705bf30aff65851b8ce668195ffb3-def.home.css

41 ms

Bootstrap.js

40 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Nwagent.com, 25% (16 requests) were made to D1yxxa0q6kurd9.cloudfront.net and 8% (5 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (449 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 458.4 kB (52%)

Content Size

885.7 kB

After Optimization

427.3 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-71%

Potential reduce by 18.7 kB

  • Original 26.2 kB
  • After minification 24.9 kB
  • After compression 7.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 18.7 kB or 71% of the original size.

Image Optimization

-13%

Potential reduce by 27.3 kB

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

JavaScript Optimization

-64%

Potential reduce by 412.4 kB

  • Original 648.7 kB
  • After minification 572.7 kB
  • After compression 236.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 412.4 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (75%)

Requests Now

56

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nwagent.com

nwagent.com

167 ms

agency.nationwide.com

agency.nationwide.com

94 ms

5597e09a93ceb0b69174a52cc331dab3-def.global.css

5597e09a93ceb0b69174a52cc331dab3-def.global.css

32 ms

0c5705bf30aff65851b8ce668195ffb3-def.home.css

0c5705bf30aff65851b8ce668195ffb3-def.home.css

41 ms

Bootstrap.js

Bootstrap.js

40 ms

asc

asc

64 ms

jquery.min.js

jquery.min.js

62 ms

597d4404bcb0a00dea3c984f04795797-def.global.js

597d4404bcb0a00dea3c984f04795797-def.global.js

62 ms

b177c8c0ed2b0bcdd496a26b6efeaa53-def.nondependant.js

b177c8c0ed2b0bcdd496a26b6efeaa53-def.nondependant.js

62 ms

api.js

api.js

160 ms

analytics.js

analytics.js

84 ms

prum.min.js

prum.min.js

109 ms

seal

seal

54 ms

e7ed5028f50164cbd32eee10df7e0c7a-default%2Fimages%2Fweb-bg.png

e7ed5028f50164cbd32eee10df7e0c7a-default%2Fimages%2Fweb-bg.png

48 ms

f6012371db4718f91ac7c13280245b63-default%2Fimages%2Fpage-bg.png

f6012371db4718f91ac7c13280245b63-default%2Fimages%2Fpage-bg.png

54 ms

38487b1a9349aa2874f2fd2f5248492b-default%2Fimages%2Fsprites.png

38487b1a9349aa2874f2fd2f5248492b-default%2Fimages%2Fsprites.png

100 ms

0cd0df1ad1072279e2e18e4fe060ac9f-default%2Fimages%2Fnw_main.png

0cd0df1ad1072279e2e18e4fe060ac9f-default%2Fimages%2Fnw_main.png

58 ms

725db32f84d164cad415d8694e5036d0-default%2Fimages%2Fkey_icon.gif

725db32f84d164cad415d8694e5036d0-default%2Fimages%2Fkey_icon.gif

56 ms

e30c132f61ed94a5987c167e7247cd0a-default%2Fimages%2Ffind_an_agent.png

e30c132f61ed94a5987c167e7247cd0a-default%2Fimages%2Ffind_an_agent.png

59 ms

91b6a6d60890dc38460187c0548f9a2f-default%2Fimages%2Fnw_fixed_size_bg.png

91b6a6d60890dc38460187c0548f9a2f-default%2Fimages%2Fnw_fixed_size_bg.png

59 ms

976e73b35dca90261edab8a2bffa1855-default%2Fimages%2Fnw_sliders.png

976e73b35dca90261edab8a2bffa1855-default%2Fimages%2Fnw_sliders.png

63 ms

7cbb2c5e9f08de31da3b4155a6fca8b8-webtrends.min.js

7cbb2c5e9f08de31da3b4155a6fca8b8-webtrends.min.js

44 ms

serverComponent.php

serverComponent.php

68 ms

6df68b8ae10971be3071946c27a7e220-def.app.js

6df68b8ae10971be3071946c27a7e220-def.app.js

25 ms

webtrends.hm.js

webtrends.hm.js

115 ms

49581fd2432b86d73d9bd320f6a1a894-dynamicFPCdom.js

49581fd2432b86d73d9bd320f6a1a894-dynamicFPCdom.js

35 ms

wtid.js

wtid.js

57 ms

collect

collect

18 ms

6c65e43d59abfb624e17bf79d20b406d-def.print.css

6c65e43d59abfb624e17bf79d20b406d-def.print.css

6 ms

recaptcha__en.js

recaptcha__en.js

31 ms

26456f2159cd2f56c44535e62d441d68.js

26456f2159cd2f56c44535e62d441d68.js

11 ms

collect

collect

74 ms

d58c5962eebd7d85ba14980811c78da8.js

d58c5962eebd7d85ba14980811c78da8.js

59 ms

19a495a397f50488f36667487f25324c.js

19a495a397f50488f36667487f25324c.js

14 ms

t.js

t.js

49 ms

linkid.js

linkid.js

5 ms

ip.json

ip.json

32 ms

;u20=GA1.2.1451793597.1458292988;ord=8168824196327.478

;u20=GA1.2.1451793597.1458292988;ord=8168824196327.478

52 ms

collect

collect

6 ms

collect

collect

19 ms

ga-audiences

ga-audiences

17 ms

bat.js

bat.js

143 ms

conversion.js

conversion.js

81 ms

beacon

beacon

142 ms

H2153luvzTELJhrlYa4T1gr_0JVtdA.gif

H2153luvzTELJhrlYa4T1gr_0JVtdA.gif

123 ms

lb

lb

88 ms

dcs.gif

dcs.gif

79 ms

Pix-1x1.gif

Pix-1x1.gif

58 ms

fbevents.js

fbevents.js

311 ms

fp.js

fp.js

381 ms

fbds.js

fbds.js

449 ms

40 ms

betr=sslbet_32566=%5B+%5Dssprlb_748089%5B24%5D%7Csslbet_32567=%5B+%5Dssprlb_748091%5B72%5D%7Csslbet_32568=%5B+%5Dssprlb_748093%5B168%5D%7Csslbet_32569=%5B+%5Dssprlb_748095%5B720%5D

betr=sslbet_32566=%5B+%5Dssprlb_748089%5B24%5D%7Csslbet_32567=%5B+%5Dssprlb_748091%5B72%5D%7Csslbet_32568=%5B+%5Dssprlb_748093%5B168%5D%7Csslbet_32569=%5B+%5Dssprlb_748095%5B720%5D

12 ms

1x1.gif

1x1.gif

7 ms

42 ms

spp.pl

spp.pl

19 ms

38 ms

95 ms

172 ms

offsite_event.php

offsite_event.php

64 ms

i

i

15 ms

beacon.gif

beacon.gif

139 ms

t

t

7 ms

pixel

pixel

39 ms

google-adx

google-adx

24 ms

Accessibility Review

nwagent.com accessibility score

98

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.

Best Practices

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

nwagent.com SEO score

90

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

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

nwagent.com

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