5 sec in total
781 ms
4 sec
215 ms
Welcome to bakubus.az homepage info - get ready to check Baku Bus best content for Azerbaijan right away, or after learning these important things about bakubus.az
Sizi gələcəyə aparır
Visit bakubus.azWe analyzed Bakubus.az page load time and found that the first response time was 781 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
bakubus.az performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value13.0 s
0/100
25%
Value12.6 s
3/100
10%
Value360 ms
72/100
30%
Value0.003
100/100
15%
Value12.4 s
15/100
10%
781 ms
497 ms
491 ms
492 ms
661 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 38% of them (44 requests) were addressed to the original Bakubus.az, 48% (56 requests) were made to Maps.googleapis.com and 8% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Bakubus.az.
Page size can be reduced by 1.3 MB (61%)
2.2 MB
850.5 kB
In fact, the total size of Bakubus.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. 65% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 108.6 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 108.6 kB or 92% of the original size.
Potential reduce by 27.2 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. Baku Bus images are well optimized though.
Potential reduce by 984.7 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 984.7 kB or 68% of the original size.
Potential reduce by 190.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. Bakubus.az needs all CSS files to be minified and compressed as it can save up to 190.4 kB or 84% of the original size.
Number of requests can be reduced by 58 (53%)
109
51
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Baku Bus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and as a result speed up the page load time.
bakubus.az
781 ms
main.css
497 ms
jquery.min.js
491 ms
jquery-1.10.2.min.js
492 ms
jquery-ui-1.10.4.min.js
661 ms
leaflet.js
598 ms
jquery.bakubus.js
335 ms
js
78 ms
modernizr.min.js
658 ms
bootstrap.min.js
823 ms
richmarker.min.js
820 ms
bootstrap-slider.min.js
821 ms
jquery.nanoscroller.min.js
830 ms
imagesloaded.pkgd.min.js
980 ms
bootstrap-select.min.js
996 ms
masonry.pkgd.min.js
1144 ms
jstorage.min.js
1149 ms
owl.carousel.min.js
1151 ms
pano2vr_player.min.js
1326 ms
object2vr_player.js
1312 ms
skin.js
1365 ms
skin.min.js
1466 ms
magnum.js
1467 ms
viewportSize.min.js
1471 ms
Polyline.encoded.min.js
1633 ms
analytics.js
60 ms
logo.png
1180 ms
hamburger.png
1181 ms
x.png
1360 ms
f.png
1358 ms
y.png
1359 ms
o_1a4e3h1lktr1i01vf16h21a9ta.png
1509 ms
o_1a4e7ndodebh1l7216qm1gvi1jp5a.png
1508 ms
o_1a4e3findan71b40s9r1u6e18gna.png
1507 ms
o_1a4e3ah401iib1qcj1hmg1l0f1dchi.png
1659 ms
rotator.png
1659 ms
bus-icon.png
1658 ms
lupa-icon.png
1816 ms
location-icon.png
1817 ms
result-bg.png
1821 ms
contact-red.png
1977 ms
GeometriaAZ.ttf
2584 ms
Geometria-BoldAZ.ttf
2613 ms
collect
13 ms
common.js
73 ms
map.js
94 ms
util.js
138 ms
geometry.js
135 ms
poly.js
137 ms
marker.js
133 ms
controls.js
75 ms
places_impl.js
72 ms
sprites.png
1127 ms
carousel-left.png
976 ms
carousel-right.png
1130 ms
onion.js
29 ms
openhand_8_8.cur
268 ms
infowindow.js
107 ms
ViewportInfoService.GetViewportInfo
152 ms
stats.js
151 ms
css
206 ms
transparent.png
151 ms
powered-by-google-on-white3.png
157 ms
autocomplete-icons.png
158 ms
undo_poly.png
108 ms
google4.png
109 ms
mapcnt6.png
118 ms
sv5.png
121 ms
tmapctrl.png
99 ms
vt
121 ms
vt
88 ms
vt
89 ms
vt
88 ms
vt
98 ms
vt
89 ms
vt
161 ms
vt
155 ms
vt
152 ms
vt
162 ms
vt
156 ms
vt
164 ms
vt
221 ms
vt
198 ms
vt
227 ms
vt
213 ms
vt
219 ms
vt
199 ms
vt
229 ms
vt
253 ms
vt
250 ms
vt
273 ms
vt
244 ms
vt
279 ms
vt
267 ms
vt
274 ms
vt
298 ms
vt
286 ms
vt
321 ms
vt
303 ms
vt
316 ms
vt
301 ms
vt
308 ms
vt
348 ms
vt
326 ms
vt
312 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
46 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
53 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
56 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
61 ms
vt
269 ms
vt
262 ms
vt
264 ms
vt
256 ms
vt
281 ms
vt
255 ms
AuthenticationService.Authenticate
265 ms
bakubus.az accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
bakubus.az best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
bakubus.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
AZ
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bakubus.az can be misinterpreted by Google and other search engines. Our service has detected that Azerbaijani is used on the page, and it does not match the claimed English language. Our system also found out that Bakubus.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.
bakubus.az
Open Graph description is not detected on the main page of Baku Bus. 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: