3.4 sec in total
227 ms
2.9 sec
182 ms
Click here to check amazing DB SCHENKER content for China. Otherwise, check out these important facts you probably never knew about dbschenker.com
Looking for a logistics and supply chain team who understands your business? From instant booking to advanced solutions specific to your industry, our global network and local expertise make the diffe...
Visit dbschenker.comWe analyzed Dbschenker.com page load time and found that the first response time was 227 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
dbschenker.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value6.5 s
9/100
25%
Value5.4 s
57/100
10%
Value970 ms
28/100
30%
Value0.125
83/100
15%
Value6.6 s
58/100
10%
227 ms
702 ms
343 ms
206 ms
213 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 86% of them (66 requests) were addressed to the original Dbschenker.com, 5% (4 requests) were made to Ecm-mediathek-deutschebahn.cdn.mediamid.com and 5% (4 requests) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Dbschenker.com.
Page size can be reduced by 264.9 kB (67%)
394.0 kB
129.2 kB
In fact, the total size of Dbschenker.com main page is 394.0 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. 55% of websites need less resources to load. Javascripts take 232.8 kB which makes up the majority of the site volume.
Potential reduce by 136.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 136.1 kB or 84% of the original size.
Potential reduce by 128.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 128.8 kB or 55% of the original size.
Number of requests can be reduced by 40 (56%)
71
31
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DB SCHENKER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.dbschenker.com
227 ms
702 ms
layout2010-common-dbtype,f456af5c30082d58f9529c9c300744b5ae95f2fd.css
343 ms
site-common,7eb1abc40115b6f12818e78a98d3b44fe8f9fb3a.css
206 ms
dbsearch.autocomplete.css.css
213 ms
schenker-eServices.css
211 ms
schenker-eServices-dbtype.css
212 ms
schenker-country-locator-DBSCHENKER-41.css
309 ms
jstree-styles-locator.css
314 ms
site-header-common,c4f76c17ece04c669b9bf9bef55dc9c34f17454a.js
798 ms
AutocompleteFragment.js
333 ms
video_embed.js
390 ms
e.js
235 ms
site-bottom-common,2d65b32aaf1de9d067763ebd0c19b209883ead61.js
299 ms
schenker-country-locator-DBSCHENKER-41.js
344 ms
liScroll.js
120 ms
etracker-searchterms_as_events.js
104 ms
data.png
105 ms
data.jpg
626 ms
data.png
105 ms
img2.jpg
173 ms
img2.jpg
614 ms
img2.jpg
174 ms
data.png
616 ms
data.png
616 ms
data.gif
620 ms
data.gif
617 ms
img1.jpg
618 ms
img1.jpg
620 ms
jwplayer.js
96 ms
data.gif
614 ms
data.woff
619 ms
data.woff
623 ms
data.png
612 ms
data.gif
578 ms
data.gif
577 ms
data.png
580 ms
data.png
580 ms
data.png
580 ms
data.png
579 ms
data.png
580 ms
data.png
580 ms
data.woff
653 ms
data.woff
579 ms
data.png
572 ms
data.png
628 ms
data.png
636 ms
data.png
630 ms
jquery-1.8.3.min.js
535 ms
520 ms
t.js
522 ms
data.png
546 ms
data.png
547 ms
db101705_7079_playlistsz.js
435 ms
video_embed.js
386 ms
qam-contacts-filterproxy.json
1132 ms
flashImg1.jpg
285 ms
flashImg1.jpg
293 ms
flashImg1.jpg
296 ms
flashImg1.jpg
395 ms
flashImg1.jpg
301 ms
flashImg1.jpg
585 ms
data.png
396 ms
data.png
398 ms
data.png
403 ms
data.png
495 ms
data.png
495 ms
data.png
498 ms
flashImg2.jpg
598 ms
data.png
594 ms
data.png
595 ms
flashImg2.jpg
889 ms
flashImg2.jpg
873 ms
data.png
693 ms
jwpsrv.js
79 ms
cnt_js.php
206 ms
cntcc
217 ms
dbschenker.com 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 input fields do not have accessible names
ARIA IDs are not unique
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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
dbschenker.com 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
dbschenker.com 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dbschenker.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Dbschenker.com 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.
dbschenker.com
Open Graph description is not detected on the main page of DB SCHENKER. 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: