2.9 sec in total
125 ms
2.5 sec
237 ms
Click here to check amazing Lineage content. Otherwise, check out these important facts you probably never knew about lineage.ro
The most popular Lineage 2 classic server waiting for you. Download L2 client and play! You expect grandiose battles and incredible siege. The adrenaline just rolls!
Visit lineage.roWe analyzed Lineage.ro page load time and found that the first response time was 125 ms and then it took 2.7 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.ro performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value15.6 s
0/100
25%
Value10.7 s
7/100
10%
Value5,300 ms
0/100
30%
Value0.392
26/100
15%
Value22.0 s
1/100
10%
125 ms
373 ms
66 ms
140 ms
1032 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lineage.ro, 77% (110 requests) were made to Lineage2dex.com and 5% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Mc.yandex.ru.
Page size can be reduced by 129.2 kB (9%)
1.4 MB
1.3 MB
In fact, the total size of Lineage.ro main page is 1.4 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. 75% 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 88.1 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 88.1 kB or 86% of the original size.
Potential reduce by 7.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 33.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 406 B
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.ro has all CSS files already compressed.
Number of requests can be reduced by 120 (88%)
136
16
The browser has sent 136 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 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lineage.ro
125 ms
lineage2dex.com
373 ms
js
66 ms
gtm.js
140 ms
tag.js
1032 ms
3877-fd5d7a3c5d2fba8204cf73c5f88b18c6.jpg
392 ms
preload.png
281 ms
char07.png
281 ms
logo.svg
279 ms
discord.svg
42 ms
facebook.svg
37 ms
youtube.svg
35 ms
server-ico-1.svg
50 ms
server-ico-2.svg
52 ms
widget
67 ms
stylesheet.css
63 ms
jquery-3.4.1.min.js
67 ms
swiper.min.js
77 ms
swiper.min.css
77 ms
popper.min.js
111 ms
tippy-bundle.iife.min.js
422 ms
Chart.min.js
109 ms
insertmedia.js
147 ms
jquery.mCustomScrollbar.min.css
146 ms
jquery.mCustomScrollbar.min.js
189 ms
jquery.mousewheel.min.js
194 ms
main.css
257 ms
app.js
256 ms
watch.js
264 ms
12.png
266 ms
1.png
265 ms
233.png
556 ms
379.png
424 ms
2.png
555 ms
105.png
554 ms
344.png
425 ms
22.png
542 ms
638.png
637 ms
9.png
543 ms
518.png
566 ms
366.png
566 ms
107.png
783 ms
13.png
795 ms
494.png
786 ms
127.png
583 ms
101.png
566 ms
353.png
576 ms
354.png
580 ms
639.png
554 ms
index.c28a9f9cf58c0cfb74b1.css
125 ms
050107a671106733d869.js
305 ms
705.png
793 ms
118.png
570 ms
466.png
808 ms
js
96 ms
analytics.js
92 ms
642.png
561 ms
641.png
565 ms
142.png
581 ms
143.png
564 ms
js
96 ms
destination
204 ms
destination
248 ms
fbevents.js
244 ms
p.js
534 ms
p.js
537 ms
636.png
542 ms
716.png
553 ms
635.png
571 ms
collect
175 ms
collect
174 ms
collect
301 ms
66.png
519 ms
39.png
537 ms
220.png
822 ms
97.png
822 ms
164.png
547 ms
224.png
821 ms
223.png
560 ms
161.png
416 ms
collect
141 ms
454.png
428 ms
46826.png
439 ms
js
137 ms
jquery.mousewheel.min.js
146 ms
main.js
23 ms
46651.png
323 ms
Calypso-Regular.woff
685 ms
webfont.js
44 ms
ga-audiences
96 ms
46880.png
322 ms
46620.png
334 ms
46909.png
344 ms
ga-audiences
144 ms
46764.png
552 ms
46676.png
335 ms
46918.png
561 ms
css
31 ms
46907.png
653 ms
43342.png
676 ms
43311.png
699 ms
46677.png
754 ms
qkBWXvsO6sreR8E-b8m9xL0.woff
63 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCMPrc.woff
139 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCMPrc.woff
117 ms
46769.png
522 ms
46766.png
524 ms
46649.png
522 ms
46454.png
526 ms
42152.png
526 ms
31039.png
531 ms
46582.png
514 ms
46396.png
503 ms
46906.png
489 ms
41631.png
483 ms
46646.png
489 ms
46674.png
708 ms
44425.png
477 ms
40359.png
488 ms
42388.png
482 ms
46534.png
699 ms
46587.png
465 ms
43208.png
466 ms
41456.png
460 ms
36334.png
684 ms
46882.png
463 ms
46647.png
457 ms
45409.png
453 ms
42169.png
465 ms
38791.png
447 ms
46707.png
462 ms
39488.png
292 ms
telegram.svg
293 ms
btn-dec.svg
307 ms
advert.gif
747 ms
scroll-down.svg
500 ms
bg.jpg
243 ms
arrow-dec.svg
481 ms
char02.png
257 ms
bg.jpg
262 ms
selection-arrow-down.svg
259 ms
bg.jpg
268 ms
sync_cookie_image_decide
200 ms
lineage.ro accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
lineage.ro 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
lineage.ro SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Lineage.ro 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 Lineage.ro 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.ro
Open Graph data is detected on the main page of Lineage. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: