5.3 sec in total
319 ms
4.6 sec
387 ms
Visit libase.de now to see the best up-to-date LIbase content for Germany and also check out these interesting facts you probably never knew about libase.de
Deutschlands großes Internetportal für Laktoseintoleranz und Nahrungsmittelunverträglichkeiten mit grossem Forum, Live-Chat, Lebensmittellisten
Visit libase.deWe analyzed Libase.de page load time and found that the first response time was 319 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
libase.de performance score
name
value
score
weighting
Value1.4 s
96/100
10%
Value1.9 s
98/100
25%
Value2.0 s
99/100
10%
Value0 ms
100/100
30%
Value0.144
78/100
15%
Value1.4 s
100/100
10%
319 ms
3224 ms
207 ms
213 ms
320 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that all of those requests were addressed to Libase.de and no external sources were called. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Libase.de.
Page size can be reduced by 444.1 kB (80%)
558.0 kB
113.9 kB
In fact, the total size of Libase.de main page is 558.0 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. 15% of websites need less resources to load. HTML takes 349.1 kB which makes up the majority of the site volume.
Potential reduce by 325.3 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 137.0 kB, which is 39% 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 325.3 kB or 93% of the original size.
Potential reduce by 17.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, LIbase needs image optimization as it can save up to 17.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 42.8 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 42.8 kB or 84% of the original size.
Potential reduce by 58.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. Libase.de needs all CSS files to be minified and compressed as it can save up to 58.7 kB or 82% of the original size.
Number of requests can be reduced by 36 (72%)
50
14
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LIbase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
libase.de
319 ms
3224 ms
burningBoard.css
207 ms
portal.css
213 ms
style-3.css
320 ms
default.js
213 ms
PopupMenuList.class.js
215 ms
AjaxRequest.class.js
308 ms
Ml9pagepeel.class.js
317 ms
TransMenu.class.js
380 ms
Poll.class.js
264 ms
monthlyCalendarBox.css
160 ms
klein.png
116 ms
dateS.png
115 ms
loginS.png
116 ms
submitS.png
117 ms
registerS.png
117 ms
titel_logo_rechts.gif
198 ms
leer-1-1.png
411 ms
indexS.png
224 ms
portalL.png
223 ms
portal_infobox.jpg
504 ms
chat_new.jpg
223 ms
minusS.png
295 ms
pollM.png
317 ms
threadNewM.png
325 ms
goToFirstNewPostS.png
317 ms
goToLastPostS.png
400 ms
threadNewImportantM.png
422 ms
attachmentsS.png
421 ms
threadNewImportantClosedM.png
423 ms
threadM.png
504 ms
threadImportantM.png
508 ms
pollS.png
520 ms
mcbCalendarS.png
525 ms
mcbAppointmentS.png
526 ms
mcbPreviousS.png
605 ms
mcbNextS.png
609 ms
loginOptionsS.png
601 ms
libase-titel_hintergrund.gif
613 ms
searchHeadS.png
620 ms
titel_logo_links.gif
615 ms
searchHeadOptionsS.png
689 ms
mainMenu.png
638 ms
spacer.png
611 ms
subMenuOff.gif
623 ms
snakeM.png
632 ms
tttM.png
633 ms
infoM.png
710 ms
mcbDayB.png
602 ms
mcbDayBA.png
605 ms
print.css
105 ms
libase.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
<object> elements do not have alternate text
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
libase.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
libase.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Document uses plugins
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Libase.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Libase.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.
libase.de
Open Graph description is not detected on the main page of LIbase. 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: