3.7 sec in total
472 ms
2.8 sec
520 ms
Click here to check amazing I 22 content for Germany. Otherwise, check out these important facts you probably never knew about i22.de
Mastering digital business – every day.
Visit i22.deWe analyzed I22.de page load time and found that the first response time was 472 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
i22.de performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value3.4 s
68/100
25%
Value5.2 s
60/100
10%
Value200 ms
89/100
30%
Value0.002
100/100
15%
Value5.7 s
68/100
10%
472 ms
414 ms
794 ms
292 ms
472 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 I22.de, 4% (1 request) were made to Images.ctfassets.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain I22.de.
Page size can be reduced by 56.6 kB (39%)
145.5 kB
88.8 kB
In fact, the total size of I22.de main page is 145.5 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 77.3 kB which makes up the majority of the site volume.
Potential reduce by 56.6 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 56.6 kB or 83% of the original size.
Potential reduce by 0 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. I 22 images are well optimized though.
Number of requests can be reduced by 14 (67%)
21
7
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I 22. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
i22.de
472 ms
i22.de
414 ms
www.i22.de
794 ms
3b31850c559e9e49.css
292 ms
fd9d1056-589e2e7f2840987a.js
472 ms
23-4838a88de1794334.js
383 ms
main-app-e51ff8dd76a46e0b.js
297 ms
653-0ba2afd6b119db6a.js
304 ms
877-b96c3364b8efde21.js
385 ms
layout-2dc39b44b76b8813.js
398 ms
c15bf2b0-c5f2ab0c4ce668d5.js
406 ms
97-b943b4f0706e0b61.js
572 ms
581-074cfa67b5e6e6b8.js
480 ms
error-0d82329c7b6d4f8e.js
500 ms
160b575a-8ee7f5da2d55101f.js
508 ms
940-cac3a11596e0ccbd.js
1137 ms
page-163c337bde086d6c.js
566 ms
polyfills-78c92fac7aa8fdd8.js
666 ms
webpack-1692fd4f63824229.js
595 ms
i22_pattern_footer_repeatable_Signal_Blue.svg
33 ms
image
465 ms
image
101 ms
image
106 ms
image
96 ms
i22.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
ARIA IDs are not unique
i22.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
i22.de SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I22.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 I22.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.
i22.de
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: