Tools & Wizards About Us
northrim.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

northrim.com

Powering the businesses that power Alaska

Page Load Speed

3.7 sec in total

First Response

692 ms

Resources Loaded

2.8 sec

Page Rendered

212 ms

northrim.com screenshot

About Website

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

Northrim Bank is a full-service community bank headquartered in Alaska.

Visit northrim.com

Key Findings

We analyzed Northrim.com page load time and found that the first response time was 692 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

northrim.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.492

17/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

home

692 ms

jquery-1_7_2.js

266 ms

global.js

537 ms

usp_behavior.js

216 ms

rollovers.js

212 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 90% of them (60 requests) were addressed to the original Northrim.com, 3% (2 requests) were made to Drs.digitalinsight.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Northrim.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 448.4 kB (24%)

Content Size

1.8 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Northrim.com main page is 1.8 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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 29.4 kB

  • Original 36.5 kB
  • After minification 30.0 kB
  • After compression 7.2 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 6.5 kB, which is 18% 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 29.4 kB or 80% of the original size.

Image Optimization

-12%

Potential reduce by 175.9 kB

  • Original 1.4 MB
  • After minification 1.2 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. Obviously, Northrim needs image optimization as it can save up to 175.9 kB or 12% 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 228.8 kB

  • Original 360.0 kB
  • After minification 344.3 kB
  • After compression 131.2 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 228.8 kB or 64% of the original size.

CSS Optimization

-79%

Potential reduce by 14.3 kB

  • Original 18.1 kB
  • After minification 12.5 kB
  • After compression 3.9 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. Northrim.com needs all CSS files to be minified and compressed as it can save up to 14.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (22%)

Requests Now

64

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

home

home

692 ms

jquery-1_7_2.js

jquery-1_7_2.js

266 ms

global.js

global.js

537 ms

usp_behavior.js

usp_behavior.js

216 ms

rollovers.js

rollovers.js

212 ms

jquery.DIMenus.js

jquery.DIMenus.js

299 ms

_script.js

_script.js

359 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

280 ms

fi_styles.css

fi_styles.css

281 ms

_styles.css

_styles.css

332 ms

menu.css

menu.css

342 ms

drs-1.0.min.js

drs-1.0.min.js

562 ms

jquery_AnimateTrigger-1_1.js

jquery_AnimateTrigger-1_1.js

345 ms

jquery.PromoRotator.js

jquery.PromoRotator.js

361 ms

grp.js

grp.js

395 ms

s_code.js

s_code.js

509 ms

s_ifidConfig.js

s_ifidConfig.js

411 ms

analytics.js

analytics.js

82 ms

description.jsonp

description.jsonp

78 ms

bg_body.gif

bg_body.gif

77 ms

bg_mast.png

bg_mast.png

204 ms

logo_northrimbank.png

logo_northrimbank.png

80 ms

achievemore.png

achievemore.png

80 ms

pnav_dblborder.png

pnav_dblborder.png

77 ms

pnav_personal_off.gif

pnav_personal_off.gif

77 ms

pnav_business_off.gif

pnav_business_off.gif

137 ms

pnav_about_off.gif

pnav_about_off.gif

140 ms

pnav_contact_off.gif

pnav_contact_off.gif

140 ms

bg_searchbar.png

bg_searchbar.png

139 ms

bg_search.gif

bg_search.gif

143 ms

btn_search.png

btn_search.png

204 ms

bg_content.png

bg_content.png

1133 ms

bg_loginhome.png

bg_loginhome.png

206 ms

ttl_personalbanking.png

ttl_personalbanking.png

207 ms

bg_field_user.png

bg_field_user.png

211 ms

bg_field_pw.png

bg_field_pw.png

269 ms

btn_iblogin_off.png

btn_iblogin_off.png

270 ms

ttl_businessbanking.png

ttl_businessbanking.png

273 ms

btn_loginlarge_off.png

btn_loginlarge_off.png

273 ms

ttl_creditcards.png

ttl_creditcards.png

279 ms

banner-northrim-bank-alaskanomics.gif

banner-northrim-bank-alaskanomics.gif

335 ms

banner-northrim-bank-supporting-what-matters.jpg

banner-northrim-bank-supporting-what-matters.jpg

469 ms

banner-northrim-bank-business-loans-expansion.jpg

banner-northrim-bank-business-loans-expansion.jpg

537 ms

promo-previousArrow.png

promo-previousArrow.png

338 ms

promo-nextArrow.png

promo-nextArrow.png

348 ms

icon_fb.png

icon_fb.png

403 ms

icon_twitter.png

icon_twitter.png

405 ms

icon_alaskanomics.png

icon_alaskanomics.png

417 ms

bg_newsfade.png

bg_newsfade.png

471 ms

Northrim-Bank-Earn-Miles-Referral-Program.gif

Northrim-Bank-Earn-Miles-Referral-Program.gif

472 ms

cy-protected.png

cy-protected.png

486 ms

logo_memberfdic.png

logo_memberfdic.png

537 ms

ehl_40x35_k_50.png

ehl_40x35_k_50.png

539 ms

page_capBttm.png

page_capBttm.png

539 ms

grp_settings.js2

grp_settings.js2

535 ms

collect

collect

12 ms

jquery_intuit_acc_mobile_t2d.js

jquery_intuit_acc_mobile_t2d.js

533 ms

bg_homenews.png

bg_homenews.png

829 ms

dhtml_topPointer.png

dhtml_topPointer.png

827 ms

pnav_personal_on.gif

pnav_personal_on.gif

828 ms

pnav_business_on.gif

pnav_business_on.gif

830 ms

collect

collect

60 ms

pnav_about_on.gif

pnav_about_on.gif

774 ms

pnav_contact_on.gif

pnav_contact_on.gif

772 ms

ga-audiences

ga-audiences

32 ms

s88333214069716

s88333214069716

41 ms

btn_loginlarge_on.png

btn_loginlarge_on.png

68 ms

Accessibility Review

northrim.com accessibility score

82

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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 IDs are not unique

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best Practices

northrim.com best practices score

58

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

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

northrim.com SEO score

74

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

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

northrim.com

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