6 sec in total
322 ms
5.4 sec
276 ms
Visit h2o.it now to see the best up-to-date H 2 O content for Italy and also check out these interesting facts you probably never knew about h2o.it
Negozio creato usando PrestaShop
Visit h2o.itWe analyzed H2o.it page load time and found that the first response time was 322 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
h2o.it performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value7.1 s
5/100
25%
Value10.3 s
8/100
10%
Value2,480 ms
4/100
30%
Value0.106
88/100
15%
Value16.8 s
5/100
10%
322 ms
2914 ms
146 ms
246 ms
269 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 96% of them (74 requests) were addressed to the original H2o.it, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain H2o.it.
Page size can be reduced by 652.8 kB (56%)
1.2 MB
515.4 kB
In fact, the total size of H2o.it main page is 1.2 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. 45% of websites need less resources to load. Javascripts take 478.1 kB which makes up the majority of the site volume.
Potential reduce by 36.7 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 36.7 kB or 80% of the original size.
Potential reduce by 22.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. H 2 O images are well optimized though.
Potential reduce by 339.7 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 339.7 kB or 71% of the original size.
Potential reduce by 254.0 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. H2o.it needs all CSS files to be minified and compressed as it can save up to 254.0 kB or 84% of the original size.
Number of requests can be reduced by 42 (58%)
73
31
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of H 2 O. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
h2o.it
322 ms
www.h2o.it
2914 ms
modal.css
146 ms
style.css
246 ms
typo.css
269 ms
calendar.css
223 ms
front.css
220 ms
system.css
223 ms
general.css
255 ms
facebox.css
336 ms
vmsite-ltr.css
344 ms
addons.css
337 ms
layout.css
356 ms
template.css
366 ms
usertools.css
376 ms
css3.css
447 ms
mega.css
450 ms
k2.css
457 ms
layout.css
478 ms
template.css
479 ms
setting.css
484 ms
extensions.css
557 ms
virtuemart.css
575 ms
mega.css
592 ms
bootstrap.min.css
604 ms
mootools-core.js
729 ms
core.js
668 ms
mootools-more.js
1028 ms
modal.js
705 ms
jquery.min.js
26 ms
k2.noconflict.js
756 ms
k2.js
795 ms
script.js
840 ms
caption.js
835 ms
script.js
855 ms
core.js
867 ms
login-script.js
895 ms
mega.js
813 ms
vmsite.js
766 ms
system.css
763 ms
facebox.js
767 ms
vmprices.js
794 ms
engine.js
939 ms
stylesheet.css
626 ms
responsive.css
622 ms
bg_tot.png
445 ms
dispenser-boccioni-acqua.jpg
273 ms
erogatori-acqua.jpg
279 ms
depuratori-osmosi-inversa.jpg
275 ms
altri-prodotti.jpg
274 ms
num_verde.png
273 ms
telefono-h2o.gif
441 ms
chat-h2o.png
433 ms
ISO9001.png
459 ms
logo.png
604 ms
addtocart-nsp.png
413 ms
back_menu.png
551 ms
active-arrow.png
562 ms
home.png
545 ms
h2o.png
546 ms
transparent.png
568 ms
light-transparent.png
679 ms
prodotti.png
672 ms
e-commerce.png
679 ms
servizi.png
700 ms
faq.png
708 ms
clienti.png
722 ms
contatti.png
808 ms
PTS55F-webfont.woff
822 ms
droidsans-bold-webfont.woff
777 ms
title-span.png
809 ms
interface.png
797 ms
ridge.png
789 ms
informazioni-boccioni-acqua.gif
873 ms
analytics.js
13 ms
back-top.png
817 ms
collect
25 ms
h2o.it accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
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.
h2o.it 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
Page has valid source maps
h2o.it SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise H2o.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that H2o.it 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.
h2o.it
Open Graph description is not detected on the main page of H 2 O. 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: