1.5 sec in total
27 ms
1 sec
429 ms
Visit draeger.com now to see the best up-to-date Draeger content for Germany and also check out these interesting facts you probably never knew about draeger.com
Visit draeger.comWe analyzed Draeger.com page load time and found that the first response time was 27 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
draeger.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value9.3 s
1/100
25%
Value8.3 s
19/100
10%
Value5,390 ms
0/100
30%
Value0.017
100/100
15%
Value15.8 s
6/100
10%
27 ms
112 ms
50 ms
8 ms
20 ms
Our browser made a total of 24 requests to load all elements on the main page. We found that 96% of them (23 requests) were addressed to the original Draeger.com, 4% (1 request) were made to Dragerwerk.122.2o7.net. The less responsive or slowest element that took the longest time to load (154 ms) belongs to the original domain Draeger.com.
Page size can be reduced by 824.7 kB (79%)
1.0 MB
224.5 kB
In fact, the total size of Draeger.com main page is 1.0 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. 60% of websites need less resources to load. CSS take 575.6 kB which makes up the majority of the site volume.
Potential reduce by 54.5 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 54.5 kB or 79% of the original size.
Potential reduce by 904 B
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. Draeger images are well optimized though.
Potential reduce by 277.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 277.5 kB or 74% of the original size.
Potential reduce by 491.7 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. Draeger.com needs all CSS files to be minified and compressed as it can save up to 491.7 kB or 85% of the original size.
Number of requests can be reduced by 16 (70%)
23
7
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Draeger. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
default.aspx
27 ms
corev4.css
112 ms
SPCss
50 ms
jqueryCss
8 ms
DraegerCss
20 ms
jquery
154 ms
DraegerJs
28 ms
DraegerLayoutsCss
43 ms
s_code.js
27 ms
dte.js
33 ms
WebResource.axd
108 ms
blank.js
32 ms
init.js
20 ms
ScriptResource.axd
13 ms
ScriptResource.axd
40 ms
logo_big.gif
21 ms
header-splitpage-EN.jpg
22 ms
s61944732922129
95 ms
Print.css
14 ms
background.gif
41 ms
icons.png
37 ms
sp.core.js
22 ms
ScriptResx.ashx
16 ms
sp.ui.dialog.js
24 ms
draeger.com accessibility score
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
draeger.com 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
Missing source maps for large first-party JavaScript
draeger.com 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
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Draeger.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Draeger.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.
draeger.com
Open Graph description is not detected on the main page of Draeger. 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: