9.1 sec in total
1.7 sec
6.1 sec
1.3 sec
Click here to check amazing Echo content for Azerbaijan. Otherwise, check out these important facts you probably never knew about echo.az
Общественно-политическое обозрение Азербайджана. Новости Азербайджана, аналитика, комментарии, мнения экспертов, актуальные проблемы общества.
Visit echo.azWe analyzed Echo.az page load time and found that the first response time was 1.7 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
echo.az performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value4.4 s
40/100
25%
Value5.4 s
56/100
10%
Value410 ms
67/100
30%
Value0.167
71/100
15%
Value7.5 s
47/100
10%
1711 ms
295 ms
200 ms
353 ms
498 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 44% of them (59 requests) were addressed to the original Echo.az, 7% (9 requests) were made to Tpc.googlesyndication.com and 6% (8 requests) were made to Zn2.gnezdo.ru. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Echo.az.
Page size can be reduced by 1.1 MB (13%)
8.5 MB
7.4 MB
In fact, the total size of Echo.az main page is 8.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. 70% of websites need less resources to load. Images take 8.1 MB which makes up the majority of the site volume.
Potential reduce by 230.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 230.5 kB or 84% of the original size.
Potential reduce by 800.9 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. Echo images are well optimized though.
Potential reduce by 37.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 37.6 kB or 41% of the original size.
Potential reduce by 30.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. Echo.az needs all CSS files to be minified and compressed as it can save up to 30.4 kB or 85% of the original size.
Number of requests can be reduced by 34 (27%)
126
92
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Echo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
echo.az
1711 ms
style2012_8.css
295 ms
cnt.js
200 ms
adsvcs.js
353 ms
498 ms
show_ads.js
119 ms
330 ms
a98651.jpg
1197 ms
cycounter
524 ms
3_0_FFFFFFFF_FFFFFFFF_0_pageviews
278 ms
logo-mini2.png
395 ms
logo.jpg
82 ms
a98784.jpg
144 ms
a98807.jpg
242 ms
a98787.jpg
528 ms
a98782.jpg
247 ms
a98794.jpg
245 ms
a98793.jpg
527 ms
a98789.jpg
374 ms
23047.jpg
528 ms
a98735.jpg
732 ms
23055.jpg
638 ms
a98733.jpg
624 ms
22292.jpg
1441 ms
a98727.jpg
806 ms
a94769.jpg
633 ms
a88183.jpg
857 ms
a51360.JPG
865 ms
a79185.jpg
760 ms
a98783.jpg
861 ms
a98385.jpg
2369 ms
20023.jpg
1857 ms
23049.jpg
1741 ms
a98659.JPG
1357 ms
a98802.jpg
1683 ms
23045.jpg
1570 ms
23046.jpg
1882 ms
a98654.jpg
1607 ms
180_2.jpg
1732 ms
179_2.jpg
1855 ms
178_2.jpg
1785 ms
177_2.jpg
1819 ms
search1.png
1883 ms
fblarge.png
1914 ms
twlarge.png
1936 ms
vklarge.png
1946 ms
a96314.jpg
1564 ms
a84833.jpg
928 ms
a84566.JPG
1674 ms
a95590.JPG
1146 ms
a78079.jpg
1136 ms
a79730.JPG
1145 ms
a96806.jpg
1350 ms
a72403.jpg
1278 ms
rsslarge.png
1939 ms
rdg
88 ms
a98815.jpg
2005 ms
a98816.jpg
2142 ms
ca-pub-7104543801500968.js
129 ms
zrt_lookup.html
345 ms
show_ads_impl.js
228 ms
gs_informerClient.min.css
957 ms
a98814.jpg
2279 ms
a98721.jpg
2173 ms
a97962.jpeg
1934 ms
a98665.jpg
2003 ms
logo-mini2.png
905 ms
ads
300 ms
osd.js
138 ms
a98801.jpg
1896 ms
a98792.jpg
1989 ms
a98811.JPG
1986 ms
a98718.jpg
2048 ms
suggestion_autolayout_V2_10.css
454 ms
suggestion_autolayout_V2_10.js
518 ms
layout_engine.js
589 ms
abg.js
607 ms
ga.js
71 ms
js15.js
34 ms
0.php
90 ms
context.js
357 ms
100.gif
1224 ms
googlelogo_color_112x36dp.png
198 ms
__utm.gif
148 ms
9095478577218208008
163 ms
s
75 ms
context_static_r1084.js
440 ms
x_button_blue2.svg
73 ms
ads
498 ms
gen.240x400.php
437 ms
block.html
356 ms
ads
388 ms
ads.people-group.net
145 ms
watch.js
2 ms
hit
328 ms
blog.inseadhealthalumni.net
452 ms
d.sun.png
504 ms
ajs.php
51 ms
228188.js
421 ms
lg.php
208 ms
tzr.fcgi
209 ms
129877
247 ms
watch.js
2 ms
4939908717554595569
158 ms
m_js_controller.js
79 ms
78089.js
436 ms
9424534783272887619
259 ms
match.aspx
202 ms
push
227 ms
420290_0b7be8a80d.jpg
344 ms
413677_19da8066b8.jpg
345 ms
395570_af4e3cac55.jpg
354 ms
420453_46774f2cce.jpg
354 ms
405414_a33374d48e.jpg
355 ms
420761_d0109138a1.jpg
355 ms
420758_2382d6a44f.jpg
477 ms
392623_d74ac987ef.jpg
477 ms
x90
321 ms
x80
405 ms
showad_full_sync.js
154 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
7 ms
1x1.gif
243 ms
2975095.jpeg
349 ms
2958575.png
453 ms
2974988.jpeg
334 ms
357 ms
adi
347 ms
pixel
24 ms
activeview
40 ms
lb192785_3.js
346 ms
280 ms
656 ms
510 ms
FjWm2WPec9e40000gK6EkfDzS0M5bRKVdh400004klugAEh_kKHt2P6okJxh2fDKhldSG63vvBMG0R2mXPhM1B41mV__________3tW8=J-wCLvK2cm5kGxS2CecTCCwO__________yFYhcouCa2lRTvkm03fQxjSGI8iQYkGGEyg3vo1AOpdQZ_3XEFiBe7Bm-VjdI7EWYP7g2Ne0IpaYq1hvUW1BIIBG7Payq4sfWu0QUQJW6elS9H9051iG6oeD000hce_muJql__________3zF__________m_20DzKVn40=Qe3nAwa0bGAR0Mv3jmA9a3SxcF__________3ugxdbMF1Rs_QA0l1QMakZy8YBY1rk44lAM3mmAcJPsgHnOJZxXw3baDdx_oGyi7cGwWdP0Riv421w-Ja0gqcAy2sP3F7DgGKmUKc783fuH3gAVlx2f1iG6oe5800hcgHnOJnOyFpRgQLOy5ph10Wam7ql__________3zF__________m_20DzKUHG0
125 ms
echo.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
echo.az best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
echo.az SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Echo.az can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Echo.az main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
echo.az
Open Graph description is not detected on the main page of Echo. 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: