9 sec in total
1.2 sec
7.6 sec
214 ms
Click here to check amazing Firelilly content. Otherwise, check out these important facts you probably never knew about firelilly.de
This website is for sale! firelilly.de is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, firelilly.de has ...
Visit firelilly.deWe analyzed Firelilly.de page load time and found that the first response time was 1.2 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
firelilly.de performance score
1235 ms
201 ms
301 ms
714 ms
215 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 91% of them (32 requests) were addressed to the original Firelilly.de, 6% (2 requests) were made to Stats.wordpress.com and 3% (1 request) were made to Pixel.wp.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Firelilly.de.
Page size can be reduced by 316.7 kB (39%)
802.1 kB
485.4 kB
In fact, the total size of Firelilly.de main page is 802.1 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. 25% of websites need less resources to load. Images take 496.4 kB which makes up the majority of the site volume.
Potential reduce by 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 1.5 kB, which is 12% 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 9.8 kB or 74% of the original size.
Potential reduce by 100.2 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, Firelilly needs image optimization as it can save up to 100.2 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 154.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 154.1 kB or 68% of the original size.
Potential reduce by 52.7 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. Firelilly.de needs all CSS files to be minified and compressed as it can save up to 52.7 kB or 82% of the original size.
Number of requests can be reduced by 15 (45%)
33
18
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Firelilly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.firelilly.de
1235 ms
language-selector.css
201 ms
style.css
301 ms
www.firelilly.de
714 ms
nggallery.css
215 ms
thickbox.css
231 ms
l10n.js
220 ms
jquery.js
619 ms
stepper.js
316 ms
jquery.cycle.all.min.js
439 ms
ngg.slideshow.min.js
338 ms
sitepress.js
405 ms
thickbox.js
332 ms
jquery.mystique.js
559 ms
www.firelilly.de
970 ms
e-201611.js
8 ms
e-201611.js
54 ms
color-grey.css
105 ms
bg.jpg
909 ms
header.jpg
407 ms
nav-arrow-down.png
109 ms
shadow.png
105 ms
nav.png
107 ms
nav-active.png
208 ms
nav-pointer.png
211 ms
main-right.jpg
212 ms
main-left.jpg
311 ms
intro-300x259.jpg
344 ms
icons.png
316 ms
piwik.js
119 ms
piwik.php
4192 ms
g.gif
35 ms
loadingAnimation.gif
106 ms
page-controls.png
105 ms
light-mask.png
207 ms
firelilly.de SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Firelilly.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Firelilly.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.
firelilly.de
Open Graph description is not detected on the main page of Firelilly. 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: