3.8 sec in total
487 ms
3.2 sec
125 ms
Welcome to mainline.eu homepage info - get ready to check Mainline best content right away, or after learning these important things about mainline.eu
We offer a full range of supply chain services, from European groupage, distribution and logistic services to global air and ocean freight services
Visit mainline.euWe analyzed Mainline.eu page load time and found that the first response time was 487 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
mainline.eu performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value17.2 s
0/100
25%
Value7.5 s
26/100
10%
Value620 ms
48/100
30%
Value0.492
17/100
15%
Value16.7 s
5/100
10%
487 ms
1188 ms
543 ms
20 ms
733 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Mainline.eu, 86% (36 requests) were made to Wimbosman.com and 10% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Wimbosman.com.
Page size can be reduced by 299.5 kB (21%)
1.4 MB
1.1 MB
In fact, the total size of Mainline.eu main page is 1.4 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. 20% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 20.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 20.6 kB or 69% of the original size.
Potential reduce by 30.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. Mainline images are well optimized though.
Potential reduce by 161.1 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 161.1 kB or 62% of the original size.
Potential reduce by 87.8 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. Mainline.eu needs all CSS files to be minified and compressed as it can save up to 87.8 kB or 84% of the original size.
Number of requests can be reduced by 21 (53%)
40
19
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mainline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
mainline.eu
487 ms
www.wimbosman.com
1188 ms
style.css
543 ms
jsapi
20 ms
scripts.js
733 ms
validators.js
90 ms
ga.js
18 ms
analytics.js
18 ms
bg.jpg
89 ms
67062ae6-b152-4655-8b34-a96a6880b53f.jpg
88 ms
bg_selectwebsite.jpg
96 ms
selectwebsite_dropdown.png
175 ms
bg_selecttaal.jpg
176 ms
en.jpg
187 ms
selecttaal_dropdown.png
262 ms
zoekpopupknop.png
262 ms
zoekpopup.png
264 ms
eee6cdc5-af2d-43a8-a90a-352b0077bc30.jpg
266 ms
hoofdmenu_basic_hassub.png
266 ms
3d6547ea-ae90-429a-aebc-c2ac7cbfdbc6.jpg
279 ms
39858887-d98e-4ea9-bc9c-e5da35419c3b.jpg
775 ms
f03251ee-b663-4143-b536-39134d8f1e8e.jpg
933 ms
35abed43-1491-40ac-a60f-278b7cfd13b4.jpg
901 ms
26651c34-dba5-4fa2-b111-8be4175d0ab9.jpg
524 ms
01d983fb-fcbc-4064-a624-0c797eda54e4.jpg
351 ms
4b292c84-a758-4483-a43f-93cda6a37435.jpg
462 ms
7f4a88f4-6d9b-4969-bc33-6eae0fbfaaa3.jpg
440 ms
47e56800-2d39-4a62-9613-8e10233174cf.jpg
526 ms
blok_bg.jpg
555 ms
quicklink.png
610 ms
69fb9078-0c97-4e3c-968a-49605d5537e6.jpg
698 ms
tracktrace.png
650 ms
tracktracesearch.png
697 ms
twitter.jpg
743 ms
facebook.jpg
784 ms
linkedin.jpg
786 ms
films.jpg
837 ms
footer_bg.jpg
855 ms
__utm.gif
11 ms
collect
13 ms
slideshow_aan.png
822 ms
slideshow_normal.png
823 ms
mainline.eu 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 have valid values
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
mainline.eu 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
mainline.eu SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mainline.eu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mainline.eu 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.
mainline.eu
Open Graph description is not detected on the main page of Mainline. 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: