3.1 sec in total
279 ms
2.6 sec
251 ms
Visit lineage-realm.com now to see the best up-to-date Lineage Realm content for Greece and also check out these interesting facts you probably never knew about lineage-realm.com
Home: Your lineage wiki. Full drop calculator and skill, quest, weapon and armor database.
Visit lineage-realm.comWe analyzed Lineage-realm.com page load time and found that the first response time was 279 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
lineage-realm.com performance score
279 ms
662 ms
94 ms
453 ms
10 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 57% of them (48 requests) were addressed to the original Lineage-realm.com, 8% (7 requests) were made to Apis.google.com and 6% (5 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (911 ms) belongs to the original domain Lineage-realm.com.
Page size can be reduced by 932.8 kB (53%)
1.8 MB
834.2 kB
In fact, the total size of Lineage-realm.com main page is 1.8 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 70.4 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 16.9 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 70.4 kB or 79% of the original size.
Potential reduce by 7.3 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. Lineage Realm images are well optimized though.
Potential reduce by 810.4 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 810.4 kB or 65% of the original size.
Potential reduce by 44.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. Lineage-realm.com needs all CSS files to be minified and compressed as it can save up to 44.6 kB or 82% of the original size.
Number of requests can be reduced by 40 (49%)
82
42
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lineage Realm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
lineage-realm.com
279 ms
www.lineage-realm.com
662 ms
85cc29114361f080d061d2b007a4c140_all.css
94 ms
e3b107e0e2c57a07194ac6d0fc06b608.js
453 ms
addthis_widget.js
10 ms
show_ads.js
4 ms
ga.js
22 ms
body_bg.jpg
442 ms
lineage_realm_logo.png
213 ms
Giran-Castle-Ecarlate-Clan-Lord_homepage_gal.jpg
214 ms
Horse-squad_homepage_gal.jpg
214 ms
InsanityZone-Brick_homepage_gal.jpg
212 ms
register_button.png
212 ms
rss_icon_grey.jpg
321 ms
facebook_icon_grey.jpg
320 ms
twitter_icon_grey.jpg
318 ms
ncsoft_logo.jpg
317 ms
eng-GB.gif
319 ms
pol-PL.gif
391 ms
por-PT.gif
392 ms
ell-GR.gif
394 ms
esl-ES.gif
392 ms
rom-RO.gif
393 ms
cze-CZ.gif
479 ms
fre-FR.gif
479 ms
rus-RU.gif
480 ms
ger-DE.gif
482 ms
lit-LT.gif
482 ms
hun-HU.gif
528 ms
slk-SK.gif
566 ms
dut-NL.gif
566 ms
tur-TR.gif
568 ms
chi-CN.gif
569 ms
all.js
65 ms
header_left_area_1.jpg
911 ms
header_right_area.jpg
605 ms
menu_bg.jpg
730 ms
search_bg.jpg
645 ms
input_bg.jpg
646 ms
dc_search_send.jpg
646 ms
main_area_bg.jpg
693 ms
h1_bg.jpg
820 ms
bg_advert.jpg
683 ms
zrt_lookup.html
49 ms
show_ads_impl.js
50 ms
__utm.gif
33 ms
105 ms
ads
246 ms
osd.js
96 ms
0sTQzbapM8j.js
111 ms
0sTQzbapM8j.js
161 ms
ads
266 ms
_ate.track.config_resp
48 ms
300lo.json
61 ms
ping
53 ms
sh.48536d49e4da3bdba54606b4.html
22 ms
like.php
112 ms
box_side_top.jpg
588 ms
box_side_middle.jpg
623 ms
box_content_bg_register.jpg
629 ms
box_side_bottom.jpg
676 ms
box_content_bg.jpg
712 ms
likebox.php
95 ms
widgets.js
19 ms
plusone.js
51 ms
counter.e61152ce165bc90fac45.js
23 ms
like.php
115 ms
shares.json
19 ms
cb=gapi.loaded_0
24 ms
cb=gapi.loaded_1
36 ms
fastbutton
47 ms
body_low_bg.jpg
608 ms
footer_content_bg.jpg
612 ms
slide_bullet.png
660 ms
the-realm.jpg
869 ms
GUptfeGGGu9.css
77 ms
15GlxZpw14A.css
88 ms
postmessageRelay
51 ms
rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA
8 ms
4qFiRLLPSF7.js
96 ms
lH1ibRl5GKq.png
48 ms
971028622-postmessagerelay.js
20 ms
rpc:shindig_random.js
21 ms
cb=gapi.loaded_0
3 ms
lineage-realm.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lineage-realm.com 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), while the claimed language is English. Our system also found out that Lineage-realm.com 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.
lineage-realm.com
Open Graph description is not detected on the main page of Lineage Realm. 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: