2.9 sec in total
861 ms
1.9 sec
130 ms
Visit limeo.de now to see the best up-to-date Limeo content and also check out these interesting facts you probably never knew about limeo.de
das limonenhaltige Suchverzeichnis
Visit limeo.deWe analyzed Limeo.de page load time and found that the first response time was 861 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
limeo.de performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value1.1 s
100/100
25%
Value2.9 s
95/100
10%
Value1,700 ms
11/100
30%
Value0.197
62/100
15%
Value4.3 s
84/100
10%
861 ms
650 ms
557 ms
294 ms
226 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 76% of them (42 requests) were addressed to the original Limeo.de, 7% (4 requests) were made to Impde.tradedoubler.com and 4% (2 requests) were made to Banners.webmasterplan.com. The less responsive or slowest element that took the longest time to load (861 ms) belongs to the original domain Limeo.de.
Page size can be reduced by 48.9 kB (62%)
79.2 kB
30.3 kB
In fact, the total size of Limeo.de main page is 79.2 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. Only 5% of websites need less resources to load. HTML takes 44.9 kB which makes up the majority of the site volume.
Potential reduce by 39.6 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 39.6 kB or 88% of the original size.
Potential reduce by 316 B
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. Limeo images are well optimized though.
Potential reduce by 2.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 2.6 kB or 76% of the original size.
Potential reduce by 6.4 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. Limeo.de needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 89% of the original size.
Number of requests can be reduced by 38 (76%)
50
12
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Limeo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
limeo.de
861 ms
style.css
650 ms
head.js
557 ms
tools.php
294 ms
pf2
226 ms
view.asp
220 ms
view.asp
248 ms
topback.jpg
203 ms
spacer.gif
105 ms
head1.gif
197 ms
head4.gif
202 ms
head6.gif
201 ms
headlogo.gif
203 ms
head7.gif
206 ms
headiag.gif
293 ms
shoptop.gif
301 ms
headiag2.gif
301 ms
tippstop.gif
302 ms
kltop.gif
302 ms
guenstigtop.gif
308 ms
geldvtop.gif
390 ms
head2.gif
399 ms
form.gif
400 ms
trans.gif
402 ms
go.gif
400 ms
head5.gif
409 ms
head9.gif
487 ms
head3.gif
498 ms
topback2.jpg
502 ms
specwbig.gif
500 ms
btippwbig.gif
501 ms
3552053476.03.MZZZZZZZ.jpg
614 ms
mhaeder1.gif
583 ms
mheaderdiag.gif
597 ms
wesmini.gif
599 ms
t40smini.gif
598 ms
nesmini.gif
600 ms
mheader3.gif
680 ms
svwbig.gif
696 ms
mheader5.gif
698 ms
mheader2.gif
698 ms
mheader4.gif
699 ms
388552
15 ms
catline.gif
710 ms
cm
160 ms
388552
8 ms
imp
4 ms
inv.gif
30 ms
388552
3 ms
computerh.gif
680 ms
88x31.gif
24 ms
165 ms
masie.jpg
608 ms
sideheader.gif
607 ms
napo_logo_de_80x30.gif
242 ms
limeo.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
limeo.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
limeo.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
N/A
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Limeo.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 Limeo.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
limeo.de
Open Graph description is not detected on the main page of Limeo. 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: