5.6 sec in total
1.4 sec
4.1 sec
146 ms
Welcome to ii-vi.de homepage info - get ready to check Ii Vi best content right away, or after learning these important things about ii-vi.de
Visit ii-vi.deWe analyzed Ii-vi.de page load time and found that the first response time was 1.4 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ii-vi.de performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value6.4 s
9/100
25%
Value10.7 s
7/100
10%
Value730 ms
40/100
30%
Value0.143
78/100
15%
Value12.2 s
15/100
10%
1431 ms
64 ms
93 ms
89 ms
93 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ii-vi.de, 14% (14 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Ii-vi.com.
Page size can be reduced by 368.4 kB (43%)
848.7 kB
480.3 kB
In fact, the total size of Ii-vi.de main page is 848.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 480.0 kB which makes up the majority of the site volume.
Potential reduce by 228.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 228.4 kB or 85% of the original size.
Potential reduce by 1.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. Ii Vi images are well optimized though.
Potential reduce by 6.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. This website has mostly compressed JavaScripts.
Potential reduce by 132.6 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. Ii-vi.de needs all CSS files to be minified and compressed as it can save up to 132.6 kB or 28% of the original size.
Number of requests can be reduced by 68 (87%)
78
10
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ii Vi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
1431 ms
selectize.min.css
64 ms
price-slider.min.css
93 ms
product-search.min.css
89 ms
cleantalk-public.min.css
93 ms
woocommerce-layout.css
95 ms
woocommerce.css
98 ms
slick.css
96 ms
wpnw-pro-public.min.css
121 ms
woocommerce-product-attachment-public.css
115 ms
style.css
220 ms
dashicons.min.css
152 ms
css
40 ms
genericons.css
138 ms
font-awesome.min.css
138 ms
all.min.css
144 ms
style.css
154 ms
css
43 ms
front-css.css
174 ms
plugin.css
180 ms
public.css
179 ms
perfect-scrollbar.min.css
184 ms
owl.carousel.min.css
184 ms
quadmenu-normalize.css
203 ms
quadmenu-widgets.css
210 ms
style.css
203 ms
quadmenu-locations.css
348 ms
style.min.css
329 ms
style.css
345 ms
css
27 ms
wp-polyfill-inert.min.js
345 ms
regenerator-runtime.min.js
369 ms
wp-polyfill.min.js
372 ms
hooks.min.js
370 ms
w.js
22 ms
jquery.min.js
391 ms
jquery-migrate.min.js
403 ms
apbct-public-bundle.min.js
407 ms
jquery.blockUI.min.js
407 ms
js.cookie.min.js
406 ms
all.css
168 ms
css
25 ms
woocommerce.min.js
406 ms
woocommerce-checkout-attachment-public__premium_only.js
376 ms
front-js.js
349 ms
core.min.js
350 ms
mouse.min.js
351 ms
slider.min.js
351 ms
front-vendor.js
351 ms
underscore.min.js
345 ms
wp-util.min.js
338 ms
accounting.min.js
318 ms
plugin.js
316 ms
public.js
313 ms
idle-timer.min.js
308 ms
custom.js
379 ms
scripts.min.js
463 ms
smoothscroll.js
438 ms
perfect-scrollbar.jquery.min.js
435 ms
owl.carousel.min.js
435 ms
hoverIntent.min.js
434 ms
index.js
433 ms
frontend-bundle.min.js
412 ms
frontend-bundle.min.js
412 ms
common.js
409 ms
main.js
274 ms
maxmegamenu.js
265 ms
public.js
266 ms
g.gif
234 ms
gtm.js
653 ms
coherentbar4c.jpg
154 ms
ii-vi-coherent-logo.png
155 ms
blank2-sx.jpg
154 ms
de-xs.jpg
154 ms
IT-xc.jpg
154 ms
UK-xs.jpg
154 ms
fr-xs.jpg
308 ms
et-divi-dynamic-tb-52153-12595-late.css
94 ms
KFOlCnqEu92Fr1MmSU5vAA.woff
56 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
94 ms
KFOkCnqEu92Fr1MmgWxM.woff
485 ms
KFOkCnqEu92Fr1MmgWxP.ttf
491 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
487 ms
KFOmCnqEu92Fr1Me5g.woff
488 ms
KFOmCnqEu92Fr1Me5Q.ttf
490 ms
KFOlCnqEu92Fr1MmEU9vAA.woff
486 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
495 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
491 ms
KFOlCnqEu92Fr1MmWUlvAA.woff
495 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
495 ms
KFOlCnqEu92Fr1MmYUtvAA.woff
496 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
497 ms
modules.woff
497 ms
fa-brands-400.woff
90 ms
fa-brands-400.woff
498 ms
wARDj0u
3 ms
woocommerce-smallscreen.css
46 ms
ii-vi.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.
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
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.
ii-vi.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
ii-vi.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ii-vi.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ii-vi.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.
ii-vi.de
Open Graph description is not detected on the main page of Ii Vi. 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: