Tools & Wizards About Us
leielei.info screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

leielei.info

Lei e Lei | Immagini, video, recensioni e date dello spettacolo di Giampiero Cicciò

Page Load Speed

4.4 sec in total

First Response

323 ms

Resources Loaded

4 sec

Page Rendered

138 ms

leielei.info screenshot

About Website

Visit leielei.info now to see the best up-to-date Lei E content for Italy and also check out these interesting facts you probably never knew about leielei.info

Immagini, video, recensioni e date dello spettacolo di Giampiero Cicciò

Visit leielei.info

Key Findings

We analyzed Leielei.info page load time and found that the first response time was 323 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.

Performance Metrics

leielei.info performance score

0

Network Requests Diagram

leielei.info

323 ms

www.leielei.info

1405 ms

wp-emoji-release.min.js

234 ms

advanced-responsive-video-embedder-public.css

230 ms

custom_eventory_css.css

235 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 78% of them (59 requests) were addressed to the original Leielei.info, 11% (8 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Leielei.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (74%)

Content Size

1.7 MB

After Optimization

448.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Leielei.info main page is 1.7 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. CSS take 788.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 18.1 kB

  • Original 22.4 kB
  • After minification 19.3 kB
  • After compression 4.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 3.1 kB, which is 14% 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 18.1 kB or 81% of the original size.

Image Optimization

-15%

Potential reduce by 24.4 kB

  • Original 168.2 kB
  • After minification 143.8 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. Obviously, Lei E needs image optimization as it can save up to 24.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 543.1 kB

  • Original 723.7 kB
  • After minification 584.5 kB
  • After compression 180.6 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 543.1 kB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 668.4 kB

  • Original 788.0 kB
  • After minification 682.3 kB
  • After compression 119.6 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. Leielei.info needs all CSS files to be minified and compressed as it can save up to 668.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (90%)

Requests Now

62

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lei E. 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 31 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

leielei.info

leielei.info

323 ms

www.leielei.info

www.leielei.info

1405 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

234 ms

advanced-responsive-video-embedder-public.css

advanced-responsive-video-embedder-public.css

230 ms

custom_eventory_css.css

custom_eventory_css.css

235 ms

style.css

style.css

232 ms

bootstrap.css

bootstrap.css

346 ms

bootstrap-responsive.css

bootstrap-responsive.css

234 ms

css

css

26 ms

css

css

38 ms

font-awesome.min.css

font-awesome.min.css

353 ms

tzportfolio.css

tzportfolio.css

336 ms

template.css

template.css

442 ms

megamenu.css

megamenu.css

339 ms

megamenu-responsive.css

megamenu-responsive.css

337 ms

megamenu2.css

megamenu2.css

463 ms

megamenu-responsive2.css

megamenu-responsive2.css

462 ms

off-canvas.css

off-canvas.css

465 ms

owl.carousel.css

owl.carousel.css

466 ms

countdown.css

countdown.css

467 ms

settings.css

settings.css

550 ms

jplayer.blue.flag.css

jplayer.blue.flag.css

557 ms

custom_menu.css

custom_menu.css

554 ms

eventory.css

eventory.css

558 ms

footer.css

footer.css

560 ms

perfect-scrollbar.css

perfect-scrollbar.css

561 ms

custom-sidebar.css

custom-sidebar.css

659 ms

shortcode.css

shortcode.css

660 ms

event-responsive.css

event-responsive.css

662 ms

p_event.css

p_event.css

666 ms

blog.css

blog.css

665 ms

flexslider.css

flexslider.css

668 ms

jquery.js

jquery.js

805 ms

jquery-migrate.min.js

jquery-migrate.min.js

693 ms

Advanced_lazyload.js

Advanced_lazyload.js

694 ms

css

css

66 ms

bootstrap.js

bootstrap.js

696 ms

jquery-migrate.min.js

jquery-migrate.min.js

702 ms

off-canvas.js

off-canvas.js

701 ms

menu.js

menu.js

800 ms

page.js

page.js

774 ms

jquery.parallax-1.1.3.js

jquery.parallax-1.1.3.js

705 ms

jquery.localscroll-1.2.7-min.js

jquery.localscroll-1.2.7-min.js

701 ms

jquery.ui.totop.js

jquery.ui.totop.js

700 ms

resizeimage.js

resizeimage.js

762 ms

tz_eventory.js

tz_eventory.js

761 ms

jquery.simplyscroll.min.js

jquery.simplyscroll.min.js

654 ms

jquery.jplayer.js

jquery.jplayer.js

767 ms

jplayer.playlist.js

jplayer.playlist.js

662 ms

jquery.themepunch.showbizpro.min.js

jquery.themepunch.showbizpro.min.js

758 ms

owl.carousel.js

owl.carousel.js

756 ms

countdown.js

countdown.js

649 ms

eventory.js

eventory.js

644 ms

perfect-scrollbar.js

perfect-scrollbar.js

710 ms

wp-embed.min.js

wp-embed.min.js

752 ms

shade.gif

shade.gif

372 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

15 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

23 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

25 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

503 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

630 ms

-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf

-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf

33 ms

bIcY3_3JNqUVRAQQRNVteQ.ttf

bIcY3_3JNqUVRAQQRNVteQ.ttf

41 ms

JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf

JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf

35 ms

sEjAbKUh0jM

sEjAbKUh0jM

102 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

26 ms

www-embed-player.js

www-embed-player.js

49 ms

base.js

base.js

82 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

41 ms

ad_status.js

ad_status.js

110 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

33 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

104 ms

lei-e-lei-4.png

lei-e-lei-4.png

124 ms

IMG_8915.jpg

IMG_8915.jpg

556 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

418 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

364 ms

SEO Factors

leielei.info SEO score

0

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

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

leielei.info

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