Tools & Wizards About Us
border.bank screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

border.bank

Community Banking for Minnesota & North Dakota | Border Bank

Page Load Speed

1.3 sec in total

First Response

48 ms

Resources Loaded

850 ms

Page Rendered

434 ms

border.bank screenshot

About Website

Welcome to border.bank homepage info - get ready to check Border best content for United States right away, or after learning these important things about border.bank

Border Bank has locations extending from Northern Minnesota to Metro Minneapolis, and into North Dakota. Our mission is to provide our customers the highest quality of service. Customer first. Communi...

Visit border.bank

Key Findings

We analyzed Border.bank page load time and found that the first response time was 48 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 25% of websites can load faster.

Performance Metrics

border.bank performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

border.bank

48 ms

www.border.bank

313 ms

gtm.js

108 ms

default.css

33 ms

module.css

45 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 87% of them (74 requests) were addressed to the original Border.bank, 4% (3 requests) were made to Web9.secureinternetbank.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (313 ms) belongs to the original domain Border.bank.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.4 kB (10%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Border.bank 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. 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 50.4 kB

  • Original 67.6 kB
  • After minification 52.8 kB
  • After compression 17.3 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 14.9 kB, which is 22% 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 50.4 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 14.2 kB

  • Original 1.3 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. Border images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 67.2 kB

  • Original 390.9 kB
  • After minification 390.8 kB
  • After compression 323.7 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 67.2 kB or 17% of the original size.

CSS Optimization

-42%

Potential reduce by 54.6 kB

  • Original 129.4 kB
  • After minification 129.4 kB
  • After compression 74.8 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. Border.bank needs all CSS files to be minified and compressed as it can save up to 54.6 kB or 42% of the original size.

Requests Breakdown

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

Requests Now

79

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

border.bank

border.bank

48 ms

www.border.bank

www.border.bank

313 ms

gtm.js

gtm.js

108 ms

default.css

default.css

33 ms

module.css

module.css

45 ms

bootstrap4.css

bootstrap4.css

80 ms

jquery.smartmenus.bootstrap.css

jquery.smartmenus.bootstrap.css

57 ms

MainMenu.css

MainMenu.css

58 ms

kalyan.css

kalyan.css

66 ms

skin.css

skin.css

62 ms

container.css

container.css

52 ms

Style.css

Style.css

68 ms

home.css

home.css

70 ms

Style.css

Style.css

71 ms

Setting.css

Setting.css

90 ms

Theme.css

Theme.css

73 ms

sweetalert.css

sweetalert.css

75 ms

jquery.js

jquery.js

102 ms

jquery-migrate.js

jquery-migrate.js

99 ms

jquery-ui.min.js

jquery-ui.min.js

119 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

98 ms

webAPI.min.js

webAPI.min.js

99 ms

sweetalert.min.js

sweetalert.min.js

100 ms

chat-iframe.css

chat-iframe.css

101 ms

WebResource.axd

WebResource.axd

116 ms

ScriptResource.axd

ScriptResource.axd

116 ms

ScriptResource.axd

ScriptResource.axd

179 ms

dnn.js

dnn.js

181 ms

dnn.modalpopup.js

dnn.modalpopup.js

178 ms

unoslider.dev.js

unoslider.dev.js

180 ms

bootstrap.min.js

bootstrap.min.js

180 ms

jquery.smartmenus.js

jquery.smartmenus.js

192 ms

jquery.smartmenus.bootstrap.js

jquery.smartmenus.bootstrap.js

202 ms

custom.js

custom.js

200 ms

scripts.js

scripts.js

200 ms

dnncore.js

dnncore.js

204 ms

Tooltip.min.js

Tooltip.min.js

205 ms

font-awesome.min.css

font-awesome.min.css

39 ms

css2

css2

47 ms

api.js

api.js

47 ms

remoteLoginLoad

remoteLoginLoad

272 ms

Remoteloginload

Remoteloginload

270 ms

JCSbox.css

JCSbox.css

201 ms

LiveFormMobile.min.js

LiveFormMobile.min.js

177 ms

intlTelInput-jquery.min.js

intlTelInput-jquery.min.js

171 ms

utils.js

utils.js

179 ms

jquery.watermark.min.js

jquery.watermark.min.js

163 ms

jquery.maskMoney.min.js

jquery.maskMoney.min.js

161 ms

strength.min.js

strength.min.js

150 ms

dnn.servicesframework.js

dnn.servicesframework.js

152 ms

dnn.jquery.js

dnn.jquery.js

182 ms

JCSbox.js

JCSbox.js

155 ms

CookieAlert.js

CookieAlert.js

151 ms

WebResource.axd

WebResource.axd

155 ms

WebResource.axd

WebResource.axd

172 ms

WebResource.axd

WebResource.axd

172 ms

WebResource.axd

WebResource.axd

151 ms

AccpuntLogin_Logo.svg

AccpuntLogin_Logo.svg

108 ms

Logo.svg

Logo.svg

111 ms

loginbtn.svg

loginbtn.svg

110 ms

locationicon.svg

locationicon.svg

114 ms

phoneicon.svg

phoneicon.svg

111 ms

searchicon.svg

searchicon.svg

111 ms

triangle.png

triangle.png

112 ms

HP_Hero-OnlineLoanApps-2024.jpg

HP_Hero-OnlineLoanApps-2024.jpg

128 ms

HP_Hero-YourForever-2024.jpg

HP_Hero-YourForever-2024.jpg

125 ms

HP_Hero-OurOffice-Q3-2023_1.jpg

HP_Hero-OurOffice-Q3-2023_1.jpg

104 ms

515MainBox_Personal.jpg

515MainBox_Personal.jpg

93 ms

515MainBox_MyBank.jpg

515MainBox_MyBank.jpg

94 ms

515MainBox_Business.jpg

515MainBox_Business.jpg

100 ms

HP_Computer.svg

HP_Computer.svg

84 ms

eStatements-Home-Image.png

eStatements-Home-Image.png

143 ms

successtories_Wintergreen.jpg

successtories_Wintergreen.jpg

83 ms

loading.gif

loading.gif

77 ms

scrollto-topicon.png

scrollto-topicon.png

75 ms

footerfdicsmall.svg

footerfdicsmall.svg

74 ms

x-twitter1.svg

x-twitter1.svg

82 ms

footerbar_closebutton.png

footerbar_closebutton.png

80 ms

accountlogin_image.svg

accountlogin_image.svg

32 ms

KFOlCnqEu92Fr1MmEU9vAA.woff

KFOlCnqEu92Fr1MmEU9vAA.woff

58 ms

KFOlCnqEu92Fr1MmSU5vAA.woff

KFOlCnqEu92Fr1MmSU5vAA.woff

84 ms

KFOlCnqEu92Fr1MmWUlvAA.woff

KFOlCnqEu92Fr1MmWUlvAA.woff

99 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

36 ms

remoteLoginPost

remoteLoginPost

53 ms

square.png

square.png

12 ms

Accessibility Review

border.bank accessibility score

94

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

button, link, and menuitem elements do not have accessible names.

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

border.bank best practices score

67

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

Displays images with incorrect aspect ratio

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

border.bank SEO score

83

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 Border.bank 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 Border.bank 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

border.bank

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