Tools & Wizards About Us
l2database.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

l2database.com

Źródło wiedzy o grach komputerowych

Page Load Speed

23.5 sec in total

First Response

7 sec

Resources Loaded

16.1 sec

Page Rendered

338 ms

l2database.com screenshot

About Website

Visit l2database.com now to see the best up-to-date L 2 Database content and also check out these interesting facts you probably never knew about l2database.com

Lineage 2 Drop Database for GoD, Goddess of Destruction, GoD Harmony, GoD Tauti, High Five, Freya, Gracia Final/Plus, high5, h5, L2 C4, C5, C6, Interlude, Kamael, Hellbound, & Epilogue. Full High Five...

Visit l2database.com

Key Findings

We analyzed L2database.com page load time and found that the first response time was 7 sec and then it took 16.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

l2database.com performance score

0

Network Requests Diagram

l2database.com

7044 ms

mootools-uncompressed.js

340 ms

caption.js

208 ms

system.css

209 ms

general.css

209 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 35% of them (35 requests) were addressed to the original L2database.com, 8% (8 requests) were made to Apis.google.com and 7% (7 requests) were made to Pub.clicksor.net. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source A.yesadsrv.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (60%)

Content Size

1.8 MB

After Optimization

715.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of L2database.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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 99.2 kB

  • Original 129.0 kB
  • After minification 126.5 kB
  • After compression 29.8 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 99.2 kB or 77% of the original size.

Image Optimization

-12%

Potential reduce by 36.0 kB

  • Original 297.0 kB
  • After minification 261.0 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, L 2 Database needs image optimization as it can save up to 36.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 737.2 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 376.9 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 737.2 kB or 66% of the original size.

CSS Optimization

-81%

Potential reduce by 200.4 kB

  • Original 248.2 kB
  • After minification 231.0 kB
  • After compression 47.8 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. L2database.com needs all CSS files to be minified and compressed as it can save up to 200.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (63%)

Requests Now

95

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

l2database.com

l2database.com

7044 ms

mootools-uncompressed.js

mootools-uncompressed.js

340 ms

caption.js

caption.js

208 ms

system.css

system.css

209 ms

general.css

general.css

209 ms

template.css

template.css

212 ms

script.js

script.js

214 ms

addthis_widget.js

addthis_widget.js

49 ms

show_ads.js

show_ads.js

11 ms

brand

brand

17 ms

showAd.php

showAd.php

74 ms

brand

brand

43 ms

ga.js

ga.js

91 ms

vote.gif

vote.gif

512 ms

Page-BgSimpleGradient.jpg

Page-BgSimpleGradient.jpg

142 ms

Page-BgGlare.png

Page-BgGlare.png

302 ms

PostDateIcon.png

PostDateIcon.png

176 ms

PostAuthorIcon.png

PostAuthorIcon.png

176 ms

pdf_button.png

pdf_button.png

173 ms

printButton.png

printButton.png

176 ms

emailButton.png

emailButton.png

283 ms

rating_star.png

rating_star.png

300 ms

rating_star_blank.png

rating_star_blank.png

301 ms

Sheet-s.png

Sheet-s.png

212 ms

Sheet-h.png

Sheet-h.png

213 ms

Sheet-v.png

Sheet-v.png

232 ms

Sheet-c.png

Sheet-c.png

307 ms

l2db.jpg

l2db.jpg

422 ms

nav.png

nav.png

309 ms

MenuItem.png

MenuItem.png

305 ms

spacer.gif

spacer.gif

309 ms

subitem-bg.png

subitem-bg.png

323 ms

Block-s.png

Block-s.png

421 ms

Block-h.png

Block-h.png

421 ms

Block-v.png

Block-v.png

422 ms

ca-pub-9181458701164493.js

ca-pub-9181458701164493.js

113 ms

zrt_lookup.html

zrt_lookup.html

178 ms

show_ads_impl.js

show_ads_impl.js

108 ms

__utm.gif

__utm.gif

41 ms

banners.cgi

banners.cgi

210 ms

Post-s.png

Post-s.png

344 ms

Post-h.png

Post-h.png

374 ms

Post-v.png

Post-v.png

471 ms

Button.png

Button.png

469 ms

PostBullets.png

PostBullets.png

468 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

127 ms

quant.js

quant.js

99 ms

Footer.png

Footer.png

446 ms

searchTrack.php

searchTrack.php

143 ms

show.js

show.js

149 ms

ads

ads

49 ms

osd.js

osd.js

18 ms

pixel;r=682710835;a=p-2bkZ9O0FuBeVs;fpan=1;fpa=P0-696754212-1460129812027;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1460129812026;tzo=-180;ref=;url=http%3A%2F%2Fl2database.com%2F;ogl=

pixel;r=682710835;a=p-2bkZ9O0FuBeVs;fpan=1;fpa=P0-696754212-1460129812027;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1460129812026;tzo=-180;ref=;url=http%3A%2F%2Fl2database.com%2F;ogl=

25 ms

getkey.php

getkey.php

55 ms

flashfix.js

flashfix.js

132 ms

B110387.gif

B110387.gif

262 ms

search_banner.php

search_banner.php

185 ms

getkey.php

getkey.php

121 ms

adhere_left.png

adhere_left.png

73 ms

300lo.json

300lo.json

68 ms

all.js&version=v2.0

all.js&version=v2.0

436 ms

plusone.js

plusone.js

60 ms

widgets.js

widgets.js

86 ms

counter.270bdfcf33bafb0fc8fc.js

counter.270bdfcf33bafb0fc8fc.js

11 ms

MenuSeparator.png

MenuSeparator.png

133 ms

sh.953eb77977227bfd253ee158.html

sh.953eb77977227bfd253ee158.html

36 ms

shares.json

shares.json

63 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

77 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

75 ms

fastbutton

fastbutton

137 ms

datapair

datapair

66 ms

36 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

145 ms

question_icon.png

question_icon.png

80 ms

banner_frame.php

banner_frame.php

7451 ms

sendtext.php

sendtext.php

498 ms

sendtext.php

sendtext.php

480 ms

close_icon.png

close_icon.png

81 ms

postmessageRelay

postmessageRelay

55 ms

header_bg.png

header_bg.png

39 ms

footer_bg.png

footer_bg.png

45 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

28 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

30 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

44 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

23 ms

rpc:shindig_random.js

rpc:shindig_random.js

30 ms

tweet_button.fd774b599f565016d763dd860cb31c79.en-gb.html

tweet_button.fd774b599f565016d763dd860cb31c79.en-gb.html

44 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

jot

jot

134 ms

119 ms

xd_arbiter.php

xd_arbiter.php

308 ms

xd_arbiter.php

xd_arbiter.php

506 ms

like.php

like.php

148 ms

Sh_BYjerrZ8.js

Sh_BYjerrZ8.js

560 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

622 ms

ui.js

ui.js

59 ms

4-1442241153-881.png

4-1442241153-881.png

323 ms

ping

ping

77 ms

like.php

like.php

145 ms

SEO Factors

l2database.com SEO score

0

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise L2database.com can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it does not match the claimed English language. Our system also found out that L2database.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

l2database.com

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