10.1 sec in total
540 ms
9.4 sec
149 ms
Click here to check amazing IBank content for Georgia. Otherwise, check out these important facts you probably never knew about ibank.ge
დააგემოვნეთ სრულიად ახალი ინტერნეტბანკი
Visit ibank.geWe analyzed Ibank.ge page load time and found that the first response time was 540 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ibank.ge performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value13.8 s
0/100
25%
Value14.0 s
1/100
10%
Value10,730 ms
0/100
30%
Value0.049
99/100
15%
Value18.5 s
3/100
10%
540 ms
3020 ms
180 ms
359 ms
970 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ibank.ge, 40% (19 requests) were made to Login.bog.ge and 38% (18 requests) were made to Ibank.bog.ge. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Login.bog.ge.
Page size can be reduced by 2.1 MB (45%)
4.6 MB
2.5 MB
In fact, the total size of Ibank.ge main page is 4.6 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. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 5.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. This page needs HTML code to be minified as it can gain 1.3 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.2 kB or 71% of the original size.
Potential reduce by 245.0 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, IBank needs image optimization as it can save up to 245.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.3 MB
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 1.3 MB or 74% of the original size.
Potential reduce by 588.5 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. Ibank.ge needs all CSS files to be minified and compressed as it can save up to 588.5 kB or 86% of the original size.
Number of requests can be reduced by 19 (53%)
36
17
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IBank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
ibank.ge
540 ms
3020 ms
app-proposal.css
180 ms
style.css
359 ms
jquery-1.11.3.min.js
970 ms
login.component.js
537 ms
analytics.js
55 ms
logo_ge.png
219 ms
ico_help.png
222 ms
ico_internetbank_hover.png
353 ms
ico_epay.png
401 ms
ico_mobilebank.png
407 ms
google.png
533 ms
appstore.png
540 ms
bg.jpg
1630 ms
ico_readmore.png
583 ms
soc.jpg
599 ms
ico_arr_r.png
710 ms
logo.png
719 ms
BOGNusxuri.woff
1097 ms
BOGMtavruli.woff
1121 ms
collect
11 ms
collect
47 ms
ga-audiences
49 ms
Login
260 ms
09b91c483ce7.20170823_162351.css
870 ms
5f0dd9467933.20170904_171844.js
1505 ms
dragdrop.png
179 ms
more-dd.png
357 ms
login-loader-sb.gif
508 ms
gtm.js
79 ms
success-circle.png
181 ms
rb_remember_checkbox.png
172 ms
rb_icon_username.png
338 ms
rb_icon_password.png
361 ms
user.png
340 ms
consult.png
342 ms
hint_transparent_bg.png
497 ms
popup_transparent_bg.png
498 ms
arial-narrow.woff
516 ms
arial-narrow-bold.woff
865 ms
bog_unicode_mtavruli.ttf
889 ms
bog_unicode_nusxuri.ttf
875 ms
collect
2 ms
collect
3 ms
collect
12 ms
ga-audiences
13 ms
ibank.ge accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
ibank.ge 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ibank.ge SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
KA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ibank.ge can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Georgian. Our system also found out that Ibank.ge 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.
ibank.ge
Open Graph data is detected on the main page of IBank. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: