Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

220.lt

Pigu.lt - prekybos centras internete

Page Load Speed

6.3 sec in total

First Response

418 ms

Resources Loaded

4.7 sec

Page Rendered

1.2 sec

220.lt screenshot

About Website

Welcome to 220.lt homepage info - get ready to check 220 best content right away, or after learning these important things about 220.lt

Šimtai tūkstančių prekių internetinėje parduotuvėje pigu.lt: kvepalai, buitinė technika, baldai ir kt. Prekybos centras internete - viskas vienoje vietoje!

Visit 220.lt

Key Findings

We analyzed 220.lt page load time and found that the first response time was 418 ms and then it took 5.9 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

220.lt performance score

0

Network Requests Diagram

220.lt

418 ms

pigu.lt

1251 ms

combo-main.css

641 ms

combo-other.css

412 ms

font-awesome.min.css

419 ms

Our browser made a total of 158 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 220.lt, 64% (101 requests) were made to Lt2.pigugroup.eu and 6% (9 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Pigu.lt.

Page Optimization Overview & Recommendations

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

Content Size

3.3 MB

After Optimization

2.2 MB

In fact, the total size of 220.lt main page is 3.3 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 499.4 kB

  • Original 575.7 kB
  • After minification 477.4 kB
  • After compression 76.3 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 98.3 kB, which is 17% 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 499.4 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 31.7 kB

  • Original 1.9 MB
  • After minification 1.9 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. 220 images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 186.9 kB

  • Original 319.9 kB
  • After minification 297.2 kB
  • After compression 133.1 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 186.9 kB or 58% of the original size.

CSS Optimization

-82%

Potential reduce by 393.5 kB

  • Original 479.8 kB
  • After minification 479.5 kB
  • After compression 86.2 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. 220.lt needs all CSS files to be minified and compressed as it can save up to 393.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (32%)

Requests Now

152

After Optimization

103

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

SEO Factors

220.lt SEO score

0

Language and Encoding

  • Language Detected

    LT

  • Language Claimed

    LT

  • Encoding

    UTF-8

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

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