5.7 sec in total
426 ms
5.1 sec
157 ms
Click here to check amazing DB Schenker content. Otherwise, check out these important facts you probably never knew about dbschenker.kr
Visit dbschenker.krWe analyzed Dbschenker.kr page load time and found that the first response time was 426 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
dbschenker.kr performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value11.9 s
0/100
25%
Value11.4 s
5/100
10%
Value8,180 ms
0/100
30%
Value0.122
84/100
15%
Value14.0 s
10/100
10%
426 ms
233 ms
350 ms
200 ms
213 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 95% of them (55 requests) were addressed to the original Dbschenker.kr, 2% (1 request) were made to Code.etracker.com and 2% (1 request) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Dbschenker.kr.
Page size can be reduced by 69.0 kB (73%)
94.6 kB
25.6 kB
In fact, the total size of Dbschenker.kr main page is 94.6 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. 40% of websites need less resources to load. Javascripts take 51.5 kB which makes up the majority of the site volume.
Potential reduce by 35.7 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 35.7 kB or 83% of the original size.
Potential reduce by 33.3 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 33.3 kB or 65% of the original size.
Number of requests can be reduced by 37 (69%)
54
17
The browser has sent 54 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 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
dbschenker.kr
426 ms
233 ms
layout2010-common,fbf9fcf773b667a6f20c6c83d269db91f9b5ffbd.css
350 ms
theme_default.css.css
200 ms
bahnhof-styles.css
213 ms
dbsearch.autocomplete.css.css
202 ms
leaflet.0.7.7.css.css
204 ms
modernizr-2.5.3.js
217 ms
swfobject.js.js
299 ms
jquery-1.7.1.js
662 ms
jquery.easing.js.js
300 ms
jquery.json-2.3.js
308 ms
typeAhead.js
315 ms
global-header-utils.js
407 ms
sliderStage.js.js
407 ms
AutocompleteFragment.js
422 ms
disableSearchHighlight.js
422 ms
jquery-custom-plugins.js
357 ms
jquery-ui-1.8.18.custom.min.js
648 ms
jquery.accessible.tabs-1.9.4.custom.js
421 ms
jquery.syncheight.js.js
416 ms
shadowbox.js.js
522 ms
jquery.cookie.js.js
439 ms
global-bottom-utils.js
507 ms
cookieBanner.js
514 ms
leaflet.0.7.7.js.js
647 ms
bahnhof_de_openstreetmap.js
628 ms
data.png
101 ms
data.gif
101 ms
data.png
101 ms
img4.jpg
225 ms
img4.jpg
137 ms
img4.jpg
169 ms
data.png
294 ms
img4.jpg
200 ms
img4.jpg
200 ms
data.gif
236 ms
data.png
258 ms
data.jpg
291 ms
data.png
290 ms
data.jpg
315 ms
data.gif
326 ms
data.png
356 ms
data.png
383 ms
data.png
387 ms
t.js
523 ms
data.woff
348 ms
data.woff
467 ms
cnt_js.php
199 ms
piwik.js
486 ms
flashImg1.jpg
3235 ms
flashImg1.jpg
501 ms
flashImg1.jpg
501 ms
flashImg1.jpg
597 ms
data.png
101 ms
data.png
104 ms
data.png
200 ms
data.png
202 ms
dbschenker.kr 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.kr 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.kr 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
KO
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dbschenker.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed German language. Our system also found out that Dbschenker.kr 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.kr
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: