Tools & Wizards About Us
charlotte.nm.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

charlotte.nm.com

Charlotte, NC Financial Advisor Office | Northwestern Mutual

Page Load Speed

1.7 sec in total

First Response

36 ms

Resources Loaded

1.4 sec

Page Rendered

286 ms

charlotte.nm.com screenshot

About Website

Visit charlotte.nm.com now to see the best up-to-date Charlotte Nm content for United States and also check out these interesting facts you probably never knew about charlotte.nm.com

Everything you need from insurance to investments to financial planning, all in one place. Get in touch with your Charlotte, NC Northwestern Mutual financial advisor office.

Visit charlotte.nm.com

Key Findings

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

Performance Metrics

charlotte.nm.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value1,360 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

charlotte.nm.com

36 ms

charlotte.nm.com

62 ms

139 ms

offices.css

29 ms

launch-EN601ad48fe03a4aa39be269d4d5c2c405.min.js

22 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Charlotte.nm.com, 37% (32 requests) were made to Media.northwesternmutual.com and 10% (9 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (650 ms) relates to the external source Media.northwesternmutual.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 556.0 kB (18%)

Content Size

3.2 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Charlotte.nm.com main page is 3.2 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. 80% 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 173.0 kB

  • Original 210.7 kB
  • After minification 202.4 kB
  • After compression 37.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. 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 173.0 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 105.2 kB

  • Original 2.1 MB
  • After minification 2.0 MB

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. Charlotte Nm images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 277.4 kB

  • Original 779.3 kB
  • After minification 779.1 kB
  • After compression 501.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 277.4 kB or 36% of the original size.

CSS Optimization

-1%

Potential reduce by 409 B

  • Original 47.6 kB
  • After minification 47.6 kB
  • After compression 47.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. Charlotte.nm.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 44 (57%)

Requests Now

77

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

charlotte.nm.com

charlotte.nm.com

36 ms

charlotte.nm.com

charlotte.nm.com

62 ms

139 ms

offices.css

offices.css

29 ms

launch-EN601ad48fe03a4aa39be269d4d5c2c405.min.js

launch-EN601ad48fe03a4aa39be269d4d5c2c405.min.js

22 ms

offices.js

offices.js

103 ms

js

js

166 ms

js

js

103 ms

navigation-menu-mobile.svg

navigation-menu-mobile.svg

309 ms

fbevents.js

fbevents.js

121 ms

bat.js

bat.js

120 ms

cancel-x.svg

cancel-x.svg

301 ms

nm-logo-blue.svg

nm-logo-blue.svg

277 ms

navigation-search-inactive-mobile.svg

navigation-search-inactive-mobile.svg

170 ms

new-navigation-search-active-mobile.svg

new-navigation-search-active-mobile.svg

180 ms

navigation-chevron-blue-right-mobile.svg

navigation-chevron-blue-right-mobile.svg

179 ms

navigation-chevron-left-grey-mobile.svg

navigation-chevron-left-grey-mobile.svg

301 ms

navigation-search-reverse.svg

navigation-search-reverse.svg

301 ms

navigation-search-active.svg

navigation-search-active.svg

299 ms

handshake.svg

handshake.svg

378 ms

chevron-right-blue.svg

chevron-right-blue.svg

372 ms

nav-active-carret-blue.svg

nav-active-carret-blue.svg

370 ms

nav-inactive-carret-blue.svg

nav-inactive-carret-blue.svg

373 ms

73e3e546-0f96-4709-a1e5-1179f3f1e3e4.jpeg

73e3e546-0f96-4709-a1e5-1179f3f1e3e4.jpeg

408 ms

expert-partner.svg

expert-partner.svg

375 ms

point-to-point.svg

point-to-point.svg

406 ms

gold-star.svg

gold-star.svg

410 ms

supporting-photo-find-an-fr-v3.jpg

supporting-photo-find-an-fr-v3.jpg

434 ms

handshake-reverse.svg

handshake-reverse.svg

466 ms

man-with-flag.svg

man-with-flag.svg

430 ms

rocket.svg

rocket.svg

476 ms

supporting-photo-apply-now-v4.jpg

supporting-photo-apply-now-v4.jpg

468 ms

nametag-reverse.svg

nametag-reverse.svg

465 ms

supporting-photo-giving-back.jpg

supporting-photo-giving-back.jpg

572 ms

supporting-photo-nm-stats.jpg

supporting-photo-nm-stats.jpg

569 ms

map-marker.svg

map-marker.svg

650 ms

other-locations-blue-bar.svg

other-locations-blue-bar.svg

570 ms

chevron-right.svg

chevron-right.svg

647 ms

id

id

135 ms

AppMeasurement.min.js

AppMeasurement.min.js

96 ms

AppMeasurement_Module_ActivityMap.min.js

AppMeasurement_Module_ActivityMap.min.js

127 ms

insight.min.js

insight.min.js

109 ms

heap-3637159320.js

heap-3637159320.js

316 ms

staticmap

staticmap

212 ms

staticmap

staticmap

91 ms

staticmap

staticmap

188 ms

chevron-up.svg

chevron-up.svg

562 ms

dropdown-arrow.svg

dropdown-arrow.svg

564 ms

dropdown-arrow-open.svg

dropdown-arrow-open.svg

562 ms

chevron-left-grey.svg

chevron-left-grey.svg

638 ms

GuardianSans-Regular.woff

GuardianSans-Regular.woff

81 ms

GuardianSans-Light.woff

GuardianSans-Light.woff

197 ms

GuardianSans-Thin.woff

GuardianSans-Thin.woff

197 ms

GuardianSans-Medium.woff

GuardianSans-Medium.woff

196 ms

GuardianSans-SemiBold.woff

GuardianSans-SemiBold.woff

197 ms

287689728264317

287689728264317

154 ms

25058490.js

25058490.js

14 ms

otSDKStub.js

otSDKStub.js

152 ms

dest5.html

dest5.html

209 ms

ibs:dpid=411&dpuuid=ZtBphQAAAHd5vQNw

ibs:dpid=411&dpuuid=ZtBphQAAAHd5vQNw

67 ms

fdef34fb-1c38-40ad-a9dc-11df33182c5e.json

fdef34fb-1c38-40ad-a9dc-11df33182c5e.json

45 ms

location

location

55 ms

js

js

14 ms

js

js

37 ms

js

js

111 ms

js

js

188 ms

js

js

111 ms

otBannerSdk.js

otBannerSdk.js

16 ms

5564967.js

5564967.js

173 ms

en.json

en.json

151 ms

li_sync

li_sync

156 ms

182 ms

249 ms

js

js

135 ms

analytics.js

analytics.js

208 ms

otFlat.json

otFlat.json

94 ms

otPcPanel.json

otPcPanel.json

110 ms

otCommonStyles.css

otCommonStyles.css

107 ms

collect

collect

91 ms

ot_close.svg

ot_close.svg

76 ms

nm-navy-200x40-2x.png

nm-navy-200x40-2x.png

47 ms

nr-1044.min.js

nr-1044.min.js

13 ms

uwt.js

uwt.js

17 ms

280747e763

280747e763

120 ms

adsct

adsct

46 ms

adsct

adsct

98 ms

Accessibility Review

charlotte.nm.com accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[role]s are not contained by their required parent element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

charlotte.nm.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

Page has valid source maps

SEO Factors

charlotte.nm.com SEO score

71

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

High

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

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 Charlotte.nm.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 Charlotte.nm.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

charlotte.nm.com

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