5.6 sec in total
365 ms
4.4 sec
760 ms
Visit ecobank.com now to see the best up-to-date Ecobank content for Senegal and also check out these interesting facts you probably never knew about ecobank.com
A regional commercial bank operating in many African countries.
Visit ecobank.comWe analyzed Ecobank.com page load time and found that the first response time was 365 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ecobank.com performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value22.3 s
0/100
25%
Value9.8 s
10/100
10%
Value370 ms
71/100
30%
Value0.841
4/100
15%
Value10.6 s
23/100
10%
365 ms
1614 ms
35 ms
233 ms
312 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 88% of them (72 requests) were addressed to the original Ecobank.com, 6% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Ecobank.com.
Page size can be reduced by 1.1 MB (14%)
8.0 MB
6.8 MB
In fact, the total size of Ecobank.com main page is 8.0 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. Images take 6.3 MB which makes up the majority of the site volume.
Potential reduce by 740.9 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 740.9 kB or 52% of the original size.
Potential reduce by 187.3 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. Ecobank images are well optimized though.
Potential reduce by 2.0 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 2.0 kB or 34% of the original size.
Potential reduce by 200.8 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. Ecobank.com needs all CSS files to be minified and compressed as it can save up to 200.8 kB or 90% of the original size.
Number of requests can be reduced by 21 (30%)
70
49
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 4 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
ecobank.com
365 ms
personal-banking
1614 ms
css
35 ms
feedbackReport.min.css
233 ms
app.min.css
312 ms
EcoAllStyles.min.css
645 ms
font-awesome.min.css
235 ms
smartbanner.min.css
263 ms
WebResource.axd
233 ms
font-awesome.min.css
93 ms
leaflet.css
31 ms
leaflet.js
48 ms
eco-logo-svg.svg
130 ms
WhistleblowingB-icon.png
692 ms
20160902103106042_zGW87s885m.svg
132 ms
202403140429029781.png
222 ms
20211114100523336T.png
513 ms
smiley_guy-3.jpg
132 ms
eco_mob.jpg
226 ms
azn-logo-transparent.png
224 ms
20170801025449386_V5U9EfZVNd.svg
182 ms
20160519020429807_qh3wh5p2ee.svg
287 ms
20160519020640697_83pE2r8Nzz.svg
288 ms
20160519021020025_wcD9s9m8rw.svg
290 ms
20160519020741260_1wf7vh1Ets.svg
292 ms
20160519020904291_B5rH5tAQ22.svg
463 ms
20160519021144838_vq91pbv7kk.svg
468 ms
20160519021328213_6ZJcYM6kVV.svg
470 ms
20160519021736010_9QtM5pXn49.svg
472 ms
20160519021553541_WRA4QCWbMM.svg
474 ms
20160519022506182_HCyQB0HX98.svg
476 ms
20160519021920119_60kB0n5Jxw.svg
479 ms
20160519015911685_ng2uf4n0cc.svg
481 ms
20160519022027511_wcC9r9k7qv.svg
492 ms
20160519022406104_jcWqcYhx98.svg
532 ms
20160519022148822_8rRn3NyK27.svg
535 ms
20160519022239921_94qF3s9P00.svg
538 ms
20160519023156603_b6Qh5Sbr22.svg
541 ms
20160519023111541_QJ4WH6Q5FE.svg
566 ms
20160519023303604_50kBzn5Jww.svg
593 ms
20160519030131260_H2zrEA71Y8.svg
602 ms
20160519015506744_2VE8UG2fSR.svg
609 ms
20160519024039260_S8b5N7G6MS.svg
614 ms
20160519024305781_tn7zn9t6jh.svg
663 ms
20160519023810588_YTC6SEYdPP.svg
678 ms
20160519024413447_rj4wj6q3fe.svg
688 ms
20191111043844894_FAwN9yFU66.png
695 ms
20160519024859041_F9vN9xEU66.svg
700 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
63 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
64 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
113 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
113 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
114 ms
FontAwesomeBrands-Regular-webfont.woff
778 ms
BlackTie-Regular-webfont.woff
674 ms
BlackTie-Light-webfont.woff
699 ms
sdk.js
106 ms
BlackTie-Solid-webfont.woff
613 ms
fontawesome-webfont.woff
687 ms
20160519025553588_ZUD7TFZeQQ.svg
612 ms
20160519025316777_r96XnjD96D.svg
680 ms
20160519025111557_j22Xez9xdj.svg
644 ms
20160519025206182_P572H4C2GN.svg
651 ms
20160519025359463_ytc4seyBqp.svg
610 ms
202206090706148582.jpg
738 ms
feedbackHandler.ashx
671 ms
feedbackHandler.ashx
739 ms
feedbackHandler.ashx
845 ms
gradient.png
483 ms
angle_down.png
486 ms
20240201060227998_6ZJcYM6jVV.png
1016 ms
20240201055559375_83pE2r8N0z.png
1597 ms
20240201054329995_VP82PAU9KJ.png
1296 ms
sdk.js
13 ms
20230728010334700_5zjBzm4Hwv.png
996 ms
20221021104930039_F9vM9xEU65.png
984 ms
20220704050602992_06ncnSa9w1.png
1048 ms
20220525104628126_SB5RDXcNN5.png
1558 ms
20210401031508935_QH3WH5P4ED.png
1182 ms
20181228014846972_S6jcF3tJb4.jpg
1112 ms
20190215022440580_dUwR8t3s7c.jpg
1202 ms
20190416033552883_R7bwQS5hbE.jpg
1151 ms
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
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
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
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
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 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 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.
ecobank.com
Open Graph data is detected on the main page of Ecobank. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: