6.6 sec in total
702 ms
4.9 sec
1 sec
Click here to check amazing BLUSBUS content. Otherwise, check out these important facts you probably never knew about blusbus.nl
Visit blusbus.nlWe analyzed Blusbus.nl page load time and found that the first response time was 702 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
blusbus.nl performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value19.4 s
0/100
25%
Value13.1 s
2/100
10%
Value350 ms
73/100
30%
Value0
100/100
15%
Value13.0 s
12/100
10%
702 ms
120 ms
182 ms
185 ms
188 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 87% of them (75 requests) were addressed to the original Blusbus.nl, 6% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Blusbus.nl.
Page size can be reduced by 663.9 kB (23%)
2.9 MB
2.2 MB
In fact, the total size of Blusbus.nl main page is 2.9 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 39.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 39.6 kB or 80% of the original size.
Potential reduce by 25.5 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. BLUSBUS images are well optimized though.
Potential reduce by 445.6 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 445.6 kB or 70% of the original size.
Potential reduce by 153.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. Blusbus.nl needs all CSS files to be minified and compressed as it can save up to 153.2 kB or 84% of the original size.
Number of requests can be reduced by 38 (48%)
80
42
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BLUSBUS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.blusbus.nl
702 ms
wp-emoji-release.min.js
120 ms
styles.css
182 ms
cuteslider.css
185 ms
ftg.css
188 ms
font-awesome.css
15 ms
settings.css
457 ms
css
23 ms
base.css
1411 ms
skeleton-1200.css
214 ms
layout.css
277 ms
prettyPhoto.css
267 ms
flexslider.css
296 ms
supersized.css
306 ms
supersized.shutter.css
353 ms
fullslider.css
363 ms
nzs-frame-media-1200.css
384 ms
nzs-custom-media.css
397 ms
style.css
439 ms
mobile-media-queries.css
462 ms
jquery.js
571 ms
jquery-migrate.min.js
490 ms
modernizr.min.js
11 ms
cute.slider.js
621 ms
cute.transitions.all.js
542 ms
respond.min.js
11 ms
jquery.themepunch.tools.min.js
652 ms
jquery.themepunch.revolution.min.js
693 ms
style.css
647 ms
jquery.form.min.js
667 ms
scripts.js
712 ms
jquery.finalTilesGallery.js
748 ms
supersized.3.2.7.js
743 ms
supersized.shutter.min.js
766 ms
jquery.flexslider-min.js
797 ms
scripts.js
812 ms
jquery.prettyPhoto.js
840 ms
main.js
844 ms
wp-embed.min.js
858 ms
script.js
903 ms
blusbus-logo5.png
185 ms
back.png
128 ms
forward.png
129 ms
slide.jpg
745 ms
logo2-300x66.png
128 ms
trouwbus.jpg
587 ms
Mysteryland-18-300x199.jpg
279 ms
Mysteryland-11-150x150.jpg
198 ms
Mysteryland-12-300x199.jpg
283 ms
Mysteryland-4-150x150.jpg
272 ms
Mysteryland-1-150x150.jpg
292 ms
Mysteryland-2-150x150.jpg
372 ms
Mysteryland-3-150x150.jpg
377 ms
Mysteryland-6-150x150.jpg
388 ms
Mysteryland-7-150x150.jpg
386 ms
Mysteryland-8-150x150.jpg
472 ms
Mysteryland-9-150x150.jpg
464 ms
Mysteryland-10-150x150.jpg
493 ms
Mysteryland-5-250x250.jpg
568 ms
Mysteryland-13-150x150.jpg
550 ms
Mysteryland-14-150x150.jpg
572 ms
Mysteryland-15-150x150.jpg
581 ms
Mysteryland-16-150x150.jpg
645 ms
Mysteryland-17-150x150.jpg
656 ms
MarkDaams_045-150x150.jpg
659 ms
MarkDaams_044-150x150.jpg
668 ms
MarkDaams_052-150x150.jpg
679 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
6 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
105 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
105 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
106 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
106 ms
Mysteryland-19.jpg
1231 ms
sep.png
719 ms
mail.png
745 ms
close.png
761 ms
loading.gif
777 ms
prev.png
810 ms
next.png
824 ms
analytics.js
78 ms
ajax-loader.gif
750 ms
progress.gif
759 ms
collect
12 ms
home.jpg
861 ms
home2.jpg
360 ms
busje.jpg
628 ms
blusbus.nl 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
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.
blusbus.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
General
Impact
Issue
Detected JavaScript libraries
blusbus.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blusbus.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Blusbus.nl 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.
blusbus.nl
Open Graph description is not detected on the main page of BLUSBUS. 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: