Report Summary

  • 16

    Performance

    Renders faster than
    35% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 69

    SEO

    Google-friendlier than
    37% of websites

ibank.ge

iBank

Page Load Speed

10.1 sec in total

First Response

540 ms

Resources Loaded

9.4 sec

Page Rendered

149 ms

ibank.ge screenshot

About Website

Click here to check amazing IBank content for Georgia. Otherwise, check out these important facts you probably never knew about ibank.ge

დააგემოვნეთ სრულიად ახალი ინტერნეტბანკი

Visit ibank.ge

Key Findings

We 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.

Performance Metrics

ibank.ge performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value10,730 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

ibank.ge

540 ms

3020 ms

app-proposal.css

180 ms

style.css

359 ms

jquery-1.11.3.min.js

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 Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (45%)

Content Size

4.6 MB

After Optimization

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.

HTML Optimization

-71%

Potential reduce by 5.2 kB

  • Original 7.3 kB
  • After minification 6.0 kB
  • After compression 2.1 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.

Image Optimization

-11%

Potential reduce by 245.0 kB

  • Original 2.2 MB
  • After minification 2.0 MB

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.

JavaScript Optimization

-74%

Potential reduce by 1.3 MB

  • Original 1.7 MB
  • After minification 1.5 MB
  • After compression 445.2 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 1.3 MB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 588.5 kB

  • Original 682.5 kB
  • After minification 623.3 kB
  • After compression 93.9 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.

Requests Breakdown

Number of requests can be reduced by 19 (53%)

Requests Now

36

After Optimization

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.

Accessibility Review

ibank.ge accessibility score

63

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ibank.ge best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ibank.ge SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    KA

  • Encoding

    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.

Social Sharing Optimization

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: