2.6 sec in total
305 ms
2 sec
276 ms
Welcome to lineage2warpgate.com homepage info - get ready to check Lineage 2 Warpgate best content for Brazil right away, or after learning these important things about lineage2warpgate.com
Free to Play Classic 2.3 Official platform! Pre Alpha: Now Live! Under Development! Huge Community! L2 Classic x3 - Missing old Lineage2? Join Now!
Visit lineage2warpgate.comWe analyzed Lineage2warpgate.com page load time and found that the first response time was 305 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
lineage2warpgate.com performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value5.3 s
21/100
25%
Value3.9 s
83/100
10%
Value270 ms
82/100
30%
Value0.002
100/100
15%
Value4.9 s
78/100
10%
305 ms
126 ms
393 ms
236 ms
236 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 33% of them (29 requests) were addressed to the original Lineage2warpgate.com, 23% (20 requests) were made to Static.xx.fbcdn.net and 14% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Lineage2warpgate.com.
Page size can be reduced by 612.8 kB (33%)
1.9 MB
1.3 MB
In fact, the total size of Lineage2warpgate.com main page is 1.9 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 27.2 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 8.4 kB, which is 24% 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 27.2 kB or 77% of the original size.
Potential reduce by 86.9 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 2 Warpgate images are well optimized though.
Potential reduce by 252.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 252.9 kB or 56% of the original size.
Potential reduce by 245.9 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. Lineage2warpgate.com needs all CSS files to be minified and compressed as it can save up to 245.9 kB or 84% of the original size.
Number of requests can be reduced by 43 (51%)
85
42
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lineage 2 Warpgate. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lineage2warpgate.com
305 ms
global.css
126 ms
jquery-1.7.2.min.js
393 ms
global.js
236 ms
modal.js
236 ms
jquery.min.js
74 ms
jquery.cookie.js
240 ms
adsbygoogle.js
7 ms
analytics.js
43 ms
atrk.js
116 ms
voteforus.png
442 ms
197 ms
background_top.jpg
924 ms
bg.png
197 ms
evening13042015.jpg
299 ms
warpgateneversleeps.jpg
349 ms
1.jpg
483 ms
classicwarpgatelogo.jpg
700 ms
all.js
105 ms
background_bot.jpg
416 ms
css_stripes1.png
1240 ms
css_stripes2.jpg
615 ms
background.png
506 ms
blackmtransparent.png
614 ms
zoomin.png
669 ms
linkid.js
62 ms
ca-pub-2801110974387982.js
239 ms
zrt_lookup.html
135 ms
show_ads_impl.js
141 ms
center_area_parte2.jpg
819 ms
center_area_parte1.jpg
794 ms
center_area_parte4.png
966 ms
banners_info_back.png
818 ms
separator.png
818 ms
center_area_parte3.jpg
917 ms
donations_img.jpg
915 ms
gallery_modal_horizontal_back1.png
918 ms
atrk.gif
193 ms
collect
101 ms
livechat_off.jpg
826 ms
Y9alhXLgimk
191 ms
likebox.php
336 ms
450 ms
xd_arbiter.php
103 ms
xd_arbiter.php
130 ms
ads
44 ms
fanclose.png
867 ms
test.png
25 ms
osd.js
24 ms
www-embed-player-vflQrT_sR.css
63 ms
www-embed-player.js
83 ms
base.js
169 ms
YQe3dSsMbL6.css
45 ms
ikPBP94Hp80.css
54 ms
MvZfQzy9-jz.css
149 ms
_rx8naC75Dy.js
183 ms
b94UUzHjapV.js
204 ms
0wM5s1Khldu.js
203 ms
TTCre3391I0.js
201 ms
ezSeJz80WmZ.js
203 ms
6kb4qPGfoPa.js
201 ms
Xq6IQFjERmT.js
262 ms
-YBL9NxImsH.js
261 ms
-AWXRi4rrMJ.js
261 ms
B9x7unvN8Hn.js
267 ms
DULOQLY-aiv.js
259 ms
VpVLc1dkyZp.js
259 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
265 ms
ad_status.js
266 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
288 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
314 ms
10517958_338454252975085_3698363927116401598_n.jpg
185 ms
12644942_579098295577345_2160661680425566497_n.jpg
266 ms
10354686_10150004552801856_220367501106153455_n.jpg
207 ms
600857_10201144350040086_160610127_n.jpg
209 ms
12540917_1114083455282496_1847238821529195627_n.jpg
211 ms
12705533_110575762663833_1267618346352890515_n.jpg
211 ms
1379760_356370147832886_1756239462_n.jpg
279 ms
12631532_1012161425511145_2238676845134616079_n.jpg
287 ms
10678735_750107725026352_3288150665724786191_n.jpg
217 ms
12376474_888371264610390_7003925418132098948_n.jpg
326 ms
10425474_685955971519554_656123030196800755_n.jpg
239 ms
12063791_103082750055099_3551962334428151321_n.jpg
258 ms
wL6VQj7Ab77.png
134 ms
s7jcwEQH7Sx.png
134 ms
355OzDqhgUf.png
29 ms
I6-MnjEovm5.js
10 ms
f6T91Deal_q.js
14 ms
lineage2warpgate.com accessibility score
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
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
lineage2warpgate.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
lineage2warpgate.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lineage2warpgate.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 Lineage2warpgate.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.
lineage2warpgate.com
Open Graph data is detected on the main page of Lineage 2 Warpgate. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: