3.4 sec in total
479 ms
2.8 sec
122 ms
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.bankWe analyzed Woodland.bank page load time and found that the first response time was 479 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
woodland.bank performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value13.5 s
0/100
25%
Value8.6 s
17/100
10%
Value3,830 ms
1/100
30%
Value0.081
94/100
15%
Value18.1 s
3/100
10%
479 ms
335 ms
350 ms
421 ms
85 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 19% of them (10 requests) were addressed to the original Woodland.bank, 15% (8 requests) were made to Cdn.firstbranchcms.com and 9% (5 requests) were made to Libs.coremetrics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cdn.firstbranchcms.com.
Page size can be reduced by 65.3 kB (7%)
879.6 kB
814.3 kB
In fact, the total size of Woodland.bank main page is 879.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. 65% of websites need less resources to load. Images take 510.7 kB which makes up the majority of the site volume.
Potential reduce by 59.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 59.7 kB or 78% of the original size.
Potential reduce by 50 B
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.
Potential reduce by 5.4 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.
Potential reduce by 111 B
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.
Number of requests can be reduced by 28 (60%)
47
19
The browser has sent 47 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 25 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.woodland.bank
479 ms
custom.min.css
335 ms
siteAlertDefault.css
350 ms
all.min.js
421 ms
eluminate.js
85 ms
RemoteLogon
202 ms
compliance-logos.js
347 ms
warning.js
326 ms
audioeye-api.js
356 ms
css
27 ms
css
38 ms
fbevents.js
14 ms
head.js
60 ms
90331489.js
13 ms
90415528.js
123 ms
print.css
445 ms
dispatcher-v3.js
109 ms
pendo.js
99 ms
gtm.js
247 ms
desktopImage.png
656 ms
desktopImage.jpeg
1123 ms
desktopImage.jpeg
1143 ms
image.png
845 ms
icon.png
856 ms
icon.png
887 ms
icon.png
843 ms
icon.png
1053 ms
logo-2x.png
395 ms
bg-pattern.jpg
366 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
154 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
154 ms
fa-solid-900.woff
327 ms
XoHo2YL_S7-g5rsqITcnvd8p.woff
187 ms
yahoo-min.js
91 ms
cp-v3.js
90 ms
cm
149 ms
fa-brands-400.woff
361 ms
json-min.js
33 ms
destination
64 ms
up_loader.1.1.0.js
68 ms
aem.js
55 ms
6c77c00c-077f-43ba-5267-43d26a27a4c2
141 ms
6c77c00c-077f-43ba-5267-43d26a27a4c2
72 ms
6c77c00c-077f-43ba-5267-43d26a27a4c2
80 ms
js
73 ms
analytics.js
25 ms
bootstrap.js
38 ms
linkid.js
12 ms
collect
36 ms
collect
48 ms
collect
38 ms
js
44 ms
ga-audiences
63 ms
woodland.bank accessibility score
woodland.bank best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
woodland.bank SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
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 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.
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: