4.8 sec in total
352 ms
4.2 sec
243 ms
Click here to check amazing Workbus content for France. Otherwise, check out these important facts you probably never knew about workbus.nl
Zoals je ziet is de website van Workbus niet meer in de lucht, geen paniek: er is technisch niets mis gegaan! Wij zijn simpelweg per 1 januari 2023 omgedoopt tot Logistic Force! Oftewel een nieuwe loo...
Visit workbus.nlWe analyzed Workbus.nl page load time and found that the first response time was 352 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
workbus.nl performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value9.9 s
0/100
25%
Value7.6 s
25/100
10%
Value2,600 ms
4/100
30%
Value1.567
0/100
15%
Value18.9 s
3/100
10%
352 ms
906 ms
932 ms
191 ms
465 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 47% of them (32 requests) were addressed to the original Workbus.nl, 15% (10 requests) were made to Static.xx.fbcdn.net and 15% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (932 ms) belongs to the original domain Workbus.nl.
Page size can be reduced by 861.8 kB (72%)
1.2 MB
328.0 kB
In fact, the total size of Workbus.nl main page is 1.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. 60% of websites need less resources to load. CSS take 569.4 kB which makes up the majority of the site volume.
Potential reduce by 111.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 111.6 kB or 80% of the original size.
Potential reduce by 2.3 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. Workbus images are well optimized though.
Potential reduce by 245.8 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 245.8 kB or 72% of the original size.
Potential reduce by 502.0 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. Workbus.nl needs all CSS files to be minified and compressed as it can save up to 502.0 kB or 88% of the original size.
Number of requests can be reduced by 29 (52%)
56
27
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Workbus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
workbus.nl
352 ms
www.workbus.nl
906 ms
www.workbus.nl
932 ms
DXR.axd
191 ms
DXR.axd
465 ms
css.axd
450 ms
brz8jxn.js
130 ms
modernizr-2.8.3.min.js
397 ms
WebResource.axd
186 ms
jquery.min.js
61 ms
jslib.axd
202 ms
DXR.axd
446 ms
DXR.axd
405 ms
jquery-ui.min.js
78 ms
WebResource.axd
287 ms
WebResource.axd
404 ms
WebResource.axd
404 ms
WebResource.axd
452 ms
WebResource.axd
450 ms
WebResource.axd
452 ms
WebResource.axd
461 ms
DXR.axd
899 ms
7
91 ms
analytics.js
171 ms
ajax-loader.gif
222 ms
sprite.svg
222 ms
workbus-video.jpg
604 ms
logo.svg
218 ms
DXR.axd
205 ms
DXR.axd
266 ms
vcu.svg
284 ms
nbbu.svg
287 ms
sna.svg
291 ms
cNTIBvqixGkADTVszmEaT4sD8Wx99zYUweTuqOL9rQSff4nygsMdeMI6MK6g5Mb.eot
99 ms
mP1AIpRwXMwCrGwcqVMDCsFp1l8709f9vC_xk3S93I6ff4nygsMdeMI6MK6g5Msfb2syZRsRjcbajhBRFe4yZQqXF2ByFQFKZQZ8wc4cFRwo52bkFRZ8wRZRFRB8Z2juwQbuZc9XFebXwcBcw28KjRI.eot
119 ms
theme.woff
457 ms
0rOPTE5pAbnBSQclvjR2l1O_xRU2Wu9FowyTKZ9PjiSffHRygsMdeMI6MK6g5MS.eot
166 ms
A-rYBL3CHL7fCzD2dZsEdqmlUk1mbH7N-4vcYdo-TMXffHdygsMdeMI6MK6g5MZfb2syZRsRjcbajhBRFe4yZQqXF2ByFQFKZQZ8wc4cFRwo52bkFRZ8wRZRFRB8Z2juwQbuZc9XFebXwcBcw28KjRI.eot
150 ms
SIxCYxZ2iAyxBZPVdZHNSUwFaKqzdwQK__3zACkPYNXffHRygsMdeMI6MK6g5Mifb2syZRsRjcbajhBRFe4yZQqXF2ByFQFKZQZ8wc4cFRwo52bkFRZ8wRZRFRB8Z2juwQbuZc9XFebXwcBcw28KjRI.eot
164 ms
devex.woff
456 ms
collect
40 ms
sdk.js
158 ms
wxmBUSzXl02mhqweG4tAluZQKeC6Gm6xVZ0ty7CIH0IffHdygsMdeMI6MK6g5Mj.eot
108 ms
css.axd
112 ms
111 ms
xd_arbiter.php
132 ms
img_validation_error.png
90 ms
page.php
116 ms
Xr6T9jq_7DM.css
84 ms
q68gy-v_YMF.js
120 ms
YvxwM8R7ol8.js
172 ms
ihptErjAmMX.js
156 ms
11215157_929529510453852_1192698176683426325_n.jpg
130 ms
10881921_791475934259211_112438821544791000_n.jpg
57 ms
261396_105758912853987_8051239_n.jpg
56 ms
12187837_515817578591497_3949801431209851681_n.jpg
82 ms
1507665_10152104301194522_2114727318_n.jpg
57 ms
10881566_640804652714893_799918193526614370_n.jpg
56 ms
10354686_10150004552801856_220367501106153455_n.jpg
71 ms
11130178_834242709998003_1085579874012287861_n.jpg
72 ms
10300417_882574181860579_7909325325754001335_n.jpg
75 ms
1507129_483867151724856_481139805_n.jpg
73 ms
wL6VQj7Ab77.png
19 ms
s7jcwEQH7Sx.png
20 ms
R9a_DtVRZgv.js
20 ms
cUDgRFxaoIk.js
21 ms
0JBr1QHp8Gi.js
20 ms
kDOzhTr2W91.js
34 ms
workbus.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
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.
workbus.nl 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
Missing source maps for large first-party JavaScript
workbus.nl 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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Workbus.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 Workbus.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.
workbus.nl
Open Graph description is not detected on the main page of Workbus. 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: