6.5 sec in total
1.1 sec
4.6 sec
888 ms
Welcome to prolejni.ru homepage info - get ready to check Prolejni best content for Russia right away, or after learning these important things about prolejni.ru
Большой выбор средств для лечения пролежней у лежачих больных. Мази, противопролежневые матрасы, повязки и многое другое по доступным ценам и быстрой курьерской доставкой.
Visit prolejni.ruWe analyzed Prolejni.ru page load time and found that the first response time was 1.1 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
prolejni.ru performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value6.2 s
11/100
25%
Value7.5 s
26/100
10%
Value530 ms
55/100
30%
Value0
100/100
15%
Value12.2 s
15/100
10%
1063 ms
219 ms
227 ms
249 ms
249 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 71% of them (71 requests) were addressed to the original Prolejni.ru, 11% (11 requests) were made to Vk.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Prolejni.ru.
Page size can be reduced by 892.4 kB (30%)
3.0 MB
2.1 MB
In fact, the total size of Prolejni.ru main page is 3.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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 144.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 144.3 kB or 82% of the original size.
Potential reduce by 63.1 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. Prolejni images are well optimized though.
Potential reduce by 552.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 552.7 kB or 71% of the original size.
Potential reduce by 132.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. Prolejni.ru needs all CSS files to be minified and compressed as it can save up to 132.2 kB or 81% of the original size.
Number of requests can be reduced by 49 (54%)
91
42
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prolejni. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.prolejni.ru
1063 ms
core.css
219 ms
core_popup.css
227 ms
style.css
249 ms
style.css
249 ms
style.css
246 ms
style.css
246 ms
style.css
328 ms
style.css
339 ms
style.css
367 ms
styles.css
364 ms
core.js
471 ms
core_ajax.js
367 ms
json2.min.js
422 ms
core_ls.js
435 ms
session.js
458 ms
core_fx.js
461 ms
core_popup.js
467 ms
core_currency.js
522 ms
script.js
529 ms
script.js
556 ms
script.js
565 ms
script.js
565 ms
script.js
572 ms
style.css
652 ms
css
50 ms
jquery-1.11.2.min.js
759 ms
jquery-ui.css
186 ms
jquery-ui.min.js
360 ms
jquery.maskedinput.js
674 ms
jquery.timepicker.css
681 ms
jquery.timepicker.min.js
676 ms
my.js
682 ms
jquery.mousewheel.pack.js
738 ms
jquery.fancybox.pack.js
893 ms
jquery.fancybox.css
900 ms
openapi.js
417 ms
share.js
70 ms
require.js
816 ms
app.min.js
849 ms
ba.js
341 ms
9996bb804ac4ad3a9d2c8f3b4ac19d3f.jpg
255 ms
5b33484e27b6fff14f6f84c06e21ae91.jpg
252 ms
565b727fa7a4bd8c6e8e08653a519a0a.png
355 ms
1df618353314bfa48de46d1059a65431.jpg
166 ms
5f23cbc211b309371bb5bd295dcd00ea.jpg
1512 ms
f9085273837645f49bd54f2d9287be03.jpg
703 ms
e0b0fb1cb3c98fae07ba9fbbee78f3f9.jpeg
252 ms
6667c6126d5bc5d4eba7bb0eac2cc21e.jpeg
699 ms
6e1025d02a4d8be717e94b166ab7596a.jpg
608 ms
356a53a7a2312d3990af76e61ddad85f.jpg
1527 ms
cece7eb801791277d4d438df315b4bee.jpg
699 ms
171bdd2ddca904edeebdcc7118e385d3.png
1729 ms
01ac3917316ae3273a2005af311199eb.jpg
777 ms
bfdc828c912f8ff63a283af019e12f2e.jpg
1205 ms
1ab87bf5268bade48eb1df37f221c33c.gif
779 ms
bdb1618cf93d5dfeb8ace2a0e55a2b5c.jpg
1314 ms
bb25d746e35b7824fff87af452c5512b.jpg
1671 ms
87259080f1beef41042a27ba3bf80319.jpg
1332 ms
74f17941b836c5577e9c0b80c684347a.png
1468 ms
1822f56dd575bf7ca0bf4ae42a1ed384.png
1477 ms
ed648835b6adc456bd76b3d03836ab96.png
1594 ms
9fdcb0b288cf6c8fb7b69b328e35ede7.png
1603 ms
b2d80fe34e17a68f8fd0cc210de9436a.png
1633 ms
c5d8050d65a96c326ac7175125799614.png
1646 ms
3a266e36538c95072744c64143f85806.png
1729 ms
7e48763e2def1da5e37a071108eacea1.png
1746 ms
328eaaaf961596adf8ff4db66a408711.png
1777 ms
3ae5e2dd9ce65e90c65800af4bb975cb.png
1788 ms
header_decor.png
1775 ms
logo.png
1810 ms
Fl4y0QdOxyyTHEGMXX8kcaCWcynf_cDxXwCLxiixG1c.ttf
169 ms
B85vmdvDILX92ray16e-1g.ttf
210 ms
isZ-wbCXNKAbnjo6_TwHTqCWcynf_cDxXwCLxiixG1c.ttf
210 ms
icons-s4491012f52.png
1803 ms
array.png
1855 ms
main_nav.jpg
1781 ms
style.css
1790 ms
7m8l7TlFO-S3VkhHuR0at5p-63r6doWhTEbsfBIRJ7A.ttf
218 ms
sWTqoqnV-OOzHbi5P-jvYPesZW2xOQ-xsNqO47m55DA.ttf
216 ms
t6Nd4cfPRhZP44Q5QAjcC5p-63r6doWhTEbsfBIRJ7A.ttf
222 ms
upload.gif
219 ms
widget_like.php
348 ms
bottom_decor.png
1523 ms
watch.js
180 ms
hit
360 ms
ui-bg_flat_75_ffffff_40x100.png
133 ms
bx_stat
432 ms
b-share-icon.png
102 ms
jquery.min.js
91 ms
jquery-ui.min.js
1558 ms
loader_nav19239_3.js
632 ms
lite.css
251 ms
lite.js
544 ms
lang3_0.js
864 ms
widgets.css
786 ms
xdm.js
934 ms
al_like.js
1027 ms
hit
952 ms
like_widget.png
151 ms
prolejni.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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
prolejni.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
prolejni.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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prolejni.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Prolejni.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.
prolejni.ru
Open Graph description is not detected on the main page of Prolejni. 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: