23.3 sec in total
472 ms
22.7 sec
185 ms
Welcome to citytaxi.az homepage info - get ready to check Citytaxi best content for Azerbaijan right away, or after learning these important things about citytaxi.az
Сити такси/ city taxi Баку
Visit citytaxi.azWe analyzed Citytaxi.az page load time and found that the first response time was 472 ms and then it took 22.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
citytaxi.az performance score
472 ms
1252 ms
440 ms
1308 ms
2022 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 34% of them (30 requests) were addressed to the original Citytaxi.az, 20% (18 requests) were made to Maps.google.com and 13% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Citytaxi.az.
Page size can be reduced by 872.8 kB (59%)
1.5 MB
615.7 kB
In fact, the total size of Citytaxi.az main page is 1.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. Javascripts take 917.4 kB which makes up the majority of the site volume.
Potential reduce by 58.4 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 8.8 kB, which is 12% 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 58.4 kB or 82% of the original size.
Potential reduce by 4.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. Citytaxi images are well optimized though.
Potential reduce by 614.3 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 614.3 kB or 67% of the original size.
Potential reduce by 195.2 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. Citytaxi.az needs all CSS files to be minified and compressed as it can save up to 195.2 kB or 86% of the original size.
Number of requests can be reduced by 43 (58%)
74
31
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Citytaxi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
472 ms
kernel_main.css
1252 ms
default_9f221678f05c621f43253dc16c537d7d.css
440 ms
template_4dcfdf597b3bd2c83ea111c25c02f543.css
1308 ms
kernel_main.js
2022 ms
core_db.min.js
438 ms
core_frame_cache.min.js
492 ms
css
24 ms
jquery.min.js
28 ms
js
27 ms
panel.js
652 ms
jquery.min.js
32 ms
css
32 ms
screen.css
1469 ms
preloader.js
490 ms
scripts.js
1096 ms
curi.js
711 ms
jquery-ui.css
61 ms
jquery-ui.min.js
86 ms
package_80e1d0e316adb05e9db92878a033171c0abafab7.min.js
2382 ms
ba.js
164 ms
analytics.js
13 ms
black-sand-texture.jpg
227 ms
logo.png
416 ms
calendar-icon.gif
212 ms
icons-sdf94bead88.png
879 ms
enter_code.php
228 ms
collect
40 ms
social.png
594 ms
new_pattern.png
411 ms
loader.gif
430 ms
prices_in.png
593 ms
Q_pTky3Sc3ubRibGToTAYuRnbeJu535_D6CnAMBNRuw.ttf
38 ms
UyYrYy3ltEffJV9QueSi4dtgyQF8ayeFxbhi_dcZUXc.ttf
39 ms
wtwJ9UuQFa_G0mIQrZmRFaCWcynf_cDxXwCLxiixG1c.ttf
40 ms
F51BEgHuR0tYHxF0bD4vwnYhjbSpvc47ee6xR_80Hnw.ttf
39 ms
collect
65 ms
ga-audiences
41 ms
jquery-1.9.1.min.js
8 ms
package_39005f05c2fe91425e24f4396bcd012a61fe0f77.min.js
1111 ms
common.js
104 ms
util.js
104 ms
geocoder.js
104 ms
index_client.php
565 ms
marker.js
36 ms
ui-bg_flat_75_ffffff_40x100.png
24 ms
bx_stat
223 ms
AuthenticationService.Authenticate
244 ms
GeocodeService.Search
307 ms
map.js
5 ms
StaticMapService.GetMapImage
110 ms
onion.js
19 ms
openhand_8_8.cur
29 ms
ViewportInfoService.GetViewportInfo
69 ms
stats.js
19 ms
controls.js
13 ms
transparent.png
24 ms
css
17 ms
google4.png
64 ms
index_client.php
691 ms
index_client.php
535 ms
index_client.php
530 ms
mapcnt6.png
31 ms
sv5.png
32 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
20 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
22 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
21 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
20 ms
tmapctrl.png
23 ms
cb_scout5.png
42 ms
tmapctrl4.png
41 ms
imgs8.png
40 ms
vt
45 ms
vt
57 ms
vt
39 ms
vt
32 ms
vt
35 ms
vt
50 ms
vt
73 ms
vt
54 ms
vt
55 ms
peba9qoUFrLz1OT0H-PYjALUuEpTyoUstqEm5AMlJo4.ttf
8 ms
g46X4VH_KHOWAAa-HpnGPsDdSZkkecOE1hvV7ZHvhyU.ttf
4 ms
Q_pTky3Sc3ubRibGToTAYkqE9xuTzT7IX8WsnCRxGBg.ttf
6 ms
UyYrYy3ltEffJV9QueSi4T3qrkUnfUKy4CY5bK9uBIM.ttf
14 ms
index_client.php
1847 ms
ico-taxi.png
234 ms
ico-taxi-red.png
219 ms
QuotaService.RecordEvent
26 ms
citytaxi.az SEO score
EN
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citytaxi.az can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Russian language. Our system also found out that Citytaxi.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.
citytaxi.az
Open Graph description is not detected on the main page of Citytaxi. 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: