3 sec in total
405 ms
2.5 sec
138 ms
Visit patentinformation.de now to see the best up-to-date Patentinformation content and also check out these interesting facts you probably never knew about patentinformation.de
Internetauftritt der Arbeitsgemeinschaft Deutscher Patentinformationszentren e.V. (ArgePIZ), den autorisierten Kooperationspartnern des Deutschen Patent- und Markenamtes (DPMA) und ersten Ansprechpart...
Visit patentinformation.deWe analyzed Patentinformation.de page load time and found that the first response time was 405 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
patentinformation.de performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value3.7 s
57/100
25%
Value9.9 s
10/100
10%
Value590 ms
51/100
30%
Value0.043
99/100
15%
Value10.1 s
26/100
10%
405 ms
380 ms
290 ms
187 ms
376 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Patentinformation.de, 98% (64 requests) were made to Piznet.de. The less responsive or slowest element that took the longest time to load (774 ms) relates to the external source Piznet.de.
Page size can be reduced by 579.8 kB (63%)
917.1 kB
337.3 kB
In fact, the total size of Patentinformation.de main page is 917.1 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. 30% of websites need less resources to load. Javascripts take 450.7 kB which makes up the majority of the site volume.
Potential reduce by 61.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. This page needs HTML code to be minified as it can gain 16.8 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 61.1 kB or 86% of the original size.
Potential reduce by 114.3 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. Obviously, Patentinformation needs image optimization as it can save up to 114.3 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 354.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 354.4 kB or 79% of the original size.
Potential reduce by 50.1 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. Patentinformation.de needs all CSS files to be minified and compressed as it can save up to 50.1 kB or 86% of the original size.
Number of requests can be reduced by 10 (16%)
63
53
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Patentinformation. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
{{url}}
{{time}} ms
patentinformation.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.
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 IDs are not unique
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
patentinformation.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
patentinformation.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 Patentinformation.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 Patentinformation.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.
{{og_description}}
patentinformation.de
Open Graph description is not detected on the main page of Patentinformation. 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: