2 sec in total
157 ms
1.5 sec
421 ms
Click here to check amazing Natbank content for Canada. Otherwise, check out these important facts you probably never knew about natbank.com
Looking for local support with your real estate purchases and USD transactions in Florida? Choose Natbank, National Bank of Canada's subsidiary in Florida.
Visit natbank.comWe analyzed Natbank.com page load time and found that the first response time was 157 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
natbank.com performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value11.1 s
0/100
25%
Value6.0 s
47/100
10%
Value1,920 ms
8/100
30%
Value0
100/100
15%
Value12.2 s
15/100
10%
157 ms
88 ms
33 ms
22 ms
24 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Natbank.com, 1% (1 request) were made to Assets.adobedtm.com and 1% (1 request) were made to S.go-mpulse.net. The less responsive or slowest element that took the longest time to load (260 ms) relates to the external source Nbc.ca.
Page size can be reduced by 1.4 MB (43%)
3.2 MB
1.8 MB
In fact, the total size of Natbank.com main page is 3.2 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. 80% 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.6 MB which makes up the majority of the site volume.
Potential reduce by 199.6 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 199.6 kB or 89% of the original size.
Potential reduce by 215.8 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. Obviously, Natbank needs image optimization as it can save up to 215.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 227.5 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 227.5 kB or 41% of the original size.
Potential reduce by 727.4 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. Natbank.com needs all CSS files to be minified and compressed as it can save up to 727.4 kB or 86% of the original size.
Number of requests can be reduced by 38 (63%)
60
22
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Natbank. 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 from 13 to 1 for CSS and as a result speed up the page load time.
natbank.html
157 ms
personal.html
88 ms
base.min.3f56e989e786c643b30d5668a97daa52.js
33 ms
websites.min.afe369e2daa031e232e9e25e1415ac64.js
22 ms
dataLayer.min.e63d292fd1f70097ff0a7e8254245e81.js
24 ms
launch-ENce80544c76a04686ae546c50bbd9979e.min.js
199 ms
clientlib-core-components.min.92ac67899fe3d5f4241b959add6754f8.css
27 ms
clientlib-dependencies.min.e8e8c2ccd7e4637d6fecf48ffeddbf45.js
22 ms
clientlib-base.min.fe820b99b615c60d012a61d56eefc89a.js
31 ms
clientlib-base.min.b9e58db3c42afa6e5488f495d4804f33.css
70 ms
theme.min.10ebccde8134240084bdd6fa4c27dc18.css
82 ms
clientlib.min.6ec3856b6df87ee1685172fb40c69188.css
75 ms
clientlib.min.b3e2103e5f112609157e93cd4c4c3dd1.css
76 ms
lodash.min.a98e817fa80e9f0446305f835cdaa621.js
79 ms
react.min.45e0671f00ea10ecf34e891cd69b1f90.js
79 ms
clientlib.min.6538b2e30bc8dab5296e7c166d97a2e5.js
79 ms
eventListenerHandlers.min.6da5ec95ff88986fe5a678195fb73f2e.js
79 ms
basepage.min.3097d244e3acdaa1cc46cbe27a844341.js
79 ms
sticky.min.f7421d1f70d92b9a74fb9655256bba54.js
260 ms
clientlib.min.6497776e1ddfc4aa7d7ce52e5854baf7.js
193 ms
textandimage.min.9c820de2cd8bf947380bedee97d56688.js
191 ms
lightbox.min.52a11ac88f03e7666b3215ec7235efb2.css
191 ms
lightbox.min.247e04eae056fe5567a1503aa2fe6b77.js
191 ms
modal.min.9457654facd5992c898d0b9d071341f8.css
192 ms
modal.min.ec1acb2c245793c9aca006b573a1c26e.js
195 ms
clientlib.min.60c616f6d42d7869b8a5943fbf3fc194.css
192 ms
clientlib.min.1237b86dce2f06de7f5cbc7bdb766e2a.css
193 ms
clientlib.min.e608268427093228dec948a90f1526fd.js
194 ms
container.min.0a6aff292f5cc42142779cde92054524.js
190 ms
site.min.c254b351182288a72fbd32db1f3a5320.js
196 ms
site.min.f6c1348a612942645a5181a642bcadb4.css
195 ms
clientlibs.min.90932f7188b6de3499a57fd9afe1ddb6.css
193 ms
jquery-sticky-1-0-4.min.b245ebc9b251955a08c1cf747a222d10.js
193 ms
stickyBehavior.min.81a4b9df09c15476124998587316faed.js
192 ms
site.min.8bd3357c8782030bd34e3822ff5765c2.js
193 ms
site.min.105741b41766cc59fef14e6b39edcf68.js
194 ms
layout-patch.css
194 ms
clientlib-core-components.min.0e78d12b97b3829e02f2e042879f70aa.js
202 ms
clientlibs.min.45c8405990e282ad898ca78dc2694ca6.css
201 ms
clientlibs.min.9c2c78e235436750528520027b4fd123.js
189 ms
responsiveBootstrapToolkit.min.afc2afb52200829364788f6cc6d3a5ec.js
189 ms
rules-natbank.json
122 ms
CBWCH-YHXC8-UX5PM-CKJ3F-WKW7N
101 ms
logo-natbank-mobile-200x47.png
88 ms
img-bloc-comptes-374x259.png
67 ms
img-bloc-cartes-374x259.png
84 ms
img-bloc-financement-374x259.png
85 ms
img-service-conseiller.svg
89 ms
img-cheque-deposit.svg
101 ms
img-zelle.svg
96 ms
img-virement-international.svg
105 ms
img-docusign.jpg
99 ms
img-guichet-automatique.jpg
163 ms
picto-adisors-xl-96x96.svg
125 ms
picto-phone-xl-96x96.svg
112 ms
picto-fdic-264x21.png
110 ms
picto-logo-bn-24x22.png
106 ms
Gilroy-Regular.woff
102 ms
Gilroy-Regular.woff
192 ms
Gilroy-Medium.woff
114 ms
Gilroy-Medium.woff
134 ms
Gilroy-SemiBold.woff
134 ms
Gilroy-SemiBold.woff
194 ms
Gilroy-Light.woff
136 ms
Gilroy-Light.woff
174 ms
config.json
135 ms
img-video-securenow.jpeg
115 ms
video.png
62 ms
img-amis-discutent-cafe-572x350.jpeg
55 ms
ban-natbank-part-hub-2000x375.jpg
56 ms
fontawesome-webfont.woff
40 ms
fontawesome-webfont.woff
23 ms
natbank.com accessibility score
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
[aria-*] attributes do not match their roles
[aria-*] attributes do not have valid values
natbank.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
natbank.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Natbank.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 Natbank.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.
natbank.com
Open Graph description is not detected on the main page of Natbank. 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: