4.5 sec in total
451 ms
3.9 sec
176 ms
Welcome to ewar.lt homepage info - get ready to check EWAR best content for Lithuania right away, or after learning these important things about ewar.lt
Check out the EWAR | LTVR community on Discord - hang out with 378 other members and enjoy free voice and text chat.
Visit ewar.ltWe analyzed Ewar.lt page load time and found that the first response time was 451 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ewar.lt performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value2.1 s
95/100
25%
Value2.8 s
96/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.1 s
99/100
10%
451 ms
544 ms
127 ms
261 ms
263 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 59% of them (71 requests) were addressed to the original Ewar.lt, 8% (10 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ewar.lt.
Page size can be reduced by 439.3 kB (30%)
1.5 MB
1.0 MB
In fact, the total size of Ewar.lt main page is 1.5 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 900.4 kB which makes up the majority of the site volume.
Potential reduce by 32.5 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 32.5 kB or 79% of the original size.
Potential reduce by 36.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. EWAR images are well optimized though.
Potential reduce by 315.3 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 315.3 kB or 67% of the original size.
Potential reduce by 55.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. Ewar.lt needs all CSS files to be minified and compressed as it can save up to 55.5 kB or 81% of the original size.
Number of requests can be reduced by 65 (56%)
117
52
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EWAR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
ewar.lt
451 ms
www.ewar.lt
544 ms
reset.css
127 ms
style.css
261 ms
superfish.css
263 ms
prettyPhoto.css
264 ms
jquery-ui-1.7.3.custom.css
259 ms
coin-slider-styles.css
261 ms
extra.css
383 ms
jqtransform.css
386 ms
blue.css
383 ms
vip_valdymas_02.css
385 ms
jquery-1.3.2.min.js
509 ms
jquery.cycle.all.js
383 ms
jquery.easing.js
505 ms
jqFancyTransitions.js
506 ms
coin-slider.js
505 ms
ui.core.min.js
507 ms
ui.tabs.min.js
507 ms
jquery.prettyPhoto.js
631 ms
superfish.js
630 ms
cufon-yui.js
631 ms
Delicious.font.js
890 ms
jquery.form.js
636 ms
jquery.jqtransform.js
636 ms
bluz.js
754 ms
facebook_box.js
753 ms
downloads_box.js
755 ms
vip_valdymas.js
757 ms
show_ads.js
6 ms
wtpQualitySigns.js
594 ms
epWidget.js
446 ms
epWidget.js
490 ms
EWar.LT-SAMP.png
249 ms
grizzlis_banner.gif
1069 ms
count.php
314 ms
home-bg.jpg
126 ms
logo.png
250 ms
nav-left.png
127 ms
nav-hover.png
128 ms
nav-top.png
127 ms
ajax-loader.gif
126 ms
lt.gif
252 ms
uk.gif
251 ms
ru.gif
253 ms
search_mini.png
381 ms
slider-holder.png
253 ms
10.jpg
621 ms
8.jpg
1416 ms
1.jpg
627 ms
news_1.jpg
380 ms
news_2.jpg
380 ms
news_4.jpg
510 ms
ewar_logo_2013_2.png
755 ms
social_9.png
507 ms
social_10.png
630 ms
social_11.png
631 ms
social_12.png
744 ms
social_13.png
752 ms
image.php
777 ms
%C4%8Cia_gali_b%C5%ABti_j%C5%ABs%C5%B3_reklama_468x60_2.gif
251 ms
%C4%8Cia_gali_b%C5%ABti_j%C5%ABs%C5%B3_reklama_468x60%20-%20Copy.gif
251 ms
ca-pub-2254816543915109.js
41 ms
zrt_lookup.html
40 ms
show_ads_impl.js
48 ms
iframe3.php
258 ms
countdown_timer.php
868 ms
remeliai2.png
866 ms
footer-bg.jpg
868 ms
analytics.js
6 ms
502
611 ms
server.php
1010 ms
collect
13 ms
ads
252 ms
osd.js
4 ms
ga.js
3 ms
__utm.gif
11 ms
8059545004881852637
37 ms
abg.js
39 ms
m_js_controller.js
50 ms
googlelogo_color_112x36dp.png
37 ms
s
27 ms
x_button_blue2.png
26 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
2 ms
icon_lt.png
119 ms
all.js
37 ms
widget.css
420 ms
counter-strike_1_6_x40.png
125 ms
nav-right.png
322 ms
facebook_button1.png
344 ms
slider-anchor.png
378 ms
skype_blue_x40.png
127 ms
samp_x40.png
127 ms
likebox.php
142 ms
37 ms
xd_arbiter.php
27 ms
xd_arbiter.php
32 ms
roNeOY-tz5Y.css
54 ms
UHhaxo8Cs3k.css
60 ms
_rx8naC75Dy.js
69 ms
x5F9OMjKyLw.js
80 ms
ICDbTSzjQEg.js
58 ms
TTCre3391I0.js
54 ms
digital_grey_06.png
247 ms
digital_red_06.png
244 ms
1619452_818171174919492_7640920328813839417_n.jpg
36 ms
1098307_517906798279266_1381244405_n.png
14 ms
10917069_869862256406174_4003213152817423967_n.jpg
15 ms
12274238_928717267220581_6536904048164977764_n.jpg
18 ms
1379841_10150004552801901_469209496895221757_n.jpg
15 ms
12508810_576464039189299_7325735990060354468_n.jpg
15 ms
12243457_1230111053682422_5815251281289695883_n.jpg
16 ms
12795342_222513161434810_834982078208926463_n.jpg
17 ms
wL6VQj7Ab77.png
11 ms
s7jcwEQH7Sx.png
6 ms
I6-MnjEovm5.js
3 ms
vlXaquuXMrr.js
5 ms
style.css
127 ms
server.php
964 ms
activeview
14 ms
ewar.lt 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.
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
ewar.lt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
ewar.lt SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ewar.lt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ewar.lt 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.
ewar.lt
Open Graph description is not detected on the main page of EWAR. 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: