6.5 sec in total
1.4 sec
5 sec
172 ms
Visit datalex.am now to see the best up-to-date Data Lex content for Armenia and also check out these interesting facts you probably never knew about datalex.am
Visit datalex.amWe analyzed Datalex.am page load time and found that the first response time was 1.4 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
datalex.am performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value9.7 s
0/100
25%
Value8.0 s
22/100
10%
Value90 ms
98/100
30%
Value0.253
49/100
15%
Value10.9 s
21/100
10%
1351 ms
359 ms
357 ms
364 ms
362 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 90% of them (36 requests) were addressed to the original Datalex.am, 5% (2 requests) were made to Circle.am and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Datalex.am.
Page size can be reduced by 24.4 kB (49%)
49.7 kB
25.2 kB
In fact, the total size of Datalex.am main page is 49.7 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. Only 10% of websites need less resources to load. CSS take 19.4 kB which makes up the majority of the site volume.
Potential reduce by 9.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. This page needs HTML code to be minified as it can gain 1.7 kB, which is 14% 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 9.3 kB or 73% of the original size.
Potential reduce by 0 B
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. Data Lex images are well optimized though.
Potential reduce by 34 B
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.
Potential reduce by 15.1 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. Datalex.am needs all CSS files to be minified and compressed as it can save up to 15.1 kB or 78% of the original size.
Number of requests can be reduced by 18 (46%)
39
21
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data Lex. 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.
datalex.am
1351 ms
style.css
359 ms
style.css
357 ms
style.css
364 ms
spacer.gif
362 ms
bg.gif
174 ms
shd_l.png
348 ms
head_bg.gif
348 ms
top_bg.gif
348 ms
top_left.gif
350 ms
home.gif
349 ms
mail.gif
517 ms
top_right.gif
691 ms
datalex.gif
698 ms
name.gif
702 ms
button.gif
707 ms
menu_bg.gif
705 ms
menu_left.gif
865 ms
menu_sep.gif
1037 ms
menu_right.gif
1045 ms
shadow_top.gif
1051 ms
equal_doc_bg.gif
1881 ms
equal_doc_image.gif
1229 ms
datalex.gif
2590 ms
serch.gif
1748 ms
online_payment.gif
1774 ms
timer_bg.gif
1784 ms
online_app.gif
1624 ms
banner_court.jpg
1980 ms
banner_sd.gif
2097 ms
banner_law.gif
2124 ms
banner_egov.jpg
2136 ms
shd_r.png
2228 ms
flag_arm.gif
2332 ms
flag_nl.gif
2447 ms
flag_b.gif
3259 ms
circlecode.php
250 ms
banner29.gif
86 ms
ga.js
25 ms
__utm.gif
28 ms
datalex.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
Image elements do not have [alt] attributes
Links do not have a discernible name
datalex.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
datalex.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 Datalex.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 Datalex.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.
datalex.am
Open Graph description is not detected on the main page of Data Lex. 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: