4.1 sec in total
259 ms
3.7 sec
166 ms
Welcome to inoxair.de homepage info - get ready to check Inox Air best content right away, or after learning these important things about inoxair.de
Unsere Luftnachbehandlung sorgt für saubere Luft in Ihrer Küche. Unsere Anlagen sind mit der Plasma-Technologie ausgestattet und entfernen Fett, Rauc…
Visit inoxair.deWe analyzed Inoxair.de page load time and found that the first response time was 259 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
inoxair.de performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value5.0 s
26/100
25%
Value5.2 s
60/100
10%
Value470 ms
61/100
30%
Value0.145
77/100
15%
Value5.6 s
69/100
10%
259 ms
87 ms
115 ms
73 ms
144 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Inoxair.de, 43% (36 requests) were made to Static.parastorage.com and 37% (31 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.3 MB (57%)
3.9 MB
1.7 MB
In fact, the total size of Inoxair.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. 70% of websites need less resources to load. Javascripts take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 268 B
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 268 B or 45% of the original size.
Potential reduce by 93.0 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. Inox Air images are well optimized though.
Potential reduce by 2.1 MB
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 2.1 MB or 77% of the original size.
Potential reduce by 44.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. Inoxair.de needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.
Number of requests can be reduced by 43 (57%)
76
33
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inox Air. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
inoxair.de
259 ms
inoxair.com
87 ms
www.inoxair.com
115 ms
bt
73 ms
require.min.js
144 ms
main-r.min.js
163 ms
viewer.css
155 ms
UpgradeBrowser.js
161 ms
ugc-viewer
36 ms
dynamicmodel
9 ms
56f3b9_3ddf4e095f1bc4dae16ee190993a3355_2081.json.z
108 ms
56f3b9_7b9bfd3aecaf4b444ac8252f31c752e1_1977.json.z
312 ms
bt
60 ms
skins.min.js
283 ms
components.min.js
136 ms
utils.min.js
136 ms
core.min.js
105 ms
react-with-addons.min.js
136 ms
lodash.min.js
135 ms
TweenMax.min.js
276 ms
layout.min.js
278 ms
tpa.min.js
276 ms
fonts.min.js
280 ms
animations.min.js
279 ms
swfobject.min.js
280 ms
mousetrap.min.js
281 ms
tweenEngine.min.js
282 ms
DrawSVGPlugin.min.js
283 ms
react-dom.min.js
281 ms
ScrollToPlugin.min.js
283 ms
widgets.min.js
284 ms
experiment.js
284 ms
render.min.js
284 ms
wixappsCore.min.js
286 ms
wixappsClassics.min.js
291 ms
wixappsBuilder.min.js
286 ms
zepto.min.js
286 ms
color.min.js
288 ms
react-dom-server.min.js
128 ms
latin.css
312 ms
bt
110 ms
bt
369 ms
dc.js
377 ms
56f3b9_688a549b973e42a5a5bfc428c0184bc1.jpg
214 ms
mobileIEFix.css
118 ms
8d2c2a4846503b9067e2fd2f590445c2.wix_mp
91 ms
fe7017590fbd384c7502a64601c7b444.png
90 ms
0e3ab593d41f9b50a377e56363e64221.png
275 ms
56f3b9_9c7111f25a904a6bb3d53728b13e8db8.jpg
495 ms
56f3b9_5b17a72dbd77422d8c257d9c4c0a0ccc.png
705 ms
56f3b9_e9b334375e994af8897992504d7e3d93.jpg
510 ms
56f3b9_2a7cfc2b03834c1baf3fbd97f54b4680.png
515 ms
56f3b9_9d7c7864a69d412ea949b4dd27d9a507.png
359 ms
56f3b9_835be6d5832b44efa5a0d72180e621c2.png
509 ms
56f3b9_b17dcf3b7aec403eb0ddc9cb6569785c.png
705 ms
56f3b9_b5f52c7f7078404bab9f13ebd25792b2.png
523 ms
56f3b9_1f90bb342f9d49839c10b3c2282d54fd.png
1032 ms
56f3b9_4d0b5b84e588466185379f94d954d455.png
750 ms
56f3b9_6e0d78a21c61464f86d74d1c94f05b58.png
1928 ms
56f3b9_d6fea27e458a4e73aab0d294114645b8.png
790 ms
56f3b9_2a21bf1d4d67415abb1d7505018d6f92.png
703 ms
56f3b9_e1aa0a310a8849928bf3f9ee975dcdf8.png
812 ms
56f3b9_19746874d9c546a991d89c9ae35581d4.png
810 ms
56f3b9_d445373626be49e8b9cf1c27a1d8cb13.png
971 ms
56f3b9_fd2abb10ee4e4729ba15d924b89c897b.png
1095 ms
56f3b9_e69ab4b2b7f744bf9734ea27cf0568d7.png
832 ms
56f3b9_602e12e4566c4e1ab32673f2f1b83e7d.png
1016 ms
56f3b9_fcc0a5daaa9f4bb08a493492cd7e8478.png
997 ms
56f3b9_65cf9b1b925f45d68b7ef976149f62cc.png
1126 ms
56f3b9_c786e28e89884a0e802b4340760e413c.png
1013 ms
56f3b9_4b4fbd3b14dc42c8ab2af5fc70e76c5e.png
1286 ms
56f3b9_4520a3ae56174288a8ec938aa5dc3971.png
1143 ms
56f3b9_eb74c6a1855540fabb2357a88a59cee1.png
1396 ms
bt
268 ms
bt
267 ms
liftedshadow_medium.png
296 ms
arrows_white_new3.png
294 ms
__utm.gif
191 ms
bt
78 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
103 ms
20323430-24f4-4767-9d4d-060d1e89758a.woff
77 ms
ga-audiences
57 ms
ugc-viewer
170 ms
inoxair.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
button, link, and menuitem elements do not have accessible names.
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.
inoxair.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
inoxair.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inoxair.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Inoxair.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.
inoxair.de
Open Graph description is not detected on the main page of Inox Air. 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: