15.8 sec in total
1.1 sec
14.2 sec
537 ms
Visit lineage.com now to see the best up-to-date Lineage content and also check out these interesting facts you probably never knew about lineage.com
2024. 4. 3. UPDATE
Visit lineage.comWe analyzed Lineage.com page load time and found that the first response time was 1.1 sec and then it took 14.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lineage.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value10.1 s
0/100
25%
Value10.6 s
7/100
10%
Value380 ms
70/100
30%
Value0.012
100/100
15%
Value8.7 s
36/100
10%
1051 ms
1527 ms
4773 ms
5347 ms
4964 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lineage.com, 86% (91 requests) were made to Static.plaync.co.kr and 8% (8 requests) were made to Lineage.plaync.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Static.plaync.co.kr.
Page size can be reduced by 614.7 kB (13%)
4.6 MB
4.0 MB
In fact, the total size of Lineage.com main page is 4.6 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. 70% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 66.0 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 66.0 kB or 81% of the original size.
Potential reduce by 168.5 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 images are well optimized though.
Potential reduce by 284.8 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 284.8 kB or 71% of the original size.
Potential reduce by 95.4 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.com needs all CSS files to be minified and compressed as it can save up to 95.4 kB or 84% of the original size.
Number of requests can be reduced by 40 (38%)
104
64
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 30 to 1 for JavaScripts and as a result speed up the page load time.
lineage.com
1051 ms
lineage.plaync.com
1527 ms
main.css
4773 ms
jquery_171_min.js
5347 ms
tram.min.js
4964 ms
login.min.js
4780 ms
suggest.js
4779 ms
layout_ver3.js
5162 ms
skipnav.js
4962 ms
ModalPopup.min.js
4968 ms
main_ver3.js
5162 ms
doT-1.0.3.min.js
5153 ms
lineage_v3.js
406 ms
base
502 ms
lin.api.login.js
419 ms
gnbload.js
5153 ms
launcherPluginLoader.js
5159 ms
launcher_v2.js
634 ms
ncllmplugin_utf-8.js
5331 ms
live_keyword_lineage1.js
5160 ms
plaync_logger_footer.js
5162 ms
clickzone_plaync.js
5160 ms
loggers.entry.js
5161 ms
loginInfo
428 ms
floatingbanner
216 ms
ic_suggest_off.gif
193 ms
gnb_min.js
388 ms
gnb_min.css
193 ms
ncllmplugin_utf-8.js
192 ms
checkPlugin.js
196 ms
launcher.js
195 ms
ic1.gif
194 ms
bg_gnb_15782.gif
194 ms
gnb_85246.gif
204 ms
header_m.png
193 ms
bi_lineage.png
195 ms
ic_nav.png
194 ms
search_m.png
193 ms
l1_m_1100x52920160316105205.jpg
1152 ms
lieage_1100x529_220160309093349.jpg
1164 ms
03_1100x52920160316141400.png
1896 ms
blank.gif
368 ms
l1_m_1100x52920160303111516.jpg
1521 ms
l1_m_1100x52920160217093627.jpg
1341 ms
l1_m_1100x529(cday)20160309090418.jpg
1336 ms
l1_m_1100x52920160309093349.jpg
1725 ms
l1_m_54x5420160316105205.jpg
1356 ms
lieage_54x5420160309093349.jpg
1530 ms
03_54x5420160316141400.png
1535 ms
l1_m_54x5420160303111517.png
1550 ms
l1_m_54x5420160217093627.jpg
1711 ms
l1_m_54x54(cday)20160309090418.jpg
1723 ms
l1_m_54x5420160309093349.jpg
1728 ms
promotion_bg_side.png
1726 ms
micon.png
1885 ms
gamestart_m.png
2093 ms
gamestart_light.png
1898 ms
bg_box.gif
1903 ms
256x121220160120105314.jpg
1914 ms
ic_list.gif
2063 ms
ic_more.gif
2072 ms
ico_num.gif
2084 ms
pb_320160316165939.jpg
2087 ms
loading.gif
2104 ms
0315_cday543_256x18620160315104507.jpg
2244 ms
world_001_QT20160309163106.jpg
2443 ms
pb_120160316165658.jpg
2267 ms
server_001_HF20160316181154.jpg
2464 ms
server_002_QT20160316181154.jpg
2275 ms
server_003_QT20160316181154.jpg
2290 ms
gameStartLayer.js
2301 ms
quarter_120160316164750.jpg
2323 ms
quarter_220160316164750.jpg
2329 ms
quarter_120160310131810.jpg
2344 ms
quarter_120160307171422.jpg
2298 ms
Life_001_HF20160316183000.jpg
1906 ms
Life_002_QT20160316183000.jpg
1527 ms
Life_003_QT20160316183000.jpg
1360 ms
bg_box_s.gif
1360 ms
bg_box_m.gif
1361 ms
0120160316150922.png
1338 ms
0220160316150922.png
1543 ms
6_nshop_2015102720151026140129.png
1549 ms
7_nshop_2015102720151026140129.PNG
1537 ms
1_nshop_2015102820151028123708.png
1392 ms
120160302111314.png
1326 ms
8_nshop_2015102720151026140129.png
1707 ms
2_nshop_2015102820151028123708.png
1711 ms
y20151130141151.png
1520 ms
m20151127160942.png
1577 ms
bg_nshop.gif
1377 ms
icon.png
1381 ms
ic_footer.gif
1536 ms
grade.png
1537 ms
footer.gif
1406 ms
gameStartLayer.css
1152 ms
pna_ncsoft_net.js
193 ms
ga.js
493 ms
fbevents.js
488 ms
user
459 ms
tracker.tsp
905 ms
ic_down.gif
193 ms
bg_default.gif
195 ms
110 ms
__utm.gif
27 ms
93 ms
lineage.com accessibility score
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
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lineage.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
lineage.com 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
N/A
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lineage.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 Korean. Our system also found out that Lineage.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.com
Open Graph description is not detected on the main page of 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: