2 sec in total
304 ms
1.5 sec
232 ms
Visit i-zauber.net now to see the best up-to-date I Zau BeR content and also check out these interesting facts you probably never knew about i-zauber.net
Soluciones de Software a Medida y Software Libre
Visit i-zauber.netWe analyzed I-zauber.net page load time and found that the first response time was 304 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
i-zauber.net performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value7.9 s
3/100
25%
Value9.1 s
14/100
10%
Value20 ms
100/100
30%
Value0.935
3/100
15%
Value7.7 s
45/100
10%
304 ms
96 ms
289 ms
192 ms
192 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 80% of them (55 requests) were addressed to the original I-zauber.net, 16% (11 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (668 ms) belongs to the original domain I-zauber.net.
Page size can be reduced by 70.3 kB (15%)
475.6 kB
405.3 kB
In fact, the total size of I-zauber.net main page is 475.6 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. 55% of websites need less resources to load. Images take 270.9 kB which makes up the majority of the site volume.
Potential reduce by 17.2 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 3.1 kB, which is 14% 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 17.2 kB or 77% of the original size.
Potential reduce by 27.9 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. I Zau BeR images are well optimized though.
Potential reduce by 18.5 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 18.5 kB or 14% of the original size.
Potential reduce by 6.7 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. I-zauber.net needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 13% of the original size.
Number of requests can be reduced by 39 (72%)
54
15
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Zau BeR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
i-zauber.net
304 ms
main.css
96 ms
jquery.min.js
289 ms
bootstrap.min.js
192 ms
jquery.prettyPhoto.js
192 ms
easing.js
193 ms
jquery.isotope.min.js
193 ms
jquery.ui.totop.js
193 ms
selectnav.js
286 ms
ender.js
286 ms
jquery.lazyload.js
287 ms
jquery.themepunch.plugins.min.js
289 ms
jquery.themepunch.revolution.js
387 ms
jquery.flexslider-min.js
381 ms
holder.min.js
381 ms
jquery.stellar.min.js
382 ms
countUp.min.js
383 ms
moment.min.js
385 ms
rev-setting-1.js
475 ms
draggable-0.1.js
475 ms
jquery.dependClass-0.1.js
476 ms
tmpl.js
477 ms
jquery.slider.js
480 ms
jslider.css
483 ms
jslider.mama.css
569 ms
jslider.blue.css
570 ms
bootstrap-switch.min.css
570 ms
bootstrap-switch.min.js
571 ms
custom.js
575 ms
bootstrap.css
490 ms
settings.css
574 ms
responsiveslides.css
573 ms
prettyPhoto.css
575 ms
flexslider.css
576 ms
style.css
581 ms
rev-settings.css
589 ms
font-awesome.min.css
668 ms
font-awesome-corp.css
668 ms
font-awesome-ext.css
575 ms
font-awesome-social.css
575 ms
css
33 ms
css
52 ms
bg-subheader.jpg
110 ms
logo.png
111 ms
fondo_zauber.jpg
287 ms
fer_empire_bw.jpg
190 ms
mimetica_bw.png
111 ms
miscelanea_bw.png
111 ms
monxeta_bw.png
190 ms
logos_clientes.png
384 ms
captcha.png
191 ms
logo-footer.png
193 ms
piwik.js
123 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
18 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
23 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
36 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
39 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
41 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
56 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
56 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
40 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
40 ms
fontawesome-webfont.woff
328 ms
fontawesome-social-webfont.woff
244 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
56 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf
56 ms
loader.gif
108 ms
timer.png
109 ms
ui.totop.png
197 ms
i-zauber.net 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
i-zauber.net 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
Browser errors were logged to the console
i-zauber.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
![]()
ES
![]()
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-zauber.net can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that I-zauber.net 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.
i-zauber.net
Open Graph description is not detected on the main page of I Zau BeR. 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: