6.8 sec in total
2 sec
4.7 sec
176 ms
Visit moh.am now to see the best up-to-date Moh content for Armenia and also check out these interesting facts you probably never knew about moh.am
Visit moh.amWe analyzed Moh.am page load time and found that the first response time was 2 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
moh.am performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value22.4 s
0/100
25%
Value28.8 s
0/100
10%
Value11,670 ms
0/100
30%
Value0.325
35/100
15%
Value23.0 s
1/100
10%
1980 ms
457 ms
316 ms
320 ms
321 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 86% of them (75 requests) were addressed to the original Moh.am, 3% (3 requests) were made to S.ytimg.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Moh.am.
Page size can be reduced by 1.1 MB (20%)
5.5 MB
4.4 MB
In fact, the total size of Moh.am main page is 5.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 485.5 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 443.8 kB, which is 90% 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 485.5 kB or 98% of the original size.
Potential reduce by 234.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. Moh images are well optimized though.
Potential reduce by 137.9 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 137.9 kB or 65% of the original size.
Potential reduce by 251.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. Moh.am needs all CSS files to be minified and compressed as it can save up to 251.7 kB or 83% of the original size.
Number of requests can be reduced by 20 (28%)
72
52
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
moh.am
1980 ms
style.css
457 ms
stylesheet.css
316 ms
feedback.css
320 ms
superfish.css
321 ms
superfish-navbar.css
324 ms
jquery-1.7.2.min.js
791 ms
Validate.js
481 ms
jquery.fancybox-1.3.4.js
488 ms
jquery.fancybox-1.3.4.css
486 ms
hoverIntent.js
605 ms
superfish.js
635 ms
custom.js
644 ms
comm.js
645 ms
JsHttpRequest.js
759 ms
slides.min.jquery.js
809 ms
jquery.validate.js
959 ms
common.js
808 ms
main.js
911 ms
1458222639.jpg
165 ms
1458137557.jpg
168 ms
1458107696.jpg
169 ms
1458068466.JPG
168 ms
1458050426.jpg
173 ms
1457961310.jpg
432 ms
1.jpg
566 ms
2.jpg
667 ms
3.jpg
795 ms
4.jpg
803 ms
5.jpg
733 ms
6.jpg
794 ms
7.jpg
801 ms
8.jpg
978 ms
9.jpg
1356 ms
10.jpg
1114 ms
11.jpg
1100 ms
12.jpg
1133 ms
13.jpg
1153 ms
14.jpg
1301 ms
15.jpg
1412 ms
16.jpg
1436 ms
17.jpg
1758 ms
18.jpg
1629 ms
19.jpg
1623 ms
20.jpg
2129 ms
21.jpg
1719 ms
22.jpg
1754 ms
23.jpg
1942 ms
24.jpg
2423 ms
25.jpg
2024 ms
26.jpg
2079 ms
all.js
35 ms
header.jpg
1891 ms
logo.png
2052 ms
home.gif
2067 ms
So1AqdarIx4
120 ms
155 ms
xd_arbiter.php
44 ms
xd_arbiter.php
73 ms
arianamu-webfont.woff
2026 ms
arianamub-webfont.woff
2086 ms
mail.gif
2091 ms
group.gif
2098 ms
print.gif
2115 ms
www-embed-player-vflfNyN_r.css
162 ms
www-embed-player.js
188 ms
base.js
222 ms
search.png
1940 ms
header_bottom.jpg
1981 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
48 ms
ad_status.js
42 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
35 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
38 ms
menu.png
1845 ms
oage.jpg
1763 ms
menu_bottom_shadow.png
1716 ms
footer.jpg
1700 ms
e-gov.png
1775 ms
tundarc.png
1767 ms
APHVP.png
1786 ms
email.png
1611 ms
follow.png
1503 ms
Guillotine.png
1533 ms
license_2.png
1592 ms
1.jpg
1879 ms
loading.gif
1445 ms
pagination.png
1394 ms
moh.am accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
moh.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
moh.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
N/A
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moh.am can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Russian. Our system also found out that Moh.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.
moh.am
Open Graph description is not detected on the main page of Moh. 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: