6.9 sec in total
901 ms
5.7 sec
364 ms
Visit metro.gov.az now to see the best up-to-date Metro Gov content and also check out these interesting facts you probably never knew about metro.gov.az
Visit metro.gov.azWe analyzed Metro.gov.az page load time and found that the first response time was 901 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
metro.gov.az performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value7.8 s
3/100
25%
Value4.9 s
65/100
10%
Value340 ms
74/100
30%
Value0.322
36/100
15%
Value4.9 s
77/100
10%
901 ms
25 ms
35 ms
385 ms
378 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 96% of them (112 requests) were addressed to the original Metro.gov.az, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Metro.gov.az.
Page size can be reduced by 273.7 kB (12%)
2.2 MB
1.9 MB
In fact, the total size of Metro.gov.az main page is 2.2 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. 50% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 86.9 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 86.9 kB or 81% of the original size.
Potential reduce by 813 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. Metro Gov images are well optimized though.
Potential reduce by 32.0 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 32.0 kB or 60% of the original size.
Potential reduce by 154.0 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. Metro.gov.az needs all CSS files to be minified and compressed as it can save up to 154.0 kB or 84% of the original size.
Number of requests can be reduced by 15 (13%)
114
99
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Metro Gov. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
metro.gov.az
901 ms
css
25 ms
css
35 ms
minify.css
385 ms
gallery.css
378 ms
jquery-1.9.1.min.js
4 ms
minify.js
402 ms
analytics.js
46 ms
close.png
223 ms
loading.gif
222 ms
prev.png
351 ms
next.png
380 ms
logo2x.png
377 ms
leng-arrow-down.png
379 ms
gerb2x.png
383 ms
calendar.svg
392 ms
mp-arrow-right.png
542 ms
mp-arrow-left.png
563 ms
info.svg
566 ms
icon-s.svg
568 ms
map-bg1.png
1341 ms
map.svg
1171 ms
g1g2.svg
733 ms
g2g3.svg
750 ms
g3g4.svg
753 ms
g4g5.svg
755 ms
g5g6.svg
924 ms
g6g7.svg
935 ms
g7g8.svg
939 ms
g8c1.svg
942 ms
r2c1.svg
1115 ms
r1r2.svg
1122 ms
c1c2r.svg
1126 ms
c1c2g.svg
1129 ms
c2c3r.svg
1305 ms
c2c3g.svg
1310 ms
c3c4r.svg
1315 ms
c3c4g.svg
1317 ms
c3c5r.svg
1362 ms
c3c5g.svg
1496 ms
c5c6r.svg
1499 ms
c5c6g.svg
1503 ms
c6c7r.svg
1484 ms
collect
15 ms
proxima_nova_condensed_regular-webfont.woff
1314 ms
proxima_nova_condensed_bold-webfont.woff
1344 ms
ajaxGetShuttleScheduleByDate
1485 ms
c6c7g.svg
1341 ms
c7c8r.svg
1317 ms
c7c8g.svg
1319 ms
c8c9r.svg
1358 ms
c8c9g.svg
1378 ms
c9c10r.svg
1485 ms
c9c10g.svg
1341 ms
c10c11r.svg
1323 ms
c10c11g.svg
1326 ms
g9g10.svg
1348 ms
c1g9.svg
1221 ms
zoom-in.png
1313 ms
zoom-out.png
1312 ms
mp-bg-news.png
3761 ms
medium_cdface7e78e5549e14ef47ca4671a6ca.jpg
1160 ms
medium_f4c9f719f100d850ecbbf64df2e7c63b.JPG
1171 ms
medium_23eca80931113db89b020b16171217d2.jpg
1205 ms
mp-facts-bg-01.jpg
2431 ms
1ss.svg
1139 ms
6ss.svg
1151 ms
11ss.svg
1167 ms
16ss.svg
1214 ms
2ss.svg
1254 ms
7ss.svg
1159 ms
12ss.svg
1176 ms
17ss.svg
1220 ms
3ss.svg
1311 ms
8ss.svg
1323 ms
13ss.svg
1316 ms
18ss.svg
1233 ms
4ss.svg
1315 ms
9ss.svg
1342 ms
14ss.svg
1363 ms
19ss.svg
1399 ms
5ss.svg
1444 ms
10ss.svg
1357 ms
15ss.svg
1371 ms
20ss.svg
1433 ms
virtual-karabakh.jpg
1465 ms
facebook-ico.png
1503 ms
s-inst.png
1500 ms
mob-menu-ico.png
1449 ms
icon_shuttle_new.svg
1501 ms
stad.png
1545 ms
shuttle_big.svg
1557 ms
mp-shadow.png
1604 ms
graphMotion.png
1608 ms
shuttle.svg
1512 ms
location.svg
1554 ms
purple.svg
1560 ms
green.svg
1610 ms
blue.svg
1602 ms
red.svg
1506 ms
1.svg
1537 ms
2.svg
1537 ms
3.svg
1569 ms
4.svg
1494 ms
5.svg
1482 ms
6.svg
1513 ms
7.svg
1484 ms
18.svg
1475 ms
16.svg
1464 ms
9.svg
1455 ms
20.svg
1459 ms
15.svg
1398 ms
12.svg
1450 ms
11.svg
1438 ms
icon-sight.png
1393 ms
10.png
1380 ms
8.svg
1365 ms
metro.gov.az 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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
metro.gov.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
AZ
AZ
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metro.gov.az can be misinterpreted by Google and other search engines. Our service has detected that Azerbaijani is used on the page, and it matches the claimed language. Our system also found out that Metro.gov.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.
metro.gov.az
Open Graph description is not detected on the main page of Metro Gov. 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: