Tools & Wizards About Us
vtb.am screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vtb.am

Գլխավոր ՎՏԲ-Հայաստան Բանկ

Page Load Speed

6 sec in total

First Response

1.5 sec

Resources Loaded

4.2 sec

Page Rendered

252 ms

vtb.am screenshot

About Website

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

Հարգելի հաճախորդ, Բանկի կայքում հայերեն և ռուսերեն լեզուներով հրապարակված տեղեկատվության միջև անհամապատասխանության դեպքում անհրաժեշտ է հիմնվել հայերեն տարբերակի վրա: Հղված կայքերի բովանդակության ստույ...

Visit vtb.am

Key Findings

We analyzed Vtb.am page load time and found that the first response time was 1.5 sec 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.

Performance Metrics

vtb.am performance score

0

Network Requests Diagram

vtb.am

1533 ms

kernel_main.css

252 ms

page_14b2e78089d05bc334bc396db8c33a2a.css

254 ms

popup.min.css

256 ms

template_5cf72b27e2ca2b1f627c8b61bf1fb9d9.css

260 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 94% of them (63 requests) were addressed to the original Vtb.am, 3% (2 requests) were made to Circle.am and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Vtb.am.

Page Optimization Overview & Recommendations

Page size can be reduced by 512.1 kB (31%)

Content Size

1.7 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vtb.am main page is 1.7 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 46.2 kB

  • Original 58.3 kB
  • After minification 51.9 kB
  • After compression 12.0 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 6.3 kB, which is 11% 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 46.2 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 88.3 kB

  • Original 1.1 MB
  • After minification 981.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. Vtb images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 332.0 kB

  • Original 468.9 kB
  • After minification 446.4 kB
  • After compression 137.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 332.0 kB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 45.6 kB

  • Original 55.9 kB
  • After minification 48.8 kB
  • After compression 10.3 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. Vtb.am needs all CSS files to be minified and compressed as it can save up to 45.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (41%)

Requests Now

66

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 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 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vtb.am

vtb.am

1533 ms

kernel_main.css

kernel_main.css

252 ms

page_14b2e78089d05bc334bc396db8c33a2a.css

page_14b2e78089d05bc334bc396db8c33a2a.css

254 ms

popup.min.css

popup.min.css

256 ms

template_5cf72b27e2ca2b1f627c8b61bf1fb9d9.css

template_5cf72b27e2ca2b1f627c8b61bf1fb9d9.css

260 ms

kernel_main.js

kernel_main.js

550 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

626 ms

kernel_altasib.errorsend.js

kernel_altasib.errorsend.js

374 ms

window.css

window.css

378 ms

page_4f0f407ba55ef90281453547433e7b4c.js

page_4f0f407ba55ef90281453547433e7b4c.js

381 ms

opera.css

opera.css

388 ms

jquery-1.2.6.min.php

jquery-1.2.6.min.php

624 ms

js.js

js.js

502 ms

vtb-effects.js

vtb-effects.js

508 ms

vtbvkladki.js

vtbvkladki.js

517 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

762 ms

jquery.cycle.all.js

jquery.cycle.all.js

642 ms

altasib.errorsend.ok.gif

altasib.errorsend.ok.gif

128 ms

altasib.errorsend.png

altasib.errorsend.png

133 ms

MirVTB_arm.jpg

MirVTB_arm.jpg

413 ms

maga.jpg

maga.jpg

375 ms

USD.png

USD.png

261 ms

EUR.png

EUR.png

261 ms

RUR.png

RUR.png

273 ms

GBP.png

GBP.png

362 ms

AUD.png

AUD.png

370 ms

CHF.png

CHF.png

377 ms

GEL.png

GEL.png

391 ms

gold.gif

gold.gif

487 ms

01.gif

01.gif

497 ms

02.gif

02.gif

497 ms

04.gif

04.gif

502 ms

06.gif

06.gif

521 ms

07.gif

07.gif

556 ms

08.gif

08.gif

613 ms

09.gif

09.gif

623 ms

11.gif

11.gif

621 ms

contransfer.jpg

contransfer.jpg

626 ms

DepositARM.jpg

DepositARM.jpg

1693 ms

businessarm.jpg

businessarm.jpg

685 ms

corporate.jpg

corporate.jpg

863 ms

PB.jpg

PB.jpg

744 ms

RE.jpg

RE.jpg

750 ms

ebanking.jpg

ebanking.jpg

752 ms

facebook.jpg

facebook.jpg

823 ms

gold.gif

gold.gif

868 ms

Cos.jpg

Cos.jpg

877 ms

Lz.jpg

Lz.jpg

878 ms

business.jpg

business.jpg

962 ms

zayavka.jpg

zayavka.jpg

988 ms

back2_03.jpg

back2_03.jpg

1231 ms

main_page_gr.jpg

main_page_gr.jpg

2174 ms

4.jpg

4.jpg

1135 ms

main_page_gr.jpg

main_page_gr.jpg

1525 ms

logo-vtb.png

logo-vtb.png

862 ms

bg-nav-li.gif

bg-nav-li.gif

987 ms

circlecode.php

circlecode.php

259 ms

arr.gif

arr.gif

1099 ms

51_n.gif

51_n.gif

1102 ms

bg-btn.gif

bg-btn.gif

1027 ms

c-01-tr.gif

c-01-tr.gif

1125 ms

arr-white.gif

arr-white.gif

1127 ms

btn_skype.png

btn_skype.png

1137 ms

dvdr.gif

dvdr.gif

1228 ms

banner29.gif

banner29.gif

89 ms

ga.js

ga.js

30 ms

__utm.gif

__utm.gif

11 ms

SEO Factors

vtb.am SEO score

0

Language and Encoding

  • Language Detected

    HY

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vtb.am can be misinterpreted by Google and other search engines. Our service has detected that Armenian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vtb.am 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

vtb.am

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: