7 sec in total
372 ms
6 sec
550 ms
Visit lj.ru now to see the best up-to-date Lj content for Russia and also check out these interesting facts you probably never knew about lj.ru
Your life is the best story! Just start your blog today!
Visit lj.ruWe analyzed Lj.ru page load time and found that the first response time was 372 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
lj.ru performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value10.4 s
0/100
25%
Value15.2 s
1/100
10%
Value1,830 ms
9/100
30%
Value0.337
33/100
15%
Value25.0 s
0/100
10%
372 ms
298 ms
30 ms
32 ms
23 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lj.ru, 12% (19 requests) were made to L-stat.livejournal.net and 6% (10 requests) were made to Ssp.rambler.ru. The less responsive or slowest element that took the longest time to load (835 ms) relates to the external source St.top100.ru.
Page size can be reduced by 2.0 MB (63%)
3.3 MB
1.2 MB
In fact, the total size of Lj.ru main page is 3.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. 80% 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 314.6 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 44.4 kB, which is 12% 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 314.6 kB or 83% of the original size.
Potential reduce by 1.2 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. Lj images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 68% of the original size.
Potential reduce by 366.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. Lj.ru needs all CSS files to be minified and compressed as it can save up to 366.8 kB or 45% of the original size.
Number of requests can be reduced by 105 (81%)
130
25
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lj. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lj.ru
372 ms
www.livejournal.com
298 ms
l-stat.livejournal.net
30 ms
l-stat.livejournal.net
32 ms
l-stat.livejournal.net
23 ms
8 ms
rta.js
59 ms
analytics.js
87 ms
gtm.js
102 ms
autocontext2_async.js
400 ms
beacon.js
77 ms
logo.svg
66 ms
s-icons.svg
53 ms
print-logo.png
60 ms
CaMCUg==
50 ms
6iMf6F5oPfgFuPAEB
45 ms
78 ms
218 ms
300 ms
xtcore.js
210 ms
top100.js
835 ms
yandex_metrika.js
95 ms
yandex_metrika_homepage.js
96 ms
emily
810 ms
begun.html
808 ms
collect
42 ms
collect
180 ms
watch.js
200 ms
collect
127 ms
emily
739 ms
autocontext2_async.js
739 ms
QRzzWv9J88AsQYwKv
15 ms
onmg9+AbFaAXg=
12 ms
green2.min.js
670 ms
watch.js
812 ms
001001.gif
569 ms
gw.js
555 ms
gpt.js
536 ms
preloader-disc-blue-white-16.gif
321 ms
272 ms
unit.png
106 ms
emily
173 ms
autocontext2.js
176 ms
593584368
642 ms
128 ms
505 ms
autocontext2.js
475 ms
pubads_impl_82.js
378 ms
top100.scn
361 ms
ban.ban
356 ms
advert.gif
321 ms
collect
286 ms
community.gif
270 ms
142720
273 ms
autocontext2_async_main.1e3afda065.js
487 ms
11282975
169 ms
421069
165 ms
userinfo.gif
159 ms
syndicated.svg
161 ms
community_v3.svg
162 ms
userinfo_v3.svg
161 ms
autocontext2_main.d939681776.js
289 ms
729327586.js
154 ms
hit.xiti
274 ms
1
150 ms
collect
33 ms
collect
59 ms
collect
70 ms
autocontext2_main.d939681776.js
418 ms
collect
124 ms
ads
192 ms
ads
175 ms
container.html
169 ms
pixel.gif
169 ms
27737433
160 ms
12328.js
72 ms
collect
58 ms
sync
59 ms
sync
60 ms
begun_scripts.508f4b3b74.js
127 ms
osd.js
17 ms
ads.jsonp
141 ms
358132-10.js
148 ms
begun_scripts.508f4b3b74.js
130 ms
sync
12 ms
js
80 ms
358088-2.js
178 ms
begun_utils.d76b1ad8d2.js
141 ms
32896b6ff9c9808d2cbd9bc0ee261528.jpg
152 ms
id.js
55 ms
emily.html
17 ms
pixel.gif
58 ms
show_ads.js
10 ms
begun_utils.d76b1ad8d2.js
195 ms
ca-pub-8474433047863685.js
168 ms
zrt_lookup.html
206 ms
show_ads_impl.js
84 ms
ads
138 ms
ads
285 ms
osd.js
37 ms
context.jsp
133 ms
tap.php
271 ms
player.js
52 ms
widget.backfill.loader.js
92 ms
tap.php
255 ms
context.jsp
157 ms
page_load
312 ms
event
167 ms
widget.backfill.css
54 ms
vsap.css
38 ms
vsap.min.js
55 ms
widget.backfill.js
103 ms
m_js_controller.js
135 ms
abg.js
152 ms
page_load
326 ms
widget-icons.woff
211 ms
ck-confirm
151 ms
903acc3.jsonp
175 ms
favicon
155 ms
googlelogo_color_112x36dp.png
174 ms
nessie_icon_tiamat_white.png
91 ms
s
78 ms
push
174 ms
x_button_blue2.png
97 ms
begun_tpl_block_468x60.2238ede18e.js
144 ms
gp_match
28 ms
pixel
18 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
18 ms
sandbox
261 ms
sandbox
261 ms
cnysBEGUN.gif
109 ms
begun
206 ms
sync
327 ms
sync.gif
276 ms
saveRtbUser
253 ms
begun
262 ms
rta.js
82 ms
log_errors
138 ms
ui
86 ms
log_errors
150 ms
cnysBEGUN.gif
13 ms
begun
13 ms
sync2.204
276 ms
activeview
14 ms
image
149 ms
pixel.gif
204 ms
image
119 ms
begun
134 ms
sync
196 ms
sync
140 ms
pixel
41 ms
audsp
198 ms
admitad
298 ms
activeview
18 ms
audsp
115 ms
activeview
17 ms
pixel.gif
97 ms
renegade
108 ms
collect
115 ms
sync2.204
126 ms
pixel
41 ms
108 ms
sync
8 ms
lj.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
lj.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
lj.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lj.ru can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Lj.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.
lj.ru
Open Graph description is not detected on the main page of Lj. 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: