Tools & Wizards About Us
arlis.am screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

arlis.am

Arlis

Page Load Speed

6.3 sec in total

First Response

490 ms

Resources Loaded

5.7 sec

Page Rendered

127 ms

arlis.am screenshot

About Website

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

Հայաստանի Իրավական Տեղեկատվական Համակարգ

Visit arlis.am

Key Findings

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

Performance Metrics

arlis.am performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value22.5 s

0/100

10%

TBT (Total Blocking Time)

Value20,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value42.8 s

0/100

10%

Network Requests Diagram

arlis.am

490 ms

www.arlis.am

654 ms

main.css

503 ms

MainStyles.css

330 ms

jQuery.js

1000 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 710.5 kB (68%)

Content Size

1.0 MB

After Optimization

332.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Arlis.am main page is 1.0 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. 35% of websites need less resources to load. Javascripts take 911.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 15.4 kB

  • Original 20.2 kB
  • After minification 18.9 kB
  • After compression 4.8 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 15.4 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 2.8 kB

  • Original 70.0 kB
  • After minification 67.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. Arlis images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 658.6 kB

  • Original 911.2 kB
  • After minification 791.2 kB
  • After compression 252.6 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 658.6 kB or 72% of the original size.

CSS Optimization

-80%

Potential reduce by 33.7 kB

  • Original 42.0 kB
  • After minification 28.0 kB
  • After compression 8.4 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. Arlis.am needs all CSS files to be minified and compressed as it can save up to 33.7 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (57%)

Requests Now

88

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

arlis.am

arlis.am

490 ms

www.arlis.am

www.arlis.am

654 ms

main.css

main.css

503 ms

MainStyles.css

MainStyles.css

330 ms

jQuery.js

jQuery.js

1000 ms

Progress.js

Progress.js

335 ms

ScriptResource.axd

ScriptResource.axd

986 ms

ga.js

ga.js

32 ms

gerb.jpg

gerb.jpg

174 ms

flag.jpg

flag.jpg

175 ms

arrow_PREV.gif

arrow_PREV.gif

188 ms

delimiter.gif

delimiter.gif

176 ms

arrow_NEXT.gif

arrow_NEXT.gif

315 ms

atb_help.gif

atb_help.gif

330 ms

ARLIS_Logo.gif

ARLIS_Logo.gif

350 ms

__utm.gif

__utm.gif

24 ms

Search.aspx

Search.aspx

495 ms

Publications.aspx

Publications.aspx

714 ms

Arlis_About.html

Arlis_About.html

753 ms

ReferencesTab.html

ReferencesTab.html

341 ms

Search.aspx

Search.aspx

2049 ms

Search.aspx

Search.aspx

1675 ms

Search_FL.aspx

Search_FL.aspx

547 ms

navBgr.gif

navBgr.gif

659 ms

navBgrFL.gif

navBgrFL.gif

726 ms

blueLine.gif

blueLine.gif

595 ms

LNG_button_RU.gif

LNG_button_RU.gif

607 ms

LNG_button_EN.gif

LNG_button_EN.gif

666 ms

__utm.gif

__utm.gif

10 ms

Banner.js

Banner.js

598 ms

common.js

common.js

664 ms

combo.js

combo.js

826 ms

ig_shared.js

ig_shared.js

907 ms

ig_edit.js

ig_edit.js

920 ms

ig_webdropdown.js

ig_webdropdown.js

829 ms

ig_calendar.js

ig_calendar.js

994 ms

ig_shared.css

ig_shared.css

992 ms

ig_textedit.css

ig_textedit.css

1156 ms

__utm.gif

__utm.gif

9 ms

main.css

main.css

970 ms

MainStyles.css

MainStyles.css

971 ms

jQuery.js

jQuery.js

1295 ms

Progress.js

Progress.js

1067 ms

Banner.js

Banner.js

1058 ms

common.js

common.js

1120 ms

combo.js

combo.js

1237 ms

ig_shared.js

ig_shared.js

1419 ms

ig_edit.js

ig_edit.js

1301 ms

ig_webdropdown.js

ig_webdropdown.js

1314 ms

ig_calendar.js

ig_calendar.js

1409 ms

ScriptResource.axd

ScriptResource.axd

1625 ms

ig_shared.css

ig_shared.css

1470 ms

ig_textedit.css

ig_textedit.css

1477 ms

banner.gif

banner.gif

1571 ms

igsch_xpblueup.gif

igsch_xpblueup.gif

1574 ms

__utm.gif

__utm.gif

9 ms

main.css

main.css

1655 ms

MainStyles.css

MainStyles.css

1656 ms

jQuery.js

jQuery.js

1729 ms

__utm.gif

__utm.gif

14 ms

PT_2016.html

PT_2016.html

1909 ms

Progress.js

Progress.js

1579 ms

Banner.js

Banner.js

1570 ms

common.js

common.js

1513 ms

combo.js

combo.js

1531 ms

ig_shared.js

ig_shared.js

1757 ms

ig_shared.css

ig_shared.css

1557 ms

ig_textedit.css

ig_textedit.css

1506 ms

ig_edit.js

ig_edit.js

1423 ms

ig_webdropdown.js

ig_webdropdown.js

1419 ms

ig_calendar.js

ig_calendar.js

1410 ms

ScriptResource.axd

ScriptResource.axd

1576 ms

PT1.gif

PT1.gif

1414 ms

GT0.gif

GT0.gif

1412 ms

YR0.gif

YR0.gif

1284 ms

VL0.gif

VL0.gif

1311 ms

other0.gif

other0.gif

1313 ms

vBorder.gif

vBorder.gif

1307 ms

hBorder.gif

hBorder.gif

1326 ms

PT0.gif

PT0.gif

1294 ms

president.jpg

president.jpg

1310 ms

e-gov.am.gif

e-gov.am.gif

1224 ms

parliament.gif

parliament.gif

1163 ms

justice.jpg

justice.jpg

1237 ms

EAES.gif

EAES.gif

1241 ms

nakhagits_ru.jpg

nakhagits_ru.jpg

1179 ms

Incorporation.png

Incorporation.png

1188 ms

act.png

act.png

1170 ms

tm1.gif

tm1.gif

1147 ms

DataLex_banner.jpg

DataLex_banner.jpg

1208 ms

adv.gif

adv.gif

1134 ms

nakhagits.jpg

nakhagits.jpg

1177 ms

ig_progressIndicator.gif

ig_progressIndicator.gif

1058 ms

igsch_xpblueup.gif

igsch_xpblueup.gif

1091 ms

ig_progressIndicator.gif

ig_progressIndicator.gif

1090 ms

main.css

main.css

1117 ms

igsch_xpblueup.gif

igsch_xpblueup.gif

1066 ms

ig_progressIndicator.gif

ig_progressIndicator.gif

1093 ms

Accessibility Review

arlis.am accessibility score

68

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

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

arlis.am best practices score

50

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

arlis.am 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

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

arlis.am

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