4.1 sec in total
942 ms
2.9 sec
243 ms
Visit parliament.am now to see the best up-to-date Parliament content for Armenia and also check out these interesting facts you probably never knew about parliament.am
Visit parliament.amWe analyzed Parliament.am page load time and found that the first response time was 942 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
parliament.am performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value2.4 s
92/100
25%
Value4.7 s
69/100
10%
Value40 ms
100/100
30%
Value0.001
100/100
15%
Value2.7 s
97/100
10%
942 ms
480 ms
797 ms
323 ms
165 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that all of those requests were addressed to Parliament.am and no external sources were called. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Parliament.am.
Page size can be reduced by 167.7 kB (41%)
408.5 kB
240.8 kB
In fact, the total size of Parliament.am main page is 408.5 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 239.6 kB which makes up the majority of the site volume.
Potential reduce by 22.3 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 22.3 kB or 81% of the original size.
Potential reduce by 25.6 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. Obviously, Parliament needs image optimization as it can save up to 25.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 88.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 88.6 kB or 84% of the original size.
Potential reduce by 31.2 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. Parliament.am needs all CSS files to be minified and compressed as it can save up to 31.2 kB or 88% of the original size.
Number of requests can be reduced by 11 (28%)
39
28
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Parliament. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
parliament.am
942 ms
cover_arm.css
480 ms
jquery-1.2.6.js
797 ms
functions.js
323 ms
top_bg.gif
165 ms
theme_bg.jpg
161 ms
theme_1.jpg
323 ms
logo_coat.gif
166 ms
logo_arm.gif
322 ms
search_bg.gif
325 ms
home_mail_sitemap.gif
330 ms
lang_arm.gif
335 ms
lang_rus.gif
335 ms
lang_eng.gif
481 ms
lang_frn.gif
482 ms
zag_1.gif
484 ms
menu_circle.gif
492 ms
signature_new_bg.gif
502 ms
chairman_new.jpg
831 ms
ban_armenia.jpg
639 ms
ban_patm.jpg
642 ms
ban_sahm.jpg
647 ms
ban_kanon.jpg
655 ms
news_plaj.jpg
669 ms
ico_sticker_1.gif
798 ms
news_bg.gif
802 ms
photo.php
889 ms
photo.php
901 ms
photo.php
910 ms
photo.php
1051 ms
photo.php
1052 ms
photo.php
1071 ms
photo.php
1126 ms
photo.php
1147 ms
photo.php
1156 ms
ico_top.gif
1210 ms
bottom_flg.gif
1211 ms
bottom_logo_arm.gif
1239 ms
t.gif
1286 ms
ico_mail.gif
1297 ms
parliament.am accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
parliament.am best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
parliament.am SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
HY
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Parliament.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 Parliament.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.
parliament.am
Open Graph description is not detected on the main page of Parliament. 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: