Tools & Wizards About Us
lepeeto.cz screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lepeeto.cz

Lepeeto - samolepky na zeď, nálepky na zeď, bordury, tapety, nálepky na okno, nalepovací metry, tabule, obrazy, samolepící dekorace

Page Load Speed

3.8 sec in total

First Response

329 ms

Resources Loaded

3.3 sec

Page Rendered

177 ms

lepeeto.cz screenshot

About Website

Click here to check amazing Lepeeto content for Czech Republic. Otherwise, check out these important facts you probably never knew about lepeeto.cz

Lepeeto - samolepky na zeď, nálepky na zeď, bordury, tapety, nálepky na okno, nalepovací metry, tabule, obrazy

Visit lepeeto.cz

Key Findings

We analyzed Lepeeto.cz page load time and found that the first response time was 329 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

lepeeto.cz performance score

0

Network Requests Diagram

lepeeto.cz

329 ms

264 ms

main-shoptet_responsive.css.4f5641d3855d79c9542c.css

759 ms

jquery-1.11.3.min.js

668 ms

jquery-migrate-1.4.1.min.js

566 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lepeeto.cz, 46% (22 requests) were made to Cdn.myshoptet.com and 21% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (816 ms) relates to the external source Cdn.myshoptet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.1 kB (49%)

Content Size

306.0 kB

After Optimization

154.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lepeeto.cz main page is 306.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 118.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 62.8 kB

  • Original 81.9 kB
  • After minification 75.2 kB
  • After compression 19.1 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 62.8 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 25 B

  • Original 105.5 kB
  • After minification 105.5 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. Lepeeto images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 88.3 kB

  • Original 118.6 kB
  • After minification 118.6 kB
  • After compression 30.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 88.3 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (69%)

Requests Now

32

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lepeeto.cz

lepeeto.cz

329 ms

264 ms

main-shoptet_responsive.css.4f5641d3855d79c9542c.css

main-shoptet_responsive.css.4f5641d3855d79c9542c.css

759 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

668 ms

jquery-migrate-1.4.1.min.js

jquery-migrate-1.4.1.min.js

566 ms

jquery-ui-1.8.24.min.js

jquery-ui-1.8.24.min.js

793 ms

main-shoptet_responsive.js.22c2210b5e53c0367650.js

main-shoptet_responsive.js.22c2210b5e53c0367650.js

677 ms

swiper.js

swiper.js

816 ms

uc.js

uc.js

32 ms

sdk.js

sdk.js

24 ms

css

css

42 ms

css

css

59 ms

webfont.js

webfont.js

59 ms

tango.png

tango.png

217 ms

loader3.gif

loader3.gif

115 ms

logo.svg

logo.svg

114 ms

ico-facebook.svg

ico-facebook.svg

112 ms

ico-x.svg

ico-x.svg

113 ms

ico-instagram.svg

ico-instagram.svg

114 ms

ico-youtube.svg

ico-youtube.svg

211 ms

ico-linkedin.svg

ico-linkedin.svg

212 ms

ico-hearth.png

ico-hearth.png

210 ms

logo.c72bcb64ff5a88a9531c.svg

logo.c72bcb64ff5a88a9531c.svg

209 ms

icon-login.637eb119fd3af9fa015c.svg

icon-login.637eb119fd3af9fa015c.svg

207 ms

homeIcon.cc984a52810c8d16c72e.png

homeIcon.cc984a52810c8d16c72e.png

305 ms

menuExpandBg.00914778df36bddd4f16.gif

menuExpandBg.00914778df36bddd4f16.gif

306 ms

emailIcon.1db46a37b0eb6478f6f4.png

emailIcon.1db46a37b0eb6478f6f4.png

307 ms

sdk.js

sdk.js

25 ms

css

css

23 ms

iconFont.css

iconFont.css

104 ms

shoptet-hel.css

shoptet-hel.css

211 ms

li.png

li.png

274 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

56 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr.ttf

60 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

65 ms

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhcMWkDtDM.ttf

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhcMWkDtDM.ttf

70 ms

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWkDtDM.ttf

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWkDtDM.ttf

68 ms

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhycKkDtDM.ttf

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhycKkDtDM.ttf

70 ms

61 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

7 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

8 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

4 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

8 ms

HelveticaNeue.woff

HelveticaNeue.woff

414 ms

HelveticaNeue-UltraLight.woff

HelveticaNeue-UltraLight.woff

446 ms

HelveticaNeue-Bold.woff

HelveticaNeue-Bold.woff

725 ms

icomoon.ttf

icomoon.ttf

314 ms

print.css

print.css

108 ms

SEO Factors

lepeeto.cz SEO score

0

Language and Encoding

  • Language Detected

    CS

  • Language Claimed

    CS

  • Encoding

    UTF-8

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

lepeeto.cz

Open Graph data is detected on the main page of Lepeeto. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: