4.2 sec in total
255 ms
3.5 sec
454 ms
Click here to check amazing Dfs content. Otherwise, check out these important facts you probably never knew about dfs.one
Discover synergies in modern logistics.
Visit dfs.oneWe analyzed Dfs.one page load time and found that the first response time was 255 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
dfs.one performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value26.9 s
0/100
25%
Value15.1 s
1/100
10%
Value510 ms
57/100
30%
Value0
100/100
15%
Value15.1 s
7/100
10%
255 ms
168 ms
54 ms
211 ms
293 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 95% of them (63 requests) were addressed to the original Dfs.one, 3% (2 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Dfs.one.
Page size can be reduced by 1.5 MB (71%)
2.1 MB
602.9 kB
In fact, the total size of Dfs.one main page is 2.1 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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 106.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 106.1 kB or 82% of the original size.
Potential reduce by 13.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. Dfs images are well optimized though.
Potential reduce by 799.4 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 799.4 kB or 73% of the original size.
Potential reduce by 571.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. Dfs.one needs all CSS files to be minified and compressed as it can save up to 571.0 kB or 85% of the original size.
Number of requests can be reduced by 46 (72%)
64
18
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dfs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
dfs.one
255 ms
168 ms
webfont.js
54 ms
wp-emoji-release.min.js
211 ms
mappress.css
293 ms
settings.css
384 ms
style.css
981 ms
jquery-ui-1.11.4.custom.css
399 ms
mediaelementplayer.min.css
566 ms
wp-mediaelement.css
319 ms
wpv-pagination.css
386 ms
bootstrap.min.css
522 ms
ss-gizmo.css
486 ms
font-awesome.min.css
483 ms
style.css
506 ms
responsive.css
675 ms
jquery.js
790 ms
jquery-migrate.min.js
611 ms
jquery.themepunch.tools.min.js
719 ms
jquery.themepunch.revolution.min.js
766 ms
svg-inline-min.js
711 ms
form.min.js
765 ms
love-it.js
816 ms
jquery.cookie.js
815 ms
bootstrap.min.js
872 ms
jquery-ui-1.10.2.custom.min.js
865 ms
jquery.flexslider-min.js
881 ms
jquery.easing.js
912 ms
owl.carousel.min.js
916 ms
theme-scripts.js
1154 ms
ilightbox.min.js
1135 ms
jquery.isotope.min.js
1132 ms
imagesloaded.js
1133 ms
jquery.infinitescroll.min.js
1132 ms
functions.js
1240 ms
jquery.sonar.min.js
1133 ms
lazy-load.js
1134 ms
core.min.js
1133 ms
datepicker.min.js
1244 ms
css
66 ms
mediaelement-and-player.min.js
1108 ms
wp-mediaelement.js
971 ms
underscore.min.js
942 ms
wp-util.min.js
887 ms
backbone.min.js
905 ms
wp-playlist.js
912 ms
wpv-pagination-embedded.js
940 ms
wp-embed.min.js
858 ms
css
13 ms
dfs_2015-logo-und-schriftzug-v2_v2-standard1.svg
268 ms
dfs_2015-HXXF68913475SV.jpg
302 ms
dfs_2015-logo-mit-schriftzug_zentriert-weiss-517x330.png
315 ms
HXXO20160311175913-4-1600-480x320.jpg
602 ms
HXXO20160311182636-1600-480x267.jpg
633 ms
img_9721-480x360.jpg
604 ms
dfs_2015-prozesskette-10-1.svg
609 ms
crease.svg
605 ms
dfs_2015-zentrallager_pfade-EN.svg
617 ms
dfs_2015-zentralbelieferung_pfade-EN-1.svg
624 ms
dfs_2015-synergien-04.svg
634 ms
dfs_2016-icons-auswirkungen-02.svg
632 ms
loading.gif
631 ms
fontawesome-webfont.woff
692 ms
ss-gizmo.woff
590 ms
piwik.js
691 ms
loader.gif
150 ms
dfs.one 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 match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
dfs.one best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
dfs.one SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
Tap targets are not sized appropriately
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dfs.one can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Dfs.one 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.
dfs.one
Open Graph data is detected on the main page of Dfs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: