2.7 sec in total
546 ms
2 sec
181 ms
Welcome to acquaeva.com homepage info - get ready to check Acqua Eva best content right away, or after learning these important things about acquaeva.com
Acqua Eva nasce dalla sorgente più alta d'Europa. Leggerissima e con un contenuto di sodio tra i più bassi al mondo!
Visit acquaeva.comWe analyzed Acquaeva.com page load time and found that the first response time was 546 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
acquaeva.com performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value41.1 s
0/100
25%
Value14.4 s
1/100
10%
Value260 ms
84/100
30%
Value0.294
41/100
15%
Value18.2 s
3/100
10%
546 ms
128 ms
67 ms
239 ms
245 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 45% of them (20 requests) were addressed to the original Acquaeva.com, 18% (8 requests) were made to Apis.google.com and 7% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (646 ms) belongs to the original domain Acquaeva.com.
Page size can be reduced by 368.1 kB (46%)
808.6 kB
440.5 kB
In fact, the total size of Acquaeva.com main page is 808.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. 45% of websites need less resources to load. Javascripts take 441.3 kB which makes up the majority of the site volume.
Potential reduce by 47.3 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 47.3 kB or 70% of the original size.
Potential reduce by 9.4 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. Acqua Eva images are well optimized though.
Potential reduce by 283.9 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 283.9 kB or 64% of the original size.
Potential reduce by 27.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. Acquaeva.com needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 81% of the original size.
Number of requests can be reduced by 17 (40%)
42
25
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Acqua Eva. 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 from 4 to 1 for CSS and as a result speed up the page load time.
acquaeva.com
546 ms
style.css
128 ms
jquery.min.js
67 ms
jquery.carouFredSel-4.4.3-packed.js
239 ms
swfobject.js
245 ms
addthis_widget.js
31 ms
reset.css
127 ms
menu.css
230 ms
css
25 ms
BfQP1MR3mJNaumtWa4Tizg.ttf
9 ms
logo.jpg
248 ms
slide.jpg
646 ms
mamma.jpg
247 ms
promo.jpg
247 ms
comparativa.jpg
352 ms
promo.png
240 ms
comparativa_attiva.png
352 ms
italiano.jpg
370 ms
inglese.jpg
370 ms
tedesco.jpg
369 ms
arrow.jpg
445 ms
all.js
280 ms
pageScrollerB.png
387 ms
favp.jpg
413 ms
estroverso.jpg
412 ms
300lo.json
38 ms
plusone.js
51 ms
sh.8e5f85691f9aaa082472a194.html
40 ms
cb=gapi.loaded_0
24 ms
cb=gapi.loaded_1
38 ms
fastbutton
82 ms
postmessageRelay
55 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
13 ms
3193398744-postmessagerelay.js
55 ms
rpc:shindig_random.js
55 ms
67 ms
cb=gapi.loaded_0
10 ms
xd_arbiter.php
213 ms
xd_arbiter.php
418 ms
ping
46 ms
like.php
82 ms
TY3MhkXpWJ-.js
139 ms
LVx-xkvaJ0b.png
152 ms
acquaeva.com 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
Links do not have a discernible name
acquaeva.com 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
acquaeva.com 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
IT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Acquaeva.com can be misinterpreted by Google and other search engines. Our service has detected that Italian 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 Acquaeva.com 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.
acquaeva.com
Open Graph description is not detected on the main page of Acqua Eva. 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: