5.7 sec in total
381 ms
5.1 sec
268 ms
Click here to check amazing Xxi content. Otherwise, check out these important facts you probably never knew about xxi.az
AUTO.AZ
Visit xxi.azWe analyzed Xxi.az page load time and found that the first response time was 381 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
xxi.az performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value5.4 s
20/100
25%
Value6.0 s
47/100
10%
Value100 ms
98/100
30%
Value0
100/100
15%
Value5.0 s
76/100
10%
381 ms
117 ms
456 ms
595 ms
263 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Xxi.az, 92% (92 requests) were made to Auto.az and 3% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Auto.az.
Page size can be reduced by 68.8 kB (13%)
510.2 kB
441.5 kB
In fact, the total size of Xxi.az main page is 510.2 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. 30% of websites need less resources to load. Images take 343.1 kB which makes up the majority of the site volume.
Potential reduce by 41.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. 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 41.5 kB or 78% of the original size.
Potential reduce by 26.7 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. Xxi images are well optimized though.
Potential reduce by 196 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 312 B
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. Xxi.az needs all CSS files to be minified and compressed as it can save up to 312 B or 11% of the original size.
Number of requests can be reduced by 16 (16%)
97
81
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xxi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
xxi.az
381 ms
www.auto.az
117 ms
www.auto.az
456 ms
g=css
595 ms
new.css
263 ms
jquery.min.js
22 ms
g=js
1414 ms
js
69 ms
fbevents.js
213 ms
lang_az.gif
208 ms
lang_ru.gif
208 ms
0813855001715827472.jpg
243 ms
0571654001715827303.jpg
330 ms
0198989001715827151.jpg
427 ms
0321931001715826972.jpg
432 ms
0106055001715826790.jpg
423 ms
0359774001715826584.jpg
427 ms
0229348001715826393.jpg
445 ms
0853641001715826031.jpg
545 ms
0527088001715825821.jpg
638 ms
0458830001715825559.jpg
436 ms
0216324001715825424.jpg
644 ms
0490337001715672893.jpg
675 ms
0836792001715672731.jpg
665 ms
0404115001715670866.jpg
665 ms
0997368001715670710.jpg
761 ms
0105546001715670589.jpg
874 ms
0970809001715669994.jpg
863 ms
0994498001715669613.jpg
885 ms
0645752001715566883.jpg
886 ms
0041477001715566659.jpg
894 ms
0296801001715566492.jpg
986 ms
0098057001715566195.jpg
1083 ms
0167348001715566062.jpg
1105 ms
0170551001715565922.jpg
1123 ms
0078017001715565752.jpg
1106 ms
0388408001715565567.jpg
1119 ms
0648767001715565304.jpg
1205 ms
0286867001715565137.jpg
1305 ms
0169959001715564955.jpg
1340 ms
0569008001715564553.jpg
1120 ms
0569028001715000589.jpg
1142 ms
0186800001715000360.jpg
1343 ms
0701321001715000221.jpg
1351 ms
0553463001714999515.jpg
1110 ms
sdk.js
57 ms
plusone.js
76 ms
0384505001714999058.jpg
1191 ms
0676437001714998858.jpg
1225 ms
sdk.js
7 ms
0544333001714998344.jpg
1282 ms
cb=gapi.loaded_0
6 ms
0768256001714343888.jpg
1232 ms
0021149001714343317.jpg
956 ms
0825114001714342825.jpg
942 ms
0973542001714342066.jpg
1161 ms
0195549001714341879.jpg
1169 ms
0273913001713747404.jpg
1179 ms
0521195001713747165.jpg
1205 ms
0842499001713746955.jpg
1203 ms
0139285001713746766.jpg
1140 ms
0174451001713746355.jpg
1161 ms
0642592001713745861.jpg
952 ms
0913989001713745283.jpg
961 ms
0140875001713745487.jpg
1170 ms
0413838001713425291.jpg
876 ms
0020986001713425105.jpg
892 ms
0929856001713424933.jpg
991 ms
0280517001713424783.jpg
1087 ms
0247393001713424133.jpg
1084 ms
0317146001713018761.jpg
1107 ms
0673242001713018474.jpg
931 ms
0234150001712889076.jpg
981 ms
0185813001712888741.jpg
977 ms
0118181001712888475.jpg
1037 ms
0852226001712888265.jpg
860 ms
0322822001712888033.jpg
1069 ms
0816223001712478555.jpg
1080 ms
0491837001712478213.jpg
1090 ms
0196303001712298495.jpg
904 ms
141.jpg
885 ms
plus_new.png
994 ms
logo1.gif
762 ms
ar.png
774 ms
dash.png
778 ms
dot.gif
988 ms
next.png
989 ms
rm_ic0.png
1019 ms
rm_ic1.png
787 ms
rm_ic2.png
911 ms
rm_ic3.png
686 ms
rm_ic5.png
671 ms
logo2.gif
671 ms
0560239001565780695.jpg
874 ms
60percents.png
902 ms
0545015001556795582.jpg
951 ms
0189234001499418176.jpg
950 ms
0982878001470133873.jpg
983 ms
0692084001470133940.jpg
701 ms
scroller.png
933 ms
xxi.az 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
Links do not have a discernible name
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.
xxi.az 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
General
Impact
Issue
Detected JavaScript libraries
xxi.az SEO score
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
AZ
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xxi.az can be misinterpreted by Google and other search engines. Our service has detected that Azerbaijani 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 Xxi.az 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.
xxi.az
Open Graph description is not detected on the main page of Xxi. 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: