Tools & Wizards About Us
verelq.am screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

verelq.am

Verelq News | Главная

Page Load Speed

6.9 sec in total

First Response

2.9 sec

Resources Loaded

3.4 sec

Page Rendered

617 ms

verelq.am screenshot

About Website

Click here to check amazing Verelq content for Armenia. Otherwise, check out these important facts you probably never knew about verelq.am

Информационно-аналитический центр (ИАЦ) VERELQ – изучает и освещает важнейшие события и тенденции в общественно-политической и экономической сферах Армении, а также роль и влияние армянской диаспоры в...

Visit verelq.am

Key Findings

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

Performance Metrics

verelq.am performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.415

23/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

verelq.am

2906 ms

reset.css

65 ms

font-awesome.min.css

46 ms

lightslider.css

63 ms

swiper.min.css

62 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 76% of them (45 requests) were addressed to the original Verelq.am, 14% (8 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Verelq.am.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.7 kB (13%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Verelq.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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 71.3 kB

  • Original 84.2 kB
  • After minification 57.7 kB
  • After compression 12.9 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 26.5 kB, which is 31% 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 71.3 kB or 85% of the original size.

Image Optimization

-9%

Potential reduce by 135.7 kB

  • Original 1.5 MB
  • After minification 1.3 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. Verelq images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 3.6 kB

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

-31%

Potential reduce by 8.1 kB

  • Original 25.7 kB
  • After minification 19.6 kB
  • After compression 17.7 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. Verelq.am needs all CSS files to be minified and compressed as it can save up to 8.1 kB or 31% of the original size.

Requests Breakdown

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

Requests Now

49

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

verelq.am

verelq.am

2906 ms

reset.css

reset.css

65 ms

font-awesome.min.css

font-awesome.min.css

46 ms

lightslider.css

lightslider.css

63 ms

swiper.min.css

swiper.min.css

62 ms

style-no-calendar-b.css

style-no-calendar-b.css

60 ms

jquery-ui.min.css

jquery-ui.min.css

62 ms

jquery-ui.structure.min.css

jquery-ui.structure.min.css

55 ms

css

css

66 ms

style-new-z.css

style-new-z.css

64 ms

calendar-2.css

calendar-2.css

70 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

72 ms

jquery-ui.min.js

jquery-ui.min.js

81 ms

swiper.min.js

swiper.min.js

85 ms

jquery.slimscroll.min.js

jquery.slimscroll.min.js

81 ms

script-2.js

script-2.js

71 ms

email-decode.min.js

email-decode.min.js

42 ms

lightslider.js

lightslider.js

119 ms

javascript.js

javascript.js

169 ms

logo.svg

logo.svg

60 ms

close-icon.svg

close-icon.svg

57 ms

search.svg

search.svg

58 ms

lang.svg

lang.svg

63 ms

row-bottom.svg

row-bottom.svg

62 ms

vk.svg

vk.svg

68 ms

twitter.svg

twitter.svg

67 ms

facebook.svg

facebook.svg

69 ms

telegram.svg

telegram.svg

68 ms

toggle-icon.svg

toggle-icon.svg

59 ms

a7caf17fd06424398a708b2a19a359e5.jpeg

a7caf17fd06424398a708b2a19a359e5.jpeg

81 ms

2b8ef4400a2e6a9c776ed5ec45400c64.jpg

2b8ef4400a2e6a9c776ed5ec45400c64.jpg

97 ms

d08901bdf7b743bcec96ac62d5a4fe6a.jpg

d08901bdf7b743bcec96ac62d5a4fe6a.jpg

106 ms

c95f3c88962db2c00e4c20ce90276f9f.png

c95f3c88962db2c00e4c20ce90276f9f.png

105 ms

bb139c2365a0ebcdcdc9ac617e2c63f6.jpg

bb139c2365a0ebcdcdc9ac617e2c63f6.jpg

90 ms

327beba7f22d517abbcd561c669674f9.jpg

327beba7f22d517abbcd561c669674f9.jpg

91 ms

166df452f9e32ba423d905eca7f3e738.jpg

166df452f9e32ba423d905eca7f3e738.jpg

108 ms

1f65e205092af4ddfeeee32c602b4b04.jpg

1f65e205092af4ddfeeee32c602b4b04.jpg

109 ms

left_arrow_white.png

left_arrow_white.png

160 ms

right_arrow_white.png

right_arrow_white.png

161 ms

follow-us-on-social-logo.png

follow-us-on-social-logo.png

61 ms

47efe92523eca45d86352e51cd9a59b3.jpg

47efe92523eca45d86352e51cd9a59b3.jpg

162 ms

vk.svg

vk.svg

161 ms

twitter.svg

twitter.svg

164 ms

facebook.svg

facebook.svg

645 ms

telegram.svg

telegram.svg

163 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

71 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

80 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

95 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

93 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

103 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

104 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

105 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

103 ms

analytics.js

analytics.js

54 ms

sdk.js

sdk.js

40 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

610 ms

sdk.js

sdk.js

14 ms

collect

collect

54 ms

js

js

68 ms

Accessibility Review

verelq.am accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

verelq.am best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

verelq.am SEO score

93

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

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

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Verelq.am can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Verelq.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

verelq.am

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