3.4 sec in total
353 ms
2.8 sec
257 ms
Visit nordea.ee now to see the best up-to-date Nordea content for Estonia and also check out these interesting facts you probably never knew about nordea.ee
In Estonia, our multinational and multilingual teams provide high-quality service, data and support for our business units in the Nordics. We cover various banking areas and have teams that work withi...
Visit nordea.eeWe analyzed Nordea.ee page load time and found that the first response time was 353 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
nordea.ee performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value9.7 s
0/100
25%
Value10.3 s
8/100
10%
Value5,370 ms
0/100
30%
Value0.013
100/100
15%
Value11.2 s
20/100
10%
353 ms
761 ms
343 ms
238 ms
582 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 23% of them (15 requests) were addressed to the original Nordea.ee, 42% (27 requests) were made to Cdnnordea.com and 11% (7 requests) were made to 40515350444d1369ff68-2f7735d5ad283fa41a203a082d9a8f25.ssl.cf3.rackcdn.com. The less responsive or slowest element that took the longest time to load (845 ms) belongs to the original domain Nordea.ee.
Page size can be reduced by 1.0 MB (59%)
1.7 MB
710.7 kB
In fact, the total size of Nordea.ee main page is 1.7 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. 30% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 49.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 49.3 kB or 79% of the original size.
Potential reduce by 72.4 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, Nordea needs image optimization as it can save up to 72.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 825.6 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 825.6 kB or 83% of the original size.
Potential reduce by 61.1 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. Nordea.ee needs all CSS files to be minified and compressed as it can save up to 61.1 kB or 86% of the original size.
Number of requests can be reduced by 28 (45%)
62
34
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nordea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
nordea.ee
353 ms
www.nordea.ee
761 ms
Webtrends_Redesign_v1-0-0.js
343 ms
webtrends_functions_v1-1-0.js
238 ms
clean.css
582 ms
IconStyles.ashx
610 ms
CssTmpl.ashx
285 ms
jquery-1.8.2.js
811 ms
jquery-ui-1.10.0.custom.js
836 ms
jquery.tools.1.2.7.min.js
398 ms
jquery-easing.1.3.js
397 ms
jquery-easylist.js
512 ms
jquery-equalizer.js
513 ms
jquery-megamenu.js
587 ms
swfobject_v-2-2.js
626 ms
initiate-javascripts.js
624 ms
jquery-lavalamp.1.3.5.js
626 ms
default.js
693 ms
9714d44c_panel-et.js
248 ms
wtid.js
20 ms
all-sprite.png
675 ms
nordea-logo.png
117 ms
eraklient_MiksValidaNordea.jpg
469 ms
kliendiprogramm2.jpg
322 ms
icon_popup.gif
229 ms
If_kasko_700x250_mini_EST.jpg
845 ms
kultuurisober.jpg
321 ms
veebikohtumine.jpg
455 ms
noustamine_small.jpg
334 ms
mobiilipank.jpg
450 ms
noustamine.jpg
558 ms
hooandja.jpg
441 ms
topnav-divider.png
129 ms
megamenu-baggrund.png
129 ms
megamenu-login-baggrund.png
128 ms
list-shadows-top.png
128 ms
list-shadows-bottom.png
128 ms
grd-blocks.png
240 ms
tall-right-shadow.png
242 ms
tall-left-shadow.png
232 ms
gtm.js
74 ms
pdf-large.png
174 ms
dcs.gif
29 ms
top-right.png
144 ms
top-left.png
138 ms
bottom-left.png
244 ms
bottom-right.png
252 ms
cat_1_NEW.png
168 ms
present_big.png
155 ms
cat_2_NEW.png
171 ms
cat_3_NEW.png
203 ms
cat_4_NEW.png
204 ms
cat_5_NEW.png
204 ms
conversion_async.js
46 ms
analytics.js
50 ms
fbds.js
9 ms
nordea_ee.html
324 ms
123 ms
75 ms
collect
41 ms
collect
81 ms
31 ms
ad.js
109 ms
sarg=56D48EEC21541724%7C_cdata%3A652697_0
107 ms
21 ms
nordea.ee accessibility score
nordea.ee 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
nordea.ee 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
ET
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nordea.ee can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Estonian language. Our system also found out that Nordea.ee 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.
nordea.ee
Open Graph description is not detected on the main page of Nordea. 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: