Tools & Wizards About Us
lineage2dex.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

lineage2dex.com

Free to Play Lineage 2 classic server | Lineage2 Dex

Page Load Speed

1.9 sec in total

First Response

274 ms

Resources Loaded

1.1 sec

Page Rendered

504 ms

lineage2dex.com screenshot

About Website

Click here to check amazing Lineage2 Dex content for Belarus. Otherwise, check out these important facts you probably never knew about lineage2dex.com

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 lineage2dex.com

Key Findings

We analyzed Lineage2dex.com page load time and found that the first response time was 274 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

lineage2dex.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value2,280 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.161

72/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

lineage2dex.com

274 ms

font-awesome.min.css

201 ms

jquery.arcticmodal-0.3.css

209 ms

style.css

204 ms

jquery-1.11.1.js

212 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 74% of them (35 requests) were addressed to the original Lineage2dex.com, 6% (3 requests) were made to Google-analytics.com and 6% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (486 ms) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 477.7 kB (17%)

Content Size

2.7 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lineage2dex.com main page is 2.7 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. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 57.9 kB

  • Original 64.5 kB
  • After minification 28.3 kB
  • After compression 6.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 36.3 kB, which is 56% 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 57.9 kB or 90% of the original size.

Image Optimization

-1%

Potential reduce by 23.0 kB

  • Original 2.2 MB
  • After minification 2.2 MB

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. Lineage2 Dex images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 355.8 kB

  • Original 458.2 kB
  • After minification 318.8 kB
  • After compression 102.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 355.8 kB or 78% of the original size.

CSS Optimization

-80%

Potential reduce by 41.0 kB

  • Original 51.5 kB
  • After minification 46.4 kB
  • After compression 10.5 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. Lineage2dex.com needs all CSS files to be minified and compressed as it can save up to 41.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (22%)

Requests Now

37

After Optimization

29

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lineage2 Dex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

lineage2dex.com

lineage2dex.com

274 ms

font-awesome.min.css

font-awesome.min.css

201 ms

jquery.arcticmodal-0.3.css

jquery.arcticmodal-0.3.css

209 ms

style.css

style.css

204 ms

jquery-1.11.1.js

jquery-1.11.1.js

212 ms

jquery-ui.min.js

jquery-ui.min.js

197 ms

jquery.arcticmodal-0.3.min.js

jquery.arcticmodal-0.3.min.js

196 ms

ajax.js

ajax.js

409 ms

main.js

main.js

408 ms

gtm.js

gtm.js

85 ms

logo-blue.png

logo-blue.png

69 ms

qcT8OAVaNn.jpg

qcT8OAVaNn.jpg

72 ms

3f6kJKkOn3.jpg

3f6kJKkOn3.jpg

71 ms

8RWJdnGi1o.png

8RWJdnGi1o.png

77 ms

layer-1.jpg

layer-1.jpg

69 ms

layer-2.jpg

layer-2.jpg

72 ms

layer-3.jpg

layer-3.jpg

73 ms

layer-4-1.jpg

layer-4-1.jpg

74 ms

gludio_castle.jpg

gludio_castle.jpg

73 ms

dion_castle.jpg

dion_castle.jpg

73 ms

giran_castle.jpg

giran_castle.jpg

75 ms

oren_castle.jpg

oren_castle.jpg

73 ms

aden_castle.jpg

aden_castle.jpg

76 ms

innadrile_castle.jpg

innadrile_castle.jpg

75 ms

godad_castle.jpg

godad_castle.jpg

76 ms

rune_castle.jpg

rune_castle.jpg

76 ms

schuttgart_castle.jpg

schuttgart_castle.jpg

77 ms

layer-5.jpg

layer-5.jpg

78 ms

logo-gray.png

logo-gray.png

77 ms

g2a-icon.png

g2a-icon.png

76 ms

progress-server.png

progress-server.png

77 ms

arrow-info-white.png

arrow-info-white.png

77 ms

Cinzel-Regular.otf

Cinzel-Regular.otf

18 ms

Cinzel-Bold.otf

Cinzel-Bold.otf

9 ms

Cinzel-Black.otf

Cinzel-Black.otf

8 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

9 ms

conversion_async.js

conversion_async.js

33 ms

analytics.js

analytics.js

6 ms

watch.js

watch.js

486 ms

collect

collect

69 ms

104 ms

collect

collect

104 ms

collect

collect

52 ms

collect

collect

55 ms

44 ms

ga-audiences

ga-audiences

21 ms

ga-audiences

ga-audiences

18 ms

Accessibility Review

lineage2dex.com accessibility score

88

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best Practices

lineage2dex.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Uses deprecated APIs

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lineage2dex.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lineage2dex.com 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 Lineage2dex.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.

Social Sharing Optimization

lineage2dex.com

Open Graph description is not detected on the main page of Lineage2 Dex. 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: