3.3 sec in total
358 ms
2.6 sec
261 ms
Click here to check amazing Nb Financial content for Canada. Otherwise, check out these important facts you probably never knew about nbfinancial.com
Your investment advisor will make your money work for you so you can relax and live life to the fullest!
Visit nbfinancial.comWe analyzed Nbfinancial.com page load time and found that the first response time was 358 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.
nbfinancial.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value14.1 s
0/100
25%
Value7.5 s
26/100
10%
Value1,290 ms
18/100
30%
Value0.014
100/100
15%
Value8.6 s
37/100
10%
358 ms
460 ms
494 ms
372 ms
25 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Nbfinancial.com, 2% (1 request) were made to Assets.adobedtm.com and 2% (1 request) were made to S.go-mpulse.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Nbfwm.ca.
Page size can be reduced by 1.2 MB (43%)
2.8 MB
1.6 MB
In fact, the total size of Nbfinancial.com main page is 2.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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 217.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. 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 217.2 kB or 90% of the original size.
Potential reduce by 168.9 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, Nb Financial needs image optimization as it can save up to 168.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 128.1 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 128.1 kB or 28% of the original size.
Potential reduce by 712.2 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. Nbfinancial.com needs all CSS files to be minified and compressed as it can save up to 712.2 kB or 86% of the original size.
Number of requests can be reduced by 35 (66%)
53
18
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nb Financial. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.nbfwm.ca
358 ms
base.min.3f56e989e786c643b30d5668a97daa52.js
460 ms
websites.min.afe369e2daa031e232e9e25e1415ac64.js
494 ms
dataLayer.min.e63d292fd1f70097ff0a7e8254245e81.js
372 ms
launch-ENce80544c76a04686ae546c50bbd9979e.min.js
25 ms
clientlib-core-components.min.92ac67899fe3d5f4241b959add6754f8.css
561 ms
clientlib-dependencies.min.e8e8c2ccd7e4637d6fecf48ffeddbf45.js
520 ms
clientlib-base.min.fe820b99b615c60d012a61d56eefc89a.js
296 ms
clientlib-base.min.b9e58db3c42afa6e5488f495d4804f33.css
578 ms
theme.min.10ebccde8134240084bdd6fa4c27dc18.css
620 ms
fbngp.css
670 ms
clientlib.min.6ec3856b6df87ee1685172fb40c69188.css
717 ms
clientlib.min.b3e2103e5f112609157e93cd4c4c3dd1.css
720 ms
lodash.min.a98e817fa80e9f0446305f835cdaa621.js
644 ms
react.min.45e0671f00ea10ecf34e891cd69b1f90.js
716 ms
clientlib.min.988c757c47b8953b6df51824069f116d.js
748 ms
eventListenerHandlers.min.6da5ec95ff88986fe5a678195fb73f2e.js
1092 ms
basepage.min.3097d244e3acdaa1cc46cbe27a844341.js
784 ms
sticky.min.f7421d1f70d92b9a74fb9655256bba54.js
873 ms
clientlib.min.bd469e5cc18b0da120c122925e27d76d.js
1001 ms
textandimage.min.9c820de2cd8bf947380bedee97d56688.js
915 ms
lightbox.min.52a11ac88f03e7666b3215ec7235efb2.css
891 ms
lightbox.min.247e04eae056fe5567a1503aa2fe6b77.js
951 ms
modal.min.9457654facd5992c898d0b9d071341f8.css
973 ms
modal.min.ec1acb2c245793c9aca006b573a1c26e.js
953 ms
clientlib.min.60c616f6d42d7869b8a5943fbf3fc194.css
1032 ms
clientlib.min.1237b86dce2f06de7f5cbc7bdb766e2a.css
1044 ms
clientlib.min.e608268427093228dec948a90f1526fd.js
1154 ms
jquery-sticky-1-0-4.min.b245ebc9b251955a08c1cf747a222d10.js
1084 ms
stickyBehavior.min.81a4b9df09c15476124998587316faed.js
1206 ms
site.min.8bd3357c8782030bd34e3822ff5765c2.js
1123 ms
site.min.105741b41766cc59fef14e6b39edcf68.js
1293 ms
collapse-responsive.min.2fd59c4cde072fa25ef470d63a9d7fda.js
1157 ms
layout-patch.css
1155 ms
container.min.0a6aff292f5cc42142779cde92054524.js
1460 ms
clientlib-core-components.min.0e78d12b97b3829e02f2e042879f70aa.js
1233 ms
responsiveBootstrapToolkit.min.afc2afb52200829364788f6cc6d3a5ec.js
1234 ms
rules-fbngp.json
547 ms
CBWCH-YHXC8-UX5PM-CKJ3F-WKW7N
26 ms
logo-nbfwm-245x70.png
987 ms
thumb-rich-fuller-life-277x186.png
654 ms
img-family-at-home-en.jpeg
788 ms
img-couple-gardening-en.jpeg
790 ms
thumb-lasting-legacy-277x186.png
1234 ms
img-piblications-financieres-740x400.png
834 ms
img-celiapp-fbngp.svg
790 ms
icons-products-and-services-two-tone-question-80x80.svg
792 ms
picto-telephone-rouge-80x80-5.png
833 ms
picto-logo-bn-24x22.png
816 ms
Gilroy-Regular.woff
799 ms
Gilroy-Regular.woff
899 ms
config.json
56 ms
Gilroy-SemiBold.woff
885 ms
Gilroy-SemiBold.woff
862 ms
Gilroy-Light.woff
833 ms
Gilroy-Light.woff
793 ms
logo-ciro.svg
799 ms
logo-cipf.svg
803 ms
logo-fcpe-microsites-en-v2.svg
733 ms
Gilroy-Medium.woff
570 ms
Gilroy-Medium.woff
701 ms
Gilroy-UltraLight.woff
610 ms
Gilroy-UltraLight.woff
629 ms
Gilroy-Bold.woff
632 ms
Gilroy-Bold.woff
651 ms
ban-homepage-fbngp-2000x375.jpg
237 ms
nbfinancial.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
nbfinancial.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
nbfinancial.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 Nbfinancial.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 Nbfinancial.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.
nbfinancial.com
Open Graph description is not detected on the main page of Nb Financial. 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: