Tools & Wizards About Us
lillyberry.de screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lillyberry.de

Page Load Speed

4.6 sec in total

First Response

899 ms

Resources Loaded

2.8 sec

Page Rendered

900 ms

lillyberry.de screenshot

About Website

Click here to check amazing Lillyberry content. Otherwise, check out these important facts you probably never knew about lillyberry.de

Visit lillyberry.de

Key Findings

We analyzed Lillyberry.de page load time and found that the first response time was 899 ms and then it took 3.7 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

lillyberry.de performance score

0

Network Requests Diagram

www.lillyberry.de

899 ms

style.css

193 ms

tfg_style.css

195 ms

l10n.js

192 ms

jquery.js

416 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 79% of them (31 requests) were addressed to the original Lillyberry.de, 5% (2 requests) were made to Apis.google.com and 5% (2 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Lillyberry.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.8 kB (44%)

Content Size

446.5 kB

After Optimization

250.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lillyberry.de main page is 446.5 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. 50% of websites need less resources to load. Images take 165.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 86.8 kB

  • Original 111.6 kB
  • After minification 105.2 kB
  • After compression 24.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. 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 86.8 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 6.1 kB

  • Original 165.2 kB
  • After minification 159.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. Lillyberry images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 92.3 kB

  • Original 156.7 kB
  • After minification 156.7 kB
  • After compression 64.5 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 92.3 kB or 59% of the original size.

CSS Optimization

-82%

Potential reduce by 10.6 kB

  • Original 13.0 kB
  • After minification 10.3 kB
  • After compression 2.3 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. Lillyberry.de needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.lillyberry.de

www.lillyberry.de

899 ms

style.css

style.css

193 ms

tfg_style.css

tfg_style.css

195 ms

l10n.js

l10n.js

192 ms

jquery.js

jquery.js

416 ms

external-tracking.min.js

external-tracking.min.js

221 ms

widgets.js

widgets.js

6 ms

plusone.js

plusone.js

40 ms

pinit.js

pinit.js

103 ms

ga.js

ga.js

137 ms

rtpw-button4-200x92white.png

rtpw-button4-200x92white.png

171 ms

background.gif

background.gif

238 ms

header-left.gif

header-left.gif

164 ms

header-right.gif

header-right.gif

210 ms

header-inside-right.gif

header-inside-right.gif

168 ms

logo.gif

logo.gif

595 ms

subscribe.png

subscribe.png

375 ms

navigation.gif

navigation.gif

236 ms

feature-repeat.gif

feature-repeat.gif

679 ms

feature.gif

feature.gif

500 ms

feature.php

feature.php

443 ms

content.gif

content.gif

341 ms

content-left.gif

content-left.gif

441 ms

content-right.gif

content-right.gif

492 ms

content-top.gif

content-top.gif

733 ms

content-bottom.gif

content-bottom.gif

547 ms

divider.gif

divider.gif

604 ms

wikimedia-Philip-Scalia-266x300.jpg

wikimedia-Philip-Scalia-266x300.jpg

611 ms

wikipedia-Lionel-Allorge-300x213.jpg

wikipedia-Lionel-Allorge-300x213.jpg

652 ms

buch-er-ist-wieder-da-201x300.jpg

buch-er-ist-wieder-da-201x300.jpg

701 ms

Tina-Fey-by-wikimedia-Gage-Skidmore.jpg

Tina-Fey-by-wikimedia-Gage-Skidmore.jpg

714 ms

E-Book-by-wikimedia-Maximilian-Sch%C3%B6nherr.jpg

E-Book-by-wikimedia-Maximilian-Sch%C3%B6nherr.jpg

720 ms

sidebar-top.gif

sidebar-top.gif

757 ms

sidebar-bottom.gif

sidebar-bottom.gif

782 ms

footer.gif

footer.gif

1078 ms

zafon.gif

zafon.gif

829 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

88 ms

pinit_main.js

pinit_main.js

107 ms

__utm.gif

__utm.gif

36 ms

SEO Factors

lillyberry.de SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lillyberry.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Lillyberry.de 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

lillyberry.de

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