2.8 sec in total
312 ms
2.3 sec
204 ms
Welcome to bus.hr homepage info - get ready to check Bus best content for Croatia right away, or after learning these important things about bus.hr
Autobus Zagreb Split Rijeka Zadar Pula Osijek Varaždin cijene karte. Autobusni kolodvor, vozni red vrijeme polaska i trajanje putovanja
Visit bus.hrWe analyzed Bus.hr page load time and found that the first response time was 312 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
bus.hr performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value6.7 s
8/100
25%
Value10.9 s
6/100
10%
Value4,180 ms
1/100
30%
Value0.363
30/100
15%
Value13.6 s
11/100
10%
312 ms
724 ms
268 ms
182 ms
183 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 59% of them (35 requests) were addressed to the original Bus.hr, 10% (6 requests) were made to Tpc.googlesyndication.com and 8% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Bus.hr.
Page size can be reduced by 252.9 kB (50%)
503.4 kB
250.6 kB
In fact, the total size of Bus.hr main page is 503.4 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. 45% of websites need less resources to load. Javascripts take 247.1 kB which makes up the majority of the site volume.
Potential reduce by 47.1 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 47.1 kB or 80% of the original size.
Potential reduce by 7.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. Bus images are well optimized though.
Potential reduce by 152.9 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 152.9 kB or 62% of the original size.
Potential reduce by 45.7 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. Bus.hr needs all CSS files to be minified and compressed as it can save up to 45.7 kB or 62% of the original size.
Number of requests can be reduced by 38 (67%)
57
19
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 31 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
bus.hr
312 ms
bus.hr
724 ms
dashicons.min.css
268 ms
wunderground.css
182 ms
nextgen_gallery_related_images.css
183 ms
wp-currency-converter.css
189 ms
mappress.css
279 ms
style.css
271 ms
youtube-shortcode.css
273 ms
vkalkulator.css
289 ms
jquery.js
446 ms
jquery-migrate.min.js
360 ms
DD_roundies.js
362 ms
jquery.ui.core.min.js
417 ms
jquery.ui.widget.min.js
387 ms
jquery.ui.position.min.js
449 ms
jquery.ui.menu.min.js
457 ms
jquery.ui.autocomplete.min.js
482 ms
widget.min.js
556 ms
ajax.js
533 ms
persist.js
537 ms
store.js
544 ms
ngg_store.js
575 ms
wp-currency-converter.js
621 ms
comment-reply.min.js
626 ms
lightbox_context.js
634 ms
vkalkulator.js
702 ms
bus.hr
1332 ms
adsbygoogle.js
16 ms
rtss-main.js
743 ms
logo.png
140 ms
inputbackgr.gif
140 ms
expand-down-white.gif
135 ms
english.jpg
378 ms
blablacar.jpg
180 ms
ca-pub-0530278623976951.js
123 ms
zrt_lookup.html
123 ms
show_ads_impl.js
76 ms
rtsocial-sprite-image.png
405 ms
ga.js
20 ms
__utm.gif
66 ms
fql.query
161 ms
count.json
88 ms
ads
426 ms
osd.js
26 ms
share
42 ms
ads
390 ms
ads
352 ms
m_js_controller.js
43 ms
abg.js
60 ms
ESA-160x600_driveby-white.jpg
78 ms
sbhK2lTE.js
53 ms
favicon
59 ms
googlelogo_color_112x36dp.png
34 ms
nessie_icon_tiamat_white.png
21 ms
cTrvNaRi.html
22 ms
s
17 ms
x_button_blue2.png
9 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
8 ms
bus.hr 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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
bus.hr 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
Page has valid source maps
bus.hr 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
Tap targets are not sized appropriately
HR
HR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bus.hr can be misinterpreted by Google and other search engines. Our service has detected that Croatian is used on the page, and it matches the claimed language. Our system also found out that Bus.hr 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.
bus.hr
Open Graph data is detected on the main page of Bus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: