Tools & Wizards About Us
versus.lt screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

versus.lt

Suspended Domain

Page Load Speed

6.3 sec in total

First Response

672 ms

Resources Loaded

5.3 sec

Page Rendered

260 ms

versus.lt screenshot

About Website

Visit versus.lt now to see the best up-to-date Versus content and also check out these interesting facts you probably never knew about versus.lt

„Versus aureus“ – knygos, kurias verta skaityti!

Visit versus.lt

Key Findings

We analyzed Versus.lt page load time and found that the first response time was 672 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

versus.lt performance score

0

Network Requests Diagram

naujos-knygos

672 ms

jquery.min.js

248 ms

jquery.form.js

229 ms

main.js

226 ms

jquery.cookie.js

234 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 88% of them (50 requests) were addressed to the original Versus.lt, 4% (2 requests) were made to Facebook.com and 4% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Versus.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 303.9 kB (28%)

Content Size

1.1 MB

After Optimization

794.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Versus.lt main page is 1.1 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. 45% of websites need less resources to load. Images take 773.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 48.6 kB

  • Original 58.4 kB
  • After minification 49.4 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 9.0 kB, which is 15% 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 48.6 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 56.5 kB

  • Original 773.1 kB
  • After minification 716.6 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. Versus images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 169.0 kB

  • Original 230.3 kB
  • After minification 182.6 kB
  • After compression 61.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 169.0 kB or 73% of the original size.

CSS Optimization

-81%

Potential reduce by 29.9 kB

  • Original 36.9 kB
  • After minification 31.7 kB
  • After compression 7.0 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. Versus.lt needs all CSS files to be minified and compressed as it can save up to 29.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (36%)

Requests Now

56

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

naujos-knygos

naujos-knygos

672 ms

jquery.min.js

jquery.min.js

248 ms

jquery.form.js

jquery.form.js

229 ms

main.js

main.js

226 ms

jquery.cookie.js

jquery.cookie.js

234 ms

toolbox.flashembed.min.js

toolbox.flashembed.min.js

232 ms

layout.css

layout.css

236 ms

main.css

main.css

348 ms

ie6blocker.js

ie6blocker.js

352 ms

jquery.boxy.js

jquery.boxy.js

354 ms

boxy.css

boxy.css

357 ms

jquery.corner.js

jquery.corner.js

361 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

459 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

462 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

464 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

460 ms

jquery.mousewheel.js

jquery.mousewheel.js

469 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

476 ms

custom-form-elements.js

custom-form-elements.js

571 ms

nivo-slider.css

nivo-slider.css

571 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

576 ms

body.png

body.png

118 ms

logo.png

logo.png

113 ms

search.png

search.png

119 ms

81.lt.html

81.lt.html

623 ms

84.lt.html

84.lt.html

1728 ms

80.lt.html

80.lt.html

1217 ms

83.lt.html

83.lt.html

1993 ms

82.lt.html

82.lt.html

2367 ms

6.lt.html

6.lt.html

2149 ms

6.lt.html

6.lt.html

2301 ms

6.lt.html

6.lt.html

2356 ms

6.lt.html

6.lt.html

2309 ms

6.lt.html

6.lt.html

2446 ms

6.lt.html

6.lt.html

2478 ms

6.lt.html

6.lt.html

2578 ms

6.lt.html

6.lt.html

2478 ms

6.lt.html

6.lt.html

2664 ms

6.lt.html

6.lt.html

2531 ms

6.lt.html

6.lt.html

2617 ms

6.lt.html

6.lt.html

2770 ms

d-europa-e-virselis-00000002jpg

d-europa-e-virselis-00000002jpg

2809 ms

mokejimai.png

mokejimai.png

2648 ms

all.js

all.js

270 ms

header.png

header.png

2797 ms

li_o2.png

li_o2.png

2714 ms

li.png

li.png

2749 ms

tocart.png

tocart.png

2745 ms

cart.png

cart.png

2806 ms

137 ms

xd_arbiter.php

xd_arbiter.php

213 ms

xd_arbiter.php

xd_arbiter.php

420 ms

81.lt.html

81.lt.html

402 ms

arrows.png

arrows.png

115 ms

like.php

like.php

93 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

484 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

546 ms

SEO Factors

versus.lt SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

Social Sharing Optimization

versus.lt

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