9.5 sec in total
1.1 sec
7.4 sec
1 sec
Click here to check amazing E Aqualine content. Otherwise, check out these important facts you probably never knew about e-aqualine.ru
Интернет магазин сантехники в Самаре: большой ассортимент сантехники и аксессуаров для ванной. Продажа и доставка по всей России.
Visit e-aqualine.ruWe analyzed E-aqualine.ru page load time and found that the first response time was 1.1 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
e-aqualine.ru performance score
1066 ms
650 ms
983 ms
483 ms
647 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 82% of them (69 requests) were addressed to the original E-aqualine.ru, 11% (9 requests) were made to Googleads.g.doubleclick.net and 5% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain E-aqualine.ru.
Page size can be reduced by 131.0 kB (38%)
346.4 kB
215.4 kB
In fact, the total size of E-aqualine.ru main page is 346.4 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. 30% of websites need less resources to load. Images take 139.4 kB which makes up the majority of the site volume.
Potential reduce by 72.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. 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 72.2 kB or 87% of the original size.
Potential reduce by 11.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. E Aqualine images are well optimized though.
Potential reduce by 34.6 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 34.6 kB or 32% of the original size.
Potential reduce by 13.3 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. E-aqualine.ru needs all CSS files to be minified and compressed as it can save up to 13.3 kB or 83% of the original size.
Number of requests can be reduced by 24 (33%)
72
48
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Aqualine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
e-aqualine.ru
1066 ms
style.css
650 ms
java2.js
983 ms
cartwindow.js
483 ms
Js.js
647 ms
swfobject.js
647 ms
adsbygoogle.js
25 ms
watch.js
3 ms
n.gif
359 ms
i_commercemanager_med.gif
353 ms
i_compare_med.gif
352 ms
header_bg_1_up.jpg
181 ms
header_bg_1_up_cart.jpg
360 ms
header_bg_1_up_sum.jpg
358 ms
header_bg_1_up_cur.jpg
599 ms
header_bg_1_up_order_anim.gif
667 ms
header_bg_1_bg.jpg
898 ms
header_bg_1.jpg
1048 ms
phpshop_logo.png
838 ms
phpshop_logo_icon.png
972 ms
phpshop_user2.png
1015 ms
but_enter.jpg
968 ms
header_bg_nav.jpg
1017 ms
header_bg_nav_line.jpg
1095 ms
left_search_bg.jpg
1124 ms
phpshop_search.png
1128 ms
but_search.jpg
1280 ms
catalog_bg.jpg
1282 ms
podcatalog_bg.jpg
1222 ms
left_plashka_bg.jpg
1343 ms
img706_13695_big.jpg
2918 ms
left_opros_bg.jpg
2015 ms
but_opros.jpg
2018 ms
spacer.gif
2017 ms
b7834aa_170_auto.jpg
2185 ms
dush_garn.jpg
2183 ms
db_pic.JPG
2278 ms
Aksessuary.JPG
2284 ms
FokstrPL1.jpg
2494 ms
Filtr.jpg
2577 ms
vodonagr3.jpg
2955 ms
Teplyi_pol.jpg
2763 ms
Radiator.jpg
2583 ms
soputka.jpg
2783 ms
ca-pub-6920992154252242.js
287 ms
zrt_lookup.html
310 ms
show_ads_impl.js
133 ms
but_more.jpg
2728 ms
ads
285 ms
osd.js
196 ms
img27_10559s.jpg
2578 ms
basket_put.gif
2674 ms
information.gif
2673 ms
img82_58573s.jpg
3448 ms
ads
477 ms
img17_10123s.jpg
3486 ms
ads
249 ms
ads
242 ms
ads
216 ms
img397_71222s.jpg
3177 ms
ads
130 ms
hit
1119 ms
ads
120 ms
ads
118 ms
img789_99850s.jpg
2651 ms
img722_92279s.jpg
3037 ms
img689_85210s.jpg
2978 ms
img630_12554s.jpg
2636 ms
img575_18604s.jpg
2886 ms
icon_email.gif
2919 ms
img438_18277s.jpg
3058 ms
feed.gif
2960 ms
pda.gif
2925 ms
sitemap.gif
2903 ms
mi.png
3215 ms
center_plashka_bg.jpg
3149 ms
product_bg.jpg
2926 ms
line_bg.jpg
2935 ms
product_img_bg_body.jpg
2875 ms
product_img_bg_header.jpg
2314 ms
product_img_bg_footer.jpg
2335 ms
product_price_bg.jpg
2494 ms
footer_bg.jpg
2182 ms
footer_cart.jpg
3185 ms
e-aqualine.ru SEO score
![]()
RU
![]()
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-aqualine.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 E-aqualine.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
e-aqualine.ru
Open Graph description is not detected on the main page of E Aqualine. 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: