4.8 sec in total
335 ms
4.2 sec
274 ms
Click here to check amazing Secure Ecobank content for Senegal. Otherwise, check out these important facts you probably never knew about secure.ecobank.com
A regional commercial bank operating in many African countries.
Visit secure.ecobank.comWe analyzed Secure.ecobank.com page load time and found that the first response time was 335 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
secure.ecobank.com performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value14.5 s
0/100
25%
Value11.5 s
5/100
10%
Value900 ms
31/100
30%
Value0.001
100/100
15%
Value14.3 s
9/100
10%
335 ms
104 ms
1294 ms
17 ms
248 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 84% of them (69 requests) were addressed to the original Secure.ecobank.com, 6% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Secure.ecobank.com.
Page size can be reduced by 1.0 MB (52%)
1.9 MB
914.3 kB
In fact, the total size of Secure.ecobank.com main page is 1.9 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. 55% of websites need less resources to load. HTML takes 1.5 MB which makes up the majority of the site volume.
Potential reduce by 791.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 791.7 kB or 51% of the original size.
Potential reduce by 12.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. Obviously, Secure Ecobank needs image optimization as it can save up to 12.1 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 5.9 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 198.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. Secure.ecobank.com needs all CSS files to be minified and compressed as it can save up to 198.4 kB or 84% of the original size.
Number of requests can be reduced by 33 (49%)
68
35
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Secure Ecobank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
secure.ecobank.com
335 ms
personal-banking
104 ms
login
1294 ms
ai.0.js
17 ms
dropzone.css
248 ms
animate.css
256 ms
css
33 ms
feedbackReport.min.css
252 ms
slidercaptcha.css
285 ms
_ecoStyle.min.css
842 ms
app.min.css
999 ms
dropzone.min.css
343 ms
EcoAllStyles.min.css
675 ms
foundation-datepicker.min.css
382 ms
multi-select.css
481 ms
real-person.css
524 ms
smartbanner.min.css
580 ms
themify-icons.css
614 ms
timeAccess.css
640 ms
timeAccess.min.css
837 ms
site24x7rum-min.js
232 ms
font-awesome.min.css
553 ms
WebResource.axd
294 ms
WebResource.axd
450 ms
longbow.slidercaptcha.js
448 ms
eco-logo-svg.svg
158 ms
WhistleblowingB-icon.png
1187 ms
20160902103106042_zGW87s885m.svg
157 ms
login-slide-help.gif
1819 ms
202403140429029781.png
708 ms
azn-logo-transparent.png
161 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
68 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
68 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
131 ms
KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf
138 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
139 ms
20170801025449386_V5U9EfZVNd.svg
175 ms
20160519020429807_qh3wh5p2ee.svg
666 ms
20160519020640697_83pE2r8Nzz.svg
192 ms
20160519021020025_wcD9s9m8rw.svg
419 ms
20160519020741260_1wf7vh1Ets.svg
425 ms
20160519020904291_B5rH5tAQ22.svg
428 ms
20160519021144838_vq91pbv7kk.svg
431 ms
20160519021328213_6ZJcYM6kVV.svg
446 ms
20160519021736010_9QtM5pXn49.svg
506 ms
20160519021553541_WRA4QCWbMM.svg
536 ms
20160519022506182_HCyQB0HX98.svg
593 ms
20160519021920119_60kB0n5Jxw.svg
627 ms
20160519015911685_ng2uf4n0cc.svg
693 ms
20160519022027511_wcC9r9k7qv.svg
717 ms
20160519022406104_jcWqcYhx98.svg
760 ms
20160519022148822_8rRn3NyK27.svg
752 ms
20160519022239921_94qF3s9P00.svg
794 ms
20160519023156603_b6Qh5Sbr22.svg
807 ms
20160519023111541_QJ4WH6Q5FE.svg
839 ms
20160519023303604_50kBzn5Jww.svg
862 ms
20160519030131260_H2zrEA71Y8.svg
894 ms
20160519015506744_2VE8UG2fSR.svg
898 ms
20160519024039260_S8b5N7G6MS.svg
931 ms
20160519024305781_tn7zn9t6jh.svg
962 ms
20160519023810588_YTC6SEYdPP.svg
994 ms
20160519024413447_rj4wj6q3fe.svg
987 ms
20191111043844894_FAwN9yFU66.png
1017 ms
20160519024859041_F9vN9xEU66.svg
1564 ms
20160519025553588_ZUD7TFZeQQ.svg
1076 ms
20160519025316777_r96XnjD96D.svg
1094 ms
FontAwesomeBrands-Regular-webfont.woff
1092 ms
BlackTie-Regular-webfont.woff
1059 ms
BlackTie-Light-webfont.woff
1091 ms
ga.js
34 ms
BlackTie-Solid-webfont.woff
1070 ms
sdk.js
232 ms
fontawesome-webfont.woff
1084 ms
__utm.gif
164 ms
feedbackHandler.ashx
1006 ms
20160519025111557_j22Xez9xdj.svg
897 ms
20160519025206182_P572H4C2GN.svg
905 ms
sdk.js
8 ms
20160519025359463_ytc4seyBqp.svg
947 ms
68 ms
sidebar-V4.png
911 ms
logPic4.jpg
943 ms
secure.ecobank.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
secure.ecobank.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
secure.ecobank.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 Secure.ecobank.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 Secure.ecobank.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.
secure.ecobank.com
Open Graph data is detected on the main page of Secure Ecobank. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: