Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

viva.am

Վիվա | Բջջային կապ, ինտերնետ, հեռուստատեսություն

Page Load Speed

8.2 sec in total

First Response

1.8 sec

Resources Loaded

6 sec

Page Rendered

355 ms

viva.am screenshot

About Website

Welcome to viva.am homepage info - get ready to check Viva best content for Armenia right away, or after learning these important things about viva.am

Վիվան Հայաստանում հեռահաղորդակցության առաջատար օպերատորն է, որը տրամադրում է ձայնային, ռոումինգ և ինտերնետ ծառայություններ ՀՀ ողջ տարածքում:

Visit viva.am

Key Findings

We analyzed Viva.am page load time and found that the first response time was 1.8 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

viva.am performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.0 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value990 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

www.mts.am

1802 ms

gtm.js

52 ms

main_new.min.css

1302 ms

css2

28 ms

ScriptResource.axd

488 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Viva.am, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Mts.am.

Page Optimization Overview & Recommendations

Page size can be reduced by 789.6 kB (14%)

Content Size

5.7 MB

After Optimization

5.0 MB

In fact, the total size of Viva.am main page is 5.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. 40% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 523.1 kB

  • Original 659.6 kB
  • After minification 618.3 kB
  • After compression 136.4 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 523.1 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 261.2 kB

  • Original 4.4 MB
  • After minification 4.2 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. Viva images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.3 kB

  • Original 366.3 kB
  • After minification 366.1 kB
  • After compression 361.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 305.0 kB
  • After minification 305.0 kB
  • After compression 305.0 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. Viva.am has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (29%)

Requests Now

52

After Optimization

37

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viva. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

viva.am accessibility score

84

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

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

viva.am best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

viva.am SEO score

92

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

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

    HY

  • Language Claimed

    HY

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viva.am can be misinterpreted by Google and other search engines. Our service has detected that Armenian is used on the page, and it matches the claimed language. Our system also found out that Viva.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

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