11.5 sec in total
510 ms
10.8 sec
210 ms
Welcome to prelax.ru homepage info - get ready to check Prelax best content for Russia right away, or after learning these important things about prelax.ru
Слабительное средство Прелакс — лечение запора Рё сопутствующая терапия РїСЂРё лечении геморроя. Продажа слабиС...
Visit prelax.ruWe analyzed Prelax.ru page load time and found that the first response time was 510 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
prelax.ru performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value3.4 s
65/100
25%
Value4.0 s
81/100
10%
Value320 ms
76/100
30%
Value0.405
24/100
15%
Value3.6 s
91/100
10%
510 ms
872 ms
376 ms
244 ms
642 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 75% of them (53 requests) were addressed to the original Prelax.ru, 6% (4 requests) were made to Google-analytics.com and 6% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (8.6 sec) belongs to the original domain Prelax.ru.
Page size can be reduced by 204.4 kB (41%)
496.9 kB
292.5 kB
In fact, the total size of Prelax.ru main page is 496.9 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. 25% of websites need less resources to load. Javascripts take 208.2 kB which makes up the majority of the site volume.
Potential reduce by 78.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 31.7 kB, which is 34% 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 78.2 kB or 85% of the original size.
Potential reduce by 16.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. Prelax images are well optimized though.
Potential reduce by 109.8 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 109.8 kB or 53% of the original size.
Number of requests can be reduced by 30 (46%)
65
35
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prelax. 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.
prelax.ru
510 ms
www.prelax.ru
872 ms
jquery-1.7.1.min.js
376 ms
application.js
244 ms
counter_cv.js
642 ms
top100.cnt
268 ms
banner-88x31-rambler-blue3.gif
262 ms
spacer.gif
137 ms
top_toilet.jpg
250 ms
top_toil_32.jpg
135 ms
top_slogan.gif
259 ms
ico-tw.png
260 ms
ico-vk.png
260 ms
ico-fb.png
260 ms
top_prelax.png
262 ms
top_pechat.gif
366 ms
prelax.jpg
497 ms
left-button.png
377 ms
cen_top.jpg
384 ms
prelaks__49.jpg
381 ms
prelaks__41.jpg
385 ms
prelaks__46.jpg
487 ms
prelaks__51.jpg
499 ms
prelaks__50.jpg
506 ms
prelaks__52.jpg
507 ms
prelaks__44.jpg
507 ms
prelaks__43.jpg
608 ms
prelaks__42.jpg
617 ms
prelaks__53.jpg
621 ms
ikonka_203.jpg
631 ms
btm_menu_shadow_r1.jpg
630 ms
btm_menu_shadow_l2.jpg
632 ms
btm_menu_1.jpg
8627 ms
btm_menu_2.jpg
8627 ms
btm_menu_3.jpg
8631 ms
btm_menu_shadow_r2.jpg
8629 ms
felicata_logo.gif
8628 ms
spyk-logo.png
8627 ms
bot_block.gif
8629 ms
bot_right.jpg
8630 ms
gtm.js
45 ms
bessh1.jpg
8626 ms
top_bg1.jpg
8628 ms
top_bg2.jpg
8626 ms
ga.js
5 ms
analytics.js
29 ms
watch.js
176 ms
__utm.gif
11 ms
collect
54 ms
collect
2 ms
top_bg3.jpg
8506 ms
top_bg4.jpg
8505 ms
cnt
8389 ms
hit
261 ms
watch.js
463 ms
top_bg5.jpg
8385 ms
35_100_1_189.gif
8384 ms
left_arr.gif
8384 ms
top_r.jpg
8384 ms
left_bg.gif
8384 ms
left_toilet.jpg
8382 ms
cen_bg.jpg
8278 ms
cen_bg1.jpg
8267 ms
cen_line.gif
8262 ms
right_bg.gif
8261 ms
bot_left1.jpg
8261 ms
hit
133 ms
advert.gif
91 ms
u8131.14.spylog.com
250 ms
1
91 ms
cnt
238 ms
prelax.ru 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
prelax.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
prelax.ru 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
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prelax.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 Prelax.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.
prelax.ru
Open Graph description is not detected on the main page of Prelax. 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: