2.6 sec in total
601 ms
1.7 sec
321 ms
Welcome to liferus.ru homepage info - get ready to check Life Ru S best content for Russia right away, or after learning these important things about liferus.ru
Visit liferus.ruWe analyzed Liferus.ru page load time and found that the first response time was 601 ms and then it took 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. This domain responded with an error, which can significantly jeopardize Liferus.ru rating and web reputation
liferus.ru performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value2.3 s
92/100
25%
Value16.5 s
0/100
10%
Value40,150 ms
0/100
30%
Value0
100/100
15%
Value54.3 s
0/100
10%
601 ms
272 ms
8 ms
12 ms
95 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 34% of them (32 requests) were addressed to the original Liferus.ru, 28% (27 requests) were made to Tpc.googlesyndication.com and 7% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (900 ms) belongs to the original domain Liferus.ru.
Page size can be reduced by 679.1 kB (40%)
1.7 MB
1.0 MB
In fact, the total size of Liferus.ru main page is 1.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 772.4 kB which makes up the majority of the site volume.
Potential reduce by 164.5 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 164.5 kB or 79% of the original size.
Potential reduce by 23.6 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. Life Ru S images are well optimized though.
Potential reduce by 478.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 478.0 kB or 62% of the original size.
Potential reduce by 13.0 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. Liferus.ru needs all CSS files to be minified and compressed as it can save up to 13.0 kB or 82% of the original size.
Number of requests can be reduced by 19 (22%)
87
68
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life Ru S. 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 as a result speed up the page load time.
liferus.ru
601 ms
main.css
272 ms
adsbygoogle.js
8 ms
addthis_widget.js
12 ms
plusone.js
95 ms
noteright.jpg
200 ms
alt_women.jpg
200 ms
clock.gif
325 ms
favicon.ico
325 ms
logo_t.jpg
330 ms
1_med.jpg
323 ms
1_home.jpg
344 ms
1_posh.jpg
327 ms
1_def.jpg
492 ms
1_zdor.jpg
492 ms
1_zdtv.jpg
626 ms
1_rasten.jpg
493 ms
1_kosm.jpg
628 ms
1_cosm.jpg
495 ms
1_cosm_uhod.jpg
626 ms
1_rabotn.jpg
627 ms
1_krest.jpg
626 ms
1_spravpit.jpg
630 ms
1_fito.jpg
777 ms
1_zelapteka.jpg
774 ms
1_lekar.jpg
771 ms
1_cook.jpg
775 ms
1_croup.jpg
771 ms
1_green.jpg
771 ms
1_pate.jpg
895 ms
1_bistroeda.jpg
898 ms
1_bibliya.jpg
892 ms
1_sad.jpg
898 ms
1_slov.jpg
900 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
99 ms
fastbutton
233 ms
ca-pub-6203240625374862.js
138 ms
zrt_lookup.html
135 ms
show_ads_impl.js
80 ms
2-women.jpg
838 ms
ads
238 ms
ga.js
53 ms
postmessageRelay
103 ms
osd.js
12 ms
ads
197 ms
ads
364 ms
300lo.json
54 ms
__utm.gif
40 ms
cb=gapi.loaded_0
39 ms
cb=gapi.loaded_1
39 ms
sh.7c7179124ea24ac6ba46caac.html
25 ms
api.js
58 ms
core:rpc:shindig.random:shindig.sha1.js
131 ms
2536007149-postmessagerelay.js
116 ms
collect
137 ms
custom-messages.ff94d8c06a032bf68fcb.js
22 ms
layers.3643cb2e25fb91c29386.js
23 ms
14605509970189920789
45 ms
abg.js
48 ms
m_js_controller.js
70 ms
googlelogo_color_112x36dp.png
102 ms
css
104 ms
s
33 ms
x_button_blue2.png
31 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
68 ms
16184682623340089549
68 ms
11271086218679330054
59 ms
9404870429486203450
60 ms
16556619192184112762
123 ms
11908279785334333145
123 ms
17158645401501208538
111 ms
8873943779361297499
122 ms
2591750775699298957
123 ms
6030759476991460935
109 ms
6139088810190629725
124 ms
17653610154383482626
167 ms
6963663184442451046
168 ms
6650953915696029171
167 ms
7551300043293564444
153 ms
11165958271308013036
164 ms
8757981700844677841
180 ms
3411183360476180785
206 ms
5504510100433097721
201 ms
3245119151565707629
205 ms
14403407019161656829
207 ms
powered-by-google.png
165 ms
Fl4y0QdOxyyTHEGMXX8kcT8E0i7KZn-EPnyo3HZu7kw.woff
137 ms
isZ-wbCXNKAbnjo6_TwHTj8E0i7KZn-EPnyo3HZu7kw.woff
150 ms
css
64 ms
favicon
71 ms
favicon
78 ms
imgad
65 ms
nessie_icon_tiamat_white.png
66 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
liferus.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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
liferus.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Browser errors were logged to the console
liferus.ru SEO score
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 Liferus.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 Liferus.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.
liferus.ru
Open Graph description is not detected on the main page of Life Ru S. 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: