Tools & Wizards About Us

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

vtb.com

VTB Bank (PJSC)

Page Load Speed

5.1 sec in total

First Response

508 ms

Resources Loaded

4.2 sec

Page Rendered

358 ms

About Website

Visit vtb.com now to see the best up-to-date VTB content for Russia and also check out these interesting facts you probably never knew about vtb.com

VTB Bank

Visit vtb.com

Key Findings

We analyzed Vtb.com page load time and found that the first response time was 508 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

vtb.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value10,380 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

vtb.com

508 ms

www.vtb.com

1081 ms

ruxitagentjs_ICA27NVfqrux_10233220201140653.js

489 ms

vendors.js

1271 ms

app.js

593 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 71% of them (17 requests) were addressed to the original Vtb.com, 17% (4 requests) were made to Vtb.ru and 8% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Vtb.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.9 kB (22%)

Content Size

586.2 kB

After Optimization

456.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Vtb.com main page is 586.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 223.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 129.9 kB

  • Original 146.6 kB
  • After minification 145.2 kB
  • After compression 16.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 129.9 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 223.2 kB
  • After minification 223.2 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. VTB images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 216.4 kB
  • After minification 216.4 kB
  • After compression 216.4 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.

Requests Breakdown

Number of requests can be reduced by 3 (17%)

Requests Now

18

After Optimization

15

  • AJAX
  • Images
  • JavaScript

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VTB. 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 as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

vtb.com accessibility score

81

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

vtb.com best practices score

75

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

vtb.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vtb.com 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 Russian language. Our system also found out that Vtb.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of VTB. 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: