Tools & Wizards About Us
utah.nm.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% 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

  • 79

    SEO

    Google-friendlier than
    40% of websites

utah.nm.com

Salt Lake City, UT Financial Advisor Office | Northwestern Mutual

Page Load Speed

1.8 sec in total

First Response

57 ms

Resources Loaded

1.4 sec

Page Rendered

326 ms

utah.nm.com screenshot

About Website

Welcome to utah.nm.com homepage info - get ready to check UT Ah Nm best content for United States right away, or after learning these important things about utah.nm.com

Everything you need from insurance to investments to financial planning, all in one place. Get in touch with your Salt Lake City, UT Northwestern Mutual financial advisor office.

Visit utah.nm.com

Key Findings

We analyzed Utah.nm.com page load time and found that the first response time was 57 ms and then it took 1.8 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

utah.nm.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

utah.nm.com

57 ms

utah.nm.com

42 ms

148 ms

offices.css

33 ms

launch-EN601ad48fe03a4aa39be269d4d5c2c405.min.js

24 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 577.1 kB (14%)

Content Size

4.0 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Utah.nm.com main page is 4.0 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. Only a small number of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 172.7 kB

  • Original 210.4 kB
  • After minification 201.9 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 172.7 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 104.7 kB

  • Original 3.0 MB
  • After minification 2.9 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. UT Ah Nm images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 299.3 kB

  • Original 792.3 kB
  • After minification 792.1 kB
  • After compression 492.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 299.3 kB or 38% 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. Utah.nm.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (54%)

Requests Now

74

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UT Ah 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 27 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

utah.nm.com

utah.nm.com

57 ms

utah.nm.com

utah.nm.com

42 ms

148 ms

offices.css

offices.css

33 ms

launch-EN601ad48fe03a4aa39be269d4d5c2c405.min.js

launch-EN601ad48fe03a4aa39be269d4d5c2c405.min.js

24 ms

offices.js

offices.js

112 ms

js

js

188 ms

js

js

112 ms

navigation-menu-mobile.svg

navigation-menu-mobile.svg

351 ms

fbevents.js

fbevents.js

153 ms

bat.js

bat.js

343 ms

cancel-x.svg

cancel-x.svg

363 ms

nm-logo-blue.svg

nm-logo-blue.svg

362 ms

navigation-search-inactive-mobile.svg

navigation-search-inactive-mobile.svg

359 ms

new-navigation-search-active-mobile.svg

new-navigation-search-active-mobile.svg

358 ms

navigation-chevron-blue-right-mobile.svg

navigation-chevron-blue-right-mobile.svg

468 ms

navigation-chevron-left-grey-mobile.svg

navigation-chevron-left-grey-mobile.svg

359 ms

navigation-search-reverse.svg

navigation-search-reverse.svg

561 ms

navigation-search-active.svg

navigation-search-active.svg

470 ms

handshake.svg

handshake.svg

563 ms

chevron-right-blue.svg

chevron-right-blue.svg

481 ms

nav-active-carret-blue.svg

nav-active-carret-blue.svg

471 ms

nav-inactive-carret-blue.svg

nav-inactive-carret-blue.svg

684 ms

father-with-his-daughter.jpg

father-with-his-daughter.jpg

586 ms

77fed425-5640-4d00-b152-bff4e9be08fd.jpeg

77fed425-5640-4d00-b152-bff4e9be08fd.jpeg

845 ms

expert-partner.svg

expert-partner.svg

540 ms

point-to-point.svg

point-to-point.svg

673 ms

gold-star.svg

gold-star.svg

679 ms

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

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

681 ms

handshake-reverse.svg

handshake-reverse.svg

681 ms

man-with-flag.svg

man-with-flag.svg

683 ms

rocket.svg

rocket.svg

845 ms

supporting-photo-apply-now-v4.jpg

supporting-photo-apply-now-v4.jpg

846 ms

nametag-reverse.svg

nametag-reverse.svg

852 ms

supporting-photo-giving-back.jpg

supporting-photo-giving-back.jpg

856 ms

supporting-photo-nm-stats.jpg

supporting-photo-nm-stats.jpg

864 ms

map-marker.svg

map-marker.svg

854 ms

other-locations-blue-bar.svg

other-locations-blue-bar.svg

853 ms

chevron-right.svg

chevron-right.svg

852 ms

id

id

125 ms

AppMeasurement.min.js

AppMeasurement.min.js

98 ms

AppMeasurement_Module_ActivityMap.min.js

AppMeasurement_Module_ActivityMap.min.js

114 ms

insight.min.js

insight.min.js

282 ms

heap-3637159320.js

heap-3637159320.js

300 ms

staticmap

staticmap

258 ms

staticmap

staticmap

256 ms

staticmap

staticmap

256 ms

chevron-up.svg

chevron-up.svg

907 ms

dropdown-arrow.svg

dropdown-arrow.svg

909 ms

dropdown-arrow-open.svg

dropdown-arrow-open.svg

908 ms

chevron-left-grey.svg

chevron-left-grey.svg

913 ms

GuardianSans-Regular.woff

GuardianSans-Regular.woff

238 ms

GuardianSans-Light.woff

GuardianSans-Light.woff

238 ms

GuardianSans-Thin.woff

GuardianSans-Thin.woff

240 ms

GuardianSans-Medium.woff

GuardianSans-Medium.woff

237 ms

GuardianSans-SemiBold.woff

GuardianSans-SemiBold.woff

235 ms

otSDKStub.js

otSDKStub.js

286 ms

dest5.html

dest5.html

319 ms

287689728264317

287689728264317

180 ms

25058490.js

25058490.js

80 ms

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

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

28 ms

ibs:dpid=411&dpuuid=ZtQungAAAHbqbQNw

ibs:dpid=411&dpuuid=ZtQungAAAHbqbQNw

11 ms

location

location

50 ms

js

js

19 ms

js

js

48 ms

js

js

137 ms

js

js

134 ms

js

js

133 ms

otBannerSdk.js

otBannerSdk.js

18 ms

5564967.js

5564967.js

14 ms

en.json

en.json

97 ms

198 ms

197 ms

js

js

206 ms

analytics.js

analytics.js

72 ms

otFlat.json

otFlat.json

36 ms

otPcPanel.json

otPcPanel.json

59 ms

otCommonStyles.css

otCommonStyles.css

30 ms

uwt.js

uwt.js

131 ms

collect

collect

114 ms

ot_close.svg

ot_close.svg

97 ms

nm-navy-200x40-2x.png

nm-navy-200x40-2x.png

59 ms

Accessibility Review

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

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

utah.nm.com SEO score

79

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 uses 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 Utah.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 Utah.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

utah.nm.com

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