6.5 sec in total
639 ms
5.8 sec
136 ms
Welcome to liliput.de homepage info - get ready to check Liliput best content for Germany right away, or after learning these important things about liliput.de
LILIPUT_Neuheiten_2024cDownload Liliput_Katalog_2023_72dpiDownload
Visit liliput.deWe analyzed Liliput.de page load time and found that the first response time was 639 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.
liliput.de performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value5.1 s
25/100
25%
Value6.7 s
36/100
10%
Value500 ms
58/100
30%
Value0
100/100
15%
Value9.4 s
31/100
10%
639 ms
172 ms
261 ms
176 ms
178 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 83% of them (50 requests) were addressed to the original Liliput.de, 7% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Liliput.de.
Page size can be reduced by 820.9 kB (30%)
2.7 MB
1.9 MB
In fact, the total size of Liliput.de main page is 2.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. 40% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 20.0 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 20.0 kB or 76% of the original size.
Potential reduce by 97.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. Liliput images are well optimized though.
Potential reduce by 619.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 619.1 kB or 68% of the original size.
Potential reduce by 84.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. Liliput.de needs all CSS files to be minified and compressed as it can save up to 84.6 kB or 83% of the original size.
Number of requests can be reduced by 27 (50%)
54
27
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Liliput. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
639 ms
reset.css
172 ms
template.css
261 ms
menu.css
176 ms
form.css
178 ms
slider.css
183 ms
custom.css
184 ms
jQuery.min.js
601 ms
jquery.socialshareprivacy.min.js
352 ms
template.js
355 ms
migursearch.css
356 ms
widgetkit-da53b7d2.css
453 ms
template.css
429 ms
mootools-core.js
782 ms
core.js
530 ms
jquery.min.js
14 ms
k2.js
531 ms
caption.js
620 ms
mootools-more.js
1181 ms
migursearch_en-GB.min.js
708 ms
jquery.js
978 ms
widgetkit-39833857.js
865 ms
webfont.js
7 ms
css
25 ms
YDAoLskQQ5MOAgvHUQCcLRTHiN2BPBirwIkMLKUspj4.woff
31 ms
We_iSDqttE3etzfdfhuPRVMR8FhBa8rkfAKaPBwAU3s.woff
49 ms
We_iSDqttE3etzfdfhuPRYa6iXjgqaxY3DU3RqApPOI.woff
36 ms
We_iSDqttE3etzfdfhuPRWwXwFHHZlCwprwJOQ-Se7k.woff
37 ms
lightbox.js
232 ms
mediaelement-and-player.js
443 ms
spotlight.js
237 ms
page_bg.png
227 ms
logo_bachmann_liliput.png
228 ms
menu_trenner.png
228 ms
menu_arrow_1.png
347 ms
de.gif
349 ms
en.gif
352 ms
L133152_Banner.jpg
732 ms
l_liliput.gif
517 ms
l_spectrum.gif
527 ms
l_china.gif
522 ms
l_branchline.gif
588 ms
l_graham.gif
611 ms
l_woodland.gif
691 ms
l_scenecraft.gif
695 ms
limitierte_messewagen_arial.jpg
967 ms
LINT_27.gif
1126 ms
fachhandel.jpg
782 ms
wechselstrom_home.jpg
951 ms
footer_anchor.png
872 ms
1337002299_facebook.png
914 ms
Google-Plus-Share-Button.png
1220 ms
Twitter.jpg
1042 ms
ga.js
143 ms
,
68 ms
slideshow.js
1003 ms
__utm.gif
23 ms
header_HP_Banner_133154.jpg
596 ms
L132052.jpg
550 ms
401 ms
liliput.de accessibility score
liliput.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
liliput.de SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liliput.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Liliput.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.
liliput.de
Open Graph data is detected on the main page of Liliput. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: