8.3 sec in total
1.9 sec
6.1 sec
315 ms
Visit dfge.de now to see the best up-to-date DFGE content and also check out these interesting facts you probably never knew about dfge.de
Sustainability Intelligence Experten DFGE: Wir beraten und helfen bei CSR, Carbon Footprint für Unternehmen, CDP Teilnahme, UN Global Compact, EcoVadis etc.
Visit dfge.deWe analyzed Dfge.de page load time and found that the first response time was 1.9 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
dfge.de performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value11.6 s
0/100
25%
Value24.5 s
0/100
10%
Value17,950 ms
0/100
30%
Value0.039
100/100
15%
Value34.4 s
0/100
10%
1873 ms
188 ms
200 ms
200 ms
22 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 87% of them (55 requests) were addressed to the original Dfge.de, 5% (3 requests) were made to Fonts.googleapis.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Dfge.de.
Page size can be reduced by 1.6 MB (42%)
3.9 MB
2.2 MB
In fact, the total size of Dfge.de main page is 3.9 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. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 47.8 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 47.8 kB or 70% of the original size.
Potential reduce by 63.7 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. DFGE images are well optimized though.
Potential reduce by 613.5 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 613.5 kB or 68% of the original size.
Potential reduce by 882.4 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. Dfge.de needs all CSS files to be minified and compressed as it can save up to 882.4 kB or 82% of the original size.
Number of requests can be reduced by 47 (80%)
59
12
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DFGE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
www.dfge.de
1873 ms
language-selector.css
188 ms
validationEngine.jquery.css
200 ms
layerslider.css
200 ms
css
22 ms
styles.css
222 ms
go_pricing_styles.css
324 ms
mediaelementplayer.min.css
288 ms
mediaelementplayer.css
292 ms
tp_twitter_plugin.css
294 ms
settings.css
333 ms
dynamic-captions.css
364 ms
static-captions.css
381 ms
prettyPhoto.css
393 ms
default.css
391 ms
js_composer.css
647 ms
css
30 ms
css
43 ms
main.min.css
933 ms
font-awesome.min.css
481 ms
custom-86e0ad966c.css
1048 ms
media.min.css
492 ms
royalslider.css
547 ms
style.css
575 ms
jquery.js
686 ms
jquery-migrate.min.js
661 ms
layerslider.kreaturamedia.jquery.js
763 ms
greensock.js
758 ms
layerslider.transitions.js
776 ms
go_pricing_scripts.js
783 ms
jquery.themepunch.plugins.min.js
978 ms
jquery.themepunch.revolution.min.js
959 ms
jquery.prettyPhoto.js
891 ms
EasyGalleryLoader.js
883 ms
modernizr.js
985 ms
svg-icons.min.js
1007 ms
wp-emoji-release.min.js
1034 ms
jquery.form.min.js
946 ms
scripts.js
947 ms
mediaelement-and-player.min.js
1007 ms
wp-mediaelement.js
948 ms
jquery.royalslider.min.js
946 ms
plugins.min.js
1005 ms
desktop-tablet.min.js
929 ms
desktop.min.js
960 ms
main.min.js
1330 ms
sitepress.js
967 ms
js_composer_front.js
995 ms
waypoints.min.js
972 ms
ga.js
85 ms
de.png
209 ms
en.png
213 ms
dfge_logo_200px_png24_transparent.png
238 ms
header-window.png
1349 ms
window_image.jpg
1119 ms
sustainability-check.png
635 ms
EcoDashboard_small.png
315 ms
dfge_logo_150px_png24_transparent.png
337 ms
__utm.gif
59 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
20 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
20 ms
fontawesome-webfont.woff
544 ms
dfge.de 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.
dfge.de 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
Page has valid source maps
dfge.de 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dfge.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Dfge.de 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.
dfge.de
Open Graph data is detected on the main page of DFGE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: