Tools & Wizards About Us
woodland.bank screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

woodland.bank

Woodland Bank | Personal & Business Banking

Page Load Speed

2.6 sec in total

First Response

112 ms

Resources Loaded

2.3 sec

Page Rendered

175 ms

woodland.bank screenshot

About Website

Click here to check amazing Woodland content. Otherwise, check out these important facts you probably never knew about woodland.bank

Woodland bank is committed to serving the needs of its communities and the vibrant economy in the Grand Rapids, Minnesota market.

Visit woodland.bank

Key Findings

We analyzed Woodland.bank page load time and found that the first response time was 112 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

woodland.bank performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.165

72/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

woodland.bank

112 ms

www.woodland.bank

88 ms

custom.min.css

56 ms

siteAlertDefault.css

427 ms

all.min.js

99 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 31% of them (11 requests) were addressed to the original Woodland.bank, 23% (8 requests) were made to Cdn.firstbranchcms.com and 9% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (762 ms) relates to the external source Cdn.firstbranchcms.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.4 kB (7%)

Content Size

629.6 kB

After Optimization

583.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Woodland.bank main page is 629.6 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. 55% of websites need less resources to load. Images take 491.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 46.1 kB

  • Original 54.4 kB
  • After minification 53.9 kB
  • After compression 8.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. 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 46.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 50 B

  • Original 491.2 kB
  • After minification 491.1 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. Woodland images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 188 B

  • Original 22.0 kB
  • After minification 22.0 kB
  • After compression 21.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 111 B

  • Original 62.1 kB
  • After minification 62.1 kB
  • After compression 62.0 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. Woodland.bank has all CSS files already compressed.

Requests Breakdown

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

Requests Now

28

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

woodland.bank

woodland.bank

112 ms

www.woodland.bank

www.woodland.bank

88 ms

custom.min.css

custom.min.css

56 ms

siteAlertDefault.css

siteAlertDefault.css

427 ms

all.min.js

all.min.js

99 ms

RemoteLogon

RemoteLogon

168 ms

compliance-logos.js

compliance-logos.js

98 ms

warning.js

warning.js

41 ms

audioeye-api.js

audioeye-api.js

95 ms

css

css

94 ms

css

css

110 ms

fbevents.js

fbevents.js

165 ms

pendo.js

pendo.js

352 ms

gtm.js

gtm.js

308 ms

desktopImage.png

desktopImage.png

504 ms

desktopImage.jpeg

desktopImage.jpeg

523 ms

desktopImage.jpeg

desktopImage.jpeg

518 ms

image.png

image.png

699 ms

icon.png

icon.png

703 ms

icon.png

icon.png

762 ms

icon.png

icon.png

704 ms

icon.png

icon.png

739 ms

logo-2x.png

logo-2x.png

441 ms

bg-pattern.jpg

bg-pattern.jpg

150 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

206 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

231 ms

fa-solid-900.woff

fa-solid-900.woff

240 ms

XoHo2YL_S7-g5rsqITc.woff

XoHo2YL_S7-g5rsqITc.woff

381 ms

fa-brands-400.woff

fa-brands-400.woff

176 ms

print.css

print.css

40 ms

aem.js

aem.js

42 ms

6c77c00c-077f-43ba-5267-43d26a27a4c2

6c77c00c-077f-43ba-5267-43d26a27a4c2

174 ms

6c77c00c-077f-43ba-5267-43d26a27a4c2

6c77c00c-077f-43ba-5267-43d26a27a4c2

93 ms

6c77c00c-077f-43ba-5267-43d26a27a4c2

6c77c00c-077f-43ba-5267-43d26a27a4c2

91 ms

bootstrap.js

bootstrap.js

268 ms

Accessibility Review

woodland.bank accessibility score

100

Accessibility Issues

Best Practices

woodland.bank best practices score

83

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

Browser errors were logged to the console

SEO Factors

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Woodland.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 Woodland.bank main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

woodland.bank

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