6 sec in total
981 ms
4.4 sec
681 ms
Welcome to datenrecorder.de homepage info - get ready to check Datenrecorder best content right away, or after learning these important things about datenrecorder.de
Hier haben Sie die Möglichkeit ein Produkt aus den Produktgruppen aus der Navigation auszuwählen oder einen Suchbegriff einzugeben.
Visit datenrecorder.deWe analyzed Datenrecorder.de page load time and found that the first response time was 981 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
datenrecorder.de performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value5.8 s
16/100
25%
Value4.4 s
74/100
10%
Value110 ms
97/100
30%
Value0.116
85/100
15%
Value4.7 s
80/100
10%
981 ms
218 ms
3073 ms
3164 ms
3488 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that all of those requests were addressed to Datenrecorder.de and no external sources were called. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Datenrecorder.de.
Page size can be reduced by 67.4 kB (25%)
270.7 kB
203.3 kB
In fact, the total size of Datenrecorder.de main page is 270.7 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. 20% of websites need less resources to load. Images take 199.1 kB which makes up the majority of the site volume.
Potential reduce by 54.4 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.4 kB or 89% of the original size.
Potential reduce by 3.6 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. Datenrecorder images are well optimized though.
Potential reduce by 9.5 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. Datenrecorder.de needs all CSS files to be minified and compressed as it can save up to 9.5 kB or 90% of the original size.
We found no issues to fix!
24
24
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Datenrecorder. According to our analytics all requests are already optimized.
datenrecorder.de
981 ms
w3sheet.css
218 ms
spacer.gif
3073 ms
wuntronic_logo.gif
3164 ms
navi_arrow.gif
3488 ms
flag_en.gif
3485 ms
adresse.gif
3487 ms
s_serie.GIF
531 ms
S0110.jpg
721 ms
pdf.gif
818 ms
S0111.jpg
913 ms
S0121.jpg
923 ms
S0122.jpg
1018 ms
S0141.jpg
1121 ms
S6011.jpg
1218 ms
S3541.jpg
1313 ms
S3120.jpg
1409 ms
S3121.jpg
1506 ms
S3631.jpg
1601 ms
ms5d_k.jpg
1698 ms
D3633.jpg
1887 ms
T0110.jpg
1984 ms
crv_ssl.gif
2080 ms
background.gif
2042 ms
banner_top.jpg
2232 ms
datenrecorder.de 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
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.
datenrecorder.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
datenrecorder.de 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
Document doesn't have a valid hreflang
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 doesn't use 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 Datenrecorder.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 Datenrecorder.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.
datenrecorder.de
Open Graph description is not detected on the main page of Datenrecorder. 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: