8.2 sec in total
717 ms
6.8 sec
649 ms
Visit lifestatus.ru now to see the best up-to-date Lifestatus content for Russia and also check out these interesting facts you probably never knew about lifestatus.ru
Самые прикольные и смешные статусы пользователей аськи. Каждый день нам присылают новые статусы, мы отбираем среди них лучшие.
Visit lifestatus.ruWe analyzed Lifestatus.ru page load time and found that the first response time was 717 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lifestatus.ru performance score
717 ms
331 ms
225 ms
563 ms
228 ms
Our browser made a total of 189 requests to load all elements on the main page. We found that 48% of them (91 requests) were addressed to the original Lifestatus.ru, 9% (17 requests) were made to Vk.com and 4% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Cm.marketgid.com.
Page size can be reduced by 1.3 MB (58%)
2.3 MB
951.3 kB
In fact, the total size of Lifestatus.ru main page is 2.3 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.2 MB which makes up the majority of the site volume.
Potential reduce by 190.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. This page needs HTML code to be minified as it can gain 40.2 kB, which is 19% 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 190.3 kB or 89% of the original size.
Potential reduce by 452.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. Obviously, Lifestatus needs image optimization as it can save up to 452.0 kB or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 582.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 582.0 kB or 74% of the original size.
Potential reduce by 84.8 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. Lifestatus.ru needs all CSS files to be minified and compressed as it can save up to 84.8 kB or 82% of the original size.
Number of requests can be reduced by 64 (35%)
183
119
The browser has sent 183 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifestatus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
lifestatus.ru
717 ms
frame.css
331 ms
style.css
225 ms
jquery.js
563 ms
vote.js
228 ms
imgareaselect-default.css
227 ms
jquery.imgareaselect.pack.js
253 ms
jquery.fancybox-1.3.4.pack.js
447 ms
jquery.fancybox-1.3.4.css
340 ms
site.js
453 ms
openapi.js
393 ms
share.js
262 ms
rollad.js
668 ms
plusone.js
100 ms
widgets.js
5 ms
loader.js
536 ms
top100.jcn
386 ms
tabn2v4.js
317 ms
ajax-loader.gif
113 ms
b-wdgt-add-button_lang_ru.png
342 ms
loader.js
653 ms
login.png
113 ms
back.png
120 ms
reg.png
117 ms
s_submit.png
117 ms
top_logo.jpg
229 ms
reg_button_center.jpg
306 ms
reg_button_left.jpg
340 ms
reg_button_right.jpg
233 ms
log_button_center.jpg
343 ms
log_button_left.jpg
355 ms
log_button_right.jpg
345 ms
banner-new-life.png
351 ms
gr_top.jpg
527 ms
gr_bottom.jpg
563 ms
gr_left.jpg
571 ms
gr_right.jpg
463 ms
gr_lt.jpg
463 ms
gr_rt.jpg
586 ms
gr_lb.jpg
577 ms
gr_rb.jpg
578 ms
down.png
638 ms
add.png
673 ms
s_field.jpg
696 ms
s_button.jpg
697 ms
st1.png
690 ms
st2.png
701 ms
st3.png
747 ms
st4.png
789 ms
st5.png
815 ms
st6.png
816 ms
st7.png
815 ms
st8.png
844 ms
st9.png
877 ms
st10.png
899 ms
st11.png
915 ms
banner-88x31-rambler-black2.gif
254 ms
st12.png
854 ms
st13.png
823 ms
st14.png
831 ms
st15.png
877 ms
st16.png
903 ms
roller.rollad.ru
657 ms
st17.png
806 ms
st18.png
820 ms
st19.png
743 ms
st20.png
722 ms
st21.png
752 ms
st22.png
778 ms
st23.png
794 ms
st24.png
805 ms
st25.png
705 ms
st26.png
710 ms
st27.png
680 ms
st28.png
675 ms
st29.png
688 ms
st30.png
691 ms
st31.png
693 ms
st32.png
704 ms
st33.png
679 ms
st34.png
674 ms
st35.png
675 ms
st36.png
685 ms
r_value.png
690 ms
r_button.png
747 ms
but.jpg
704 ms
486598-big.jpg
1602 ms
upload.gif
239 ms
cb=gapi.loaded_0
36 ms
widget_community.php
375 ms
but_right.jpg
646 ms
but_left.jpg
665 ms
vk.png
676 ms
fb.png
652 ms
tv.png
678 ms
share_logo.png
385 ms
mail.png
657 ms
grstat
576 ms
api_min.js
1063 ms
widget_like.php
409 ms
hit
260 ms
like.php
112 ms
top100.scn
134 ms
p_active.png
658 ms
ga.js
30 ms
p_item.png
730 ms
p_right.png
725 ms
counter_center.jpg
717 ms
counter_left.jpg
713 ms
lifestatus.ru.11301.js
411 ms
__utm.gif
27 ms
counter_right.jpg
673 ms
qeKvIRsJabD.js
503 ms
LVx-xkvaJ0b.png
558 ms
c_bg.png
684 ms
12.png
691 ms
subscribe.jpg
809 ms
promo.png
702 ms
paper-clip.png
727 ms
hit
136 ms
loader_nav19176_3.js
119 ms
lite.css
197 ms
lite.js
479 ms
lang3_0.js
263 ms
widget_community.css
264 ms
xdm.js
264 ms
al_community.js
266 ms
widgets.css
210 ms
al_like.js
239 ms
hit;Mgidohvat
293 ms
1
763 ms
lifestatus.ru.17213.js
139 ms
1
587 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
46 ms
cb=gapi.loaded_1
32 ms
fastbutton
111 ms
hit;Mgidohvat
154 ms
postmessageRelay
120 ms
e_b05f0523.jpg
362 ms
A2oq_d-BDXs.jpg
370 ms
BNO0c1cXnMM.jpg
367 ms
DIp2WZeViHs.jpg
444 ms
S-PQfPDJxrw.jpg
370 ms
iYK44EfCs_E.jpg
246 ms
pBhCBa6K3sI.jpg
374 ms
Ok7pwOW92bE.jpg
251 ms
fRAQMwk1dKY.jpg
368 ms
camera_50.png
123 ms
deactivated_50.png
130 ms
w_logo.png
119 ms
like_widget.png
122 ms
hit;Mgidohvat
194 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
46 ms
cb=gapi.loaded_0
44 ms
cb=gapi.loaded_1
45 ms
3193398744-postmessagerelay.js
62 ms
rpc:shindig_random.js
82 ms
hit;Mgidohvat
138 ms
cb=gapi.loaded_0
9 ms
jot
95 ms
share_button
280 ms
8286630_200x200.jpg
407 ms
i.js
3364 ms
ti
256 ms
1
295 ms
10133944_200x200.jpg
397 ms
10592976_200x200.jpg
396 ms
10302307_200x200.jpg
396 ms
9670327_200x200.jpg
396 ms
widgets_marketgid.png
406 ms
jquery.js
780 ms
uber-share.js
538 ms
20.css
536 ms
icon-2.png
275 ms
1791616_120x120.jpg
412 ms
ni
254 ms
2153966_120x120.jpg
407 ms
530743_120x120.jpg
407 ms
1660938_120x120.jpg
407 ms
1498042_120x120.jpg
407 ms
1553800_120x120.jpg
407 ms
423727_120x120.jpg
546 ms
mm-oval.png
134 ms
preloader.gif
128 ms
grstat
275 ms
d525461.gif
1073 ms
code.js
265 ms
counter
134 ms
tracker
134 ms
lifestatus.ru SEO score
N/A
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifestatus.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Lifestatus.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.
lifestatus.ru
Open Graph description is not detected on the main page of Lifestatus. 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: