30.4 sec in total
443 ms
24.5 sec
5.5 sec
Visit aqualife.ru now to see the best up-to-date Aqualife content for Russia and also check out these interesting facts you probably never knew about aqualife.ru
Заказ воды с доставкой по Москве и Московской области на дом и офис. От производителя, недорогая цена - Aqualife
Visit aqualife.ruWe analyzed Aqualife.ru page load time and found that the first response time was 443 ms and then it took 29.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
aqualife.ru performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value4.1 s
47/100
25%
Value22.2 s
0/100
10%
Value16,640 ms
0/100
30%
Value0.01
100/100
15%
Value26.3 s
0/100
10%
443 ms
5715 ms
322 ms
942 ms
657 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 75% of them (90 requests) were addressed to the original Aqualife.ru, 10% (12 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (12.8 sec) belongs to the original domain Aqualife.ru.
Page size can be reduced by 677.1 kB (11%)
6.0 MB
5.3 MB
In fact, the total size of Aqualife.ru main page is 6.0 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. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 49.8 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 19.0 kB, which is 31% 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 49.8 kB or 81% of the original size.
Potential reduce by 73.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. Aqualife images are well optimized though.
Potential reduce by 426.0 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 426.0 kB or 72% of the original size.
Potential reduce by 128.2 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. Aqualife.ru needs all CSS files to be minified and compressed as it can save up to 128.2 kB or 83% of the original size.
Number of requests can be reduced by 41 (40%)
102
61
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aqualife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
aqualife.ru
443 ms
www.aqualife.ru
5715 ms
core.css
322 ms
core_popup.css
942 ms
index.css
657 ms
vd.css
336 ms
fotorama.css
646 ms
style.css
430 ms
popup.css
802 ms
style.css
482 ms
owl.carousel.css
584 ms
owl.theme.css
631 ms
owl.transitions.css
740 ms
reset.css
792 ms
icons.css
821 ms
jquery.fancybox.css
824 ms
common.css
1221 ms
modal.css
1073 ms
animate.css
1822 ms
forms.css
996 ms
styles.css
1153 ms
template_styles.css
1085 ms
core.js
2436 ms
jquery-1.8.3.min.js
2543 ms
core_popup.js
1666 ms
core_ajax.js
1715 ms
core_window.js
2232 ms
jquery.fancybox.js
2180 ms
cw.js
2054 ms
main.js
1991 ms
fotorama.js
2460 ms
script.js
2229 ms
owl.carousel.min.js
2497 ms
css
117 ms
css
132 ms
css
146 ms
ba.js
333 ms
qDjo57eEvH
328 ms
logo.png
729 ms
logo_2.png
730 ms
19litrov.png
778 ms
5litrov.png
780 ms
limonadi.png
784 ms
f-nup.png
1796 ms
img1.png
1828 ms
img2.png
2370 ms
img3.png
2682 ms
img4.png
2252 ms
%D0%B0%D0%BA1-1.jpg
3837 ms
%D0%B0%D0%BA3-3.jpg
4108 ms
aqualife_utp-1.png
5819 ms
logo_utp-1.png
2375 ms
logo_utp-2.png
2812 ms
logo_utp-3.png
2812 ms
utp-1.png
4588 ms
m-utp-2.png
5467 ms
4b5027718b8e28f75c8c529279a259db.jpg
4682 ms
35f647144d268cd05f6a68f85ec97f8b.jpg
5662 ms
6639e3579ef704ed8c8efdf9bc4b35af.jpg
7104 ms
0e280c668165f2ac802b57015bb46f71.jpg
6747 ms
6311c2b01574b0410dbf44634b7929f3.jpg
7032 ms
3339511ecf3703c128f7a5795d90c3b1.jpg
11670 ms
7a054f73db25cad701ad23d230969bdf.jpg
5830 ms
e8e57210646df532003c8424de4293e6.jpg
5980 ms
43d93fda5d88462fc68e123e109fed89.jpg
6004 ms
e9f84c300b956e1ae728006229571b18.jpg
6158 ms
05cedb101cfe7e758af854d53f403335.jpg
6181 ms
7657033501f1cbfd968a55f9f649378e.jpg
6322 ms
4e5c13987c1f391bb5fecda49d8088be.jpg
6332 ms
gtm.js
244 ms
icon-bas.png
6454 ms
shape.png
6242 ms
science.png
6407 ms
technology.png
6426 ms
transport.png
6558 ms
K88pR3goAWT7BTt32Z01m6CWcynf_cDxXwCLxiixG1c.ttf
1474 ms
RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf
1502 ms
DXI1ORHCpsQm3Vp6mXoaTWeP1y_Bkidl4ESyB_O2G_c.ttf
1724 ms
MTP_ySUJH_bn48VBG8sNSmeP1y_Bkidl4ESyB_O2G_c.ttf
1724 ms
k3k702ZOKiLJc3WVjuplzGeP1y_Bkidl4ESyB_O2G_c.ttf
1721 ms
k3k702ZOKiLJc3WVjuplzPOEPOIfcPv-fZ-WyMUtx48.ttf
1712 ms
EInbV5DfGHOiMmvb1Xr-hmeP1y_Bkidl4ESyB_O2G_c.ttf
1716 ms
243e0e790d4d8fca79c043214e731d83.jpg
7723 ms
widget_ru_RU.js
1308 ms
icomoon.ttf
6185 ms
PRmiXeptR36kaC0GEAetxs48OaV_SNIXktLWq3KXug4.ttf
1288 ms
PRmiXeptR36kaC0GEAetxgbEkm-f2UOALJ0ub4PpKrw.ttf
1301 ms
PRmiXeptR36kaC0GEAetxpUejhVR4X9s8dmwuSBKoOY.ttf
1296 ms
xjAJXh38I15wypJXxuGMBlwIJl2YiaXHM0xUx_ugXFg.ttf
1292 ms
PRmiXeptR36kaC0GEAetxmpz0z5zL8i4lJVsvdmh4hw.ttf
1292 ms
offer-flag.png
6281 ms
m-utp-bg.png
9723 ms
analytics.js
1219 ms
watch.js
12 ms
code.js
1418 ms
action-calculator.png
6259 ms
phone.bbf42.4254.async.js
1340 ms
bx_stat
479 ms
ajax_counter.php
6413 ms
action-complaint.png
5329 ms
action-callback.png
5013 ms
linkid.js
76 ms
counter
194 ms
903118269fa6011a7026c13cf27a72ea.jpg
7747 ms
collect
68 ms
time-icon.png
5018 ms
collect
218 ms
ga-audiences
332 ms
cb0025780a8fdbdd685b440e84ff718f.jpg
7981 ms
52cee7f087d8bb2e907cd0cf0ca6d2b3.jpg
12791 ms
f19d3f31e019ec47065e55a236cc97c7.png
7020 ms
vk-foot.png
6160 ms
fb-foot.png
6068 ms
inst-foot.png
5709 ms
tw-foot.png
5670 ms
fotorama.png
5009 ms
044ce3ccfbaababd6ad1686fda6e7f13.jpg
7718 ms
btn-prev.png
4844 ms
btn-next.png
4872 ms
tracker
210 ms
aqualife.ru 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
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
aqualife.ru 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
aqualife.ru 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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aqualife.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Aqualife.ru 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.
aqualife.ru
Open Graph description is not detected on the main page of Aqualife. 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: