3.1 sec in total
436 ms
2.3 sec
340 ms
Welcome to exbus.org homepage info - get ready to check Exbus best content right away, or after learning these important things about exbus.org
Sprawdź ExpressBus i wybierz tanie busy do Niemiec, Holandii oraz Belgii i dojedź szybko, bezpieczne i komfortowo pod wskazany adres!
Visit exbus.orgWe analyzed Exbus.org page load time and found that the first response time was 436 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
exbus.org performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value4.5 s
37/100
25%
Value3.7 s
86/100
10%
Value150 ms
95/100
30%
Value0.001
100/100
15%
Value4.4 s
83/100
10%
436 ms
112 ms
215 ms
216 ms
220 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 84% of them (52 requests) were addressed to the original Exbus.org, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Exbus.org.
Page size can be reduced by 445.8 kB (30%)
1.5 MB
1.0 MB
In fact, the total size of Exbus.org 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. 50% of websites need less resources to load. Images take 942.9 kB which makes up the majority of the site volume.
Potential reduce by 16.0 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 16.0 kB or 72% of the original size.
Potential reduce by 53.0 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. Exbus images are well optimized though.
Potential reduce by 215.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 215.7 kB or 68% of the original size.
Potential reduce by 161.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. Exbus.org needs all CSS files to be minified and compressed as it can save up to 161.2 kB or 88% of the original size.
Number of requests can be reduced by 33 (59%)
56
23
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Exbus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
exbus.org
436 ms
style.css
112 ms
styles.css
215 ms
jquery-ui-1.10.3.custom.css
216 ms
contact_form_maker_frontend.css
220 ms
shortcodes.css
221 ms
jquery.fancybox-1.3.4.css
225 ms
page_templates.css
227 ms
jquery.js
530 ms
jquery-migrate.min.js
318 ms
js
52 ms
if_gmap_front_end.js
327 ms
cfm_main_front_end.js
326 ms
css
34 ms
jquery-ui.min.js
52 ms
jquery.cycle.all.min.js
331 ms
jquery.easing.1.3.js
332 ms
superfish.js
422 ms
colorbox-1.css
439 ms
jquery.form.min.js
432 ms
scripts.js
442 ms
widget.min.js
442 ms
effect.min.js
580 ms
effect-shake.min.js
582 ms
jquery.easing-1.3.pack.js
583 ms
jquery.fancybox-1.3.4.pack.js
583 ms
et-ptemplates-frontend.js
584 ms
custom.js
630 ms
jquery.colorbox.js
636 ms
section-info.jpg
661 ms
header_bg.jpg
938 ms
phone-pl.png
117 ms
phone-nl.png
118 ms
logo.png
186 ms
left_arrow.png
188 ms
right_arrow.png
225 ms
ajax-loader.gif
227 ms
slider22.png
292 ms
slider3.png
399 ms
step1.jpg
660 ms
step2.jpg
674 ms
step3.jpg
610 ms
step4.jpg
823 ms
section-contact.jpg
1144 ms
maps.png
1205 ms
mail.png
769 ms
bus.png
786 ms
phone.png
878 ms
phone2.png
899 ms
logo2.png
931 ms
komfort.jpg
987 ms
AWM5wXtMJeRP-AcRTgT4qQ.ttf
22 ms
l1cOQ90roY9yC7voEhngDKCWcynf_cDxXwCLxiixG1c.ttf
33 ms
dI-qzxlKVQA6TUC5RKSb36CWcynf_cDxXwCLxiixG1c.ttf
33 ms
analytics.js
15 ms
ajax-loader.gif
912 ms
overlay.png
938 ms
collect
24 ms
collect
52 ms
ga-audiences
37 ms
controller2.png
111 ms
controller1.png
108 ms
exbus.org 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.
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.
exbus.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
exbus.org 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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exbus.org can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Exbus.org 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.
exbus.org
Open Graph data is detected on the main page of Exbus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: