10.6 sec in total
709 ms
9 sec
884 ms
Welcome to real-lineage.ru homepage info - get ready to check Real Lineage best content for Russia right away, or after learning these important things about real-lineage.ru
Здарова. Потерял кучe времени на Lineage 2 и она потеряла интерес? много опыта l2? месяцы? года? задротсва и жалко просто выкидывать опыт игры туда, игрового процесса в никуда? если да, то тогда тебе ...
Visit real-lineage.ruWe analyzed Real-lineage.ru page load time and found that the first response time was 709 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
real-lineage.ru performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value19.3 s
0/100
25%
Value15.5 s
0/100
10%
Value3,560 ms
1/100
30%
Value0.311
37/100
15%
Value27.7 s
0/100
10%
709 ms
535 ms
320 ms
282 ms
319 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 25% of them (37 requests) were addressed to the original Real-lineage.ru, 8% (12 requests) were made to Cstatic.weborama.fr and 7% (10 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source W210.am15.net.
Page size can be reduced by 653.9 kB (61%)
1.1 MB
413.0 kB
In fact, the total size of Real-lineage.ru main page is 1.1 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. 60% of websites need less resources to load. Javascripts take 651.6 kB which makes up the majority of the site volume.
Potential reduce by 50.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 50.3 kB or 74% of the original size.
Potential reduce by 27.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. Obviously, Real Lineage needs image optimization as it can save up to 27.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 495.5 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 495.5 kB or 76% of the original size.
Potential reduce by 80.6 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. Real-lineage.ru needs all CSS files to be minified and compressed as it can save up to 80.6 kB or 82% of the original size.
Number of requests can be reduced by 97 (74%)
131
34
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Real Lineage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
real-lineage.ru
709 ms
mootools.js
535 ms
caption.js
320 ms
plusone.js
282 ms
system.css
319 ms
general.css
329 ms
template.css
333 ms
typo.css
330 ms
ja.script.js
479 ms
ja.moomenu.css
477 ms
ja.moomenu.js
483 ms
greenred.css
491 ms
bout.php
442 ms
widgets.js
209 ms
in.js
148 ms
openapi.js
508 ms
loader.js
397 ms
bout.php
964 ms
bn.php
308 ms
bn.php
314 ms
loader.js
465 ms
cb=gapi.loaded_0
131 ms
logo
395 ms
gaming.jpg
1255 ms
bullet.gif
247 ms
wrapper-bg.png
375 ms
grad-3.gif
246 ms
header-bg.gif
243 ms
logo.png
374 ms
emailButton.png
374 ms
printButton.png
899 ms
pdf_button.png
898 ms
8553184-1302786850885-3794.gif
1043 ms
mainnav-bg.gif
551 ms
mainnav-sep-2.gif
550 ms
mainnav-active-2.gif
550 ms
arrow-1.gif
1118 ms
content-center2.gif
1116 ms
content-top2.gif
1118 ms
content-bot2.gif
1039 ms
vline.gif
1038 ms
like.php
890 ms
secureAnonymousFramework
537 ms
upload.gif
894 ms
Share.js
633 ms
widget_like.php
1119 ms
grstat
495 ms
api_min.js
3790 ms
box-br.gif
979 ms
box-bl.gif
801 ms
box-tr.gif
986 ms
box-tl.gif
986 ms
h3-bg.gif
984 ms
sep.gif
985 ms
arrow.png
1011 ms
input-bg.gif
1176 ms
grad-1.gif
1608 ms
counter2
365 ms
5-4476.jpg
149 ms
5-4892.jpg
894 ms
5-8611.jpg
365 ms
code.js
568 ms
hit
1395 ms
watch.js
11 ms
uid.php
444 ms
fpx.php
640 ms
tk.php
435 ms
817 ms
4336 ms
button.71000885400e222c3c0eec823f8f93f0.js
580 ms
cb=gapi.loaded_1
190 ms
fastbutton
586 ms
share
322 ms
sprite_connect_v14.png
866 ms
postmessageRelay
328 ms
OZhivdPHVp_.js
946 ms
LVx-xkvaJ0b.png
1042 ms
counter
222 ms
share-counter.xml
694 ms
advmaker
1278 ms
rsc.php
678 ms
advmaker
298 ms
tweet_button.fd774b599f565016d763dd860cb31c79.ru.html
131 ms
1077434459-postmessagerelay.js
269 ms
rpc:shindig_random.js
121 ms
grlryt2bdKIyfMSOhzd1eA.woff
326 ms
cb=gapi.loaded_0
220 ms
cb=gapi.loaded_1
172 ms
loader_nav19239_3.js
166 ms
lite.css
314 ms
lite.js
1152 ms
lang3_0.js
303 ms
widgets.css
301 ms
xdm.js
296 ms
al_like.js
300 ms
jot
188 ms
advmaker
123 ms
cb=gapi.loaded_0
21 ms
hit
220 ms
renegade-smart
1687 ms
pixel
276 ms
emily
409 ms
audtd.png
785 ms
sync
352 ms
sync
409 ms
556d807310823b694772f699.js
361 ms
pixel
24 ms
sync
266 ms
pixel
205 ms
admitad
322 ms
like_widget.png
148 ms
dispatch.fcgi
209 ms
renegade-smart
139 ms
share_button
1414 ms
pixel.gif
539 ms
external_all.html
167 ms
external_libs.js
403 ms
jquery.js
944 ms
uber-share.js
445 ms
20.css
472 ms
external_tracking.fcgi
346 ms
dispatch.fcgi
483 ms
dispatch.fcgi
354 ms
13071801.js
738 ms
transp.gif
302 ms
weborama.js
319 ms
transp.gif
250 ms
transp.gif
107 ms
get
545 ms
hdmr.sddan.com
419 ms
graphinium_match.php
313 ms
pixel.gif
316 ms
dn_iframe.js
349 ms
mm-oval.png
227 ms
preloader.gif
221 ms
grstat
406 ms
d525461.gif
409 ms
counter
217 ms
transp.gif
135 ms
transp.gif
178 ms
transp.gif
88 ms
dn.html
226 ms
tracker
218 ms
transp.gif
65 ms
transp.gif
78 ms
dn.js
235 ms
transp.gif
87 ms
401736.gif
35 ms
tracker
192 ms
real-lineage.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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
real-lineage.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
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
Issues were logged in the Issues panel in Chrome Devtools
real-lineage.ru SEO score
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Real-lineage.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 Real-lineage.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.
real-lineage.ru
Open Graph description is not detected on the main page of Real Lineage. 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: