Tools & Wizards About Us
libase.de screenshot

Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 38

    SEO

    Google-friendlier than
    18% of websites

libase.de

Fehlermeldung - LIbase - Internetportal für Laktoseintoleranz und NMU

Page Load Speed

5.3 sec in total

First Response

319 ms

Resources Loaded

4.6 sec

Page Rendered

387 ms

libase.de screenshot

About Website

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.de

Key Findings

We 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.

Performance Metrics

libase.de performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

96/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.144

78/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

libase.de

319 ms

3224 ms

burningBoard.css

207 ms

portal.css

213 ms

style-3.css

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 Optimization Overview & Recommendations

Page size can be reduced by 444.1 kB (80%)

Content Size

558.0 kB

After Optimization

113.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-93%

Potential reduce by 325.3 kB

  • Original 349.1 kB
  • After minification 212.1 kB
  • After compression 23.9 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.

Image Optimization

-20%

Potential reduce by 17.2 kB

  • Original 86.4 kB
  • After minification 69.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.

JavaScript Optimization

-84%

Potential reduce by 42.8 kB

  • Original 50.7 kB
  • After minification 27.8 kB
  • After compression 7.9 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.

CSS Optimization

-82%

Potential reduce by 58.7 kB

  • Original 71.8 kB
  • After minification 64.0 kB
  • After compression 13.0 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.

Requests Breakdown

Number of requests can be reduced by 36 (72%)

Requests Now

50

After Optimization

14

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

libase.de

libase.de

319 ms

3224 ms

burningBoard.css

burningBoard.css

207 ms

portal.css

portal.css

213 ms

style-3.css

style-3.css

320 ms

default.js

default.js

213 ms

PopupMenuList.class.js

PopupMenuList.class.js

215 ms

AjaxRequest.class.js

AjaxRequest.class.js

308 ms

Ml9pagepeel.class.js

Ml9pagepeel.class.js

317 ms

TransMenu.class.js

TransMenu.class.js

380 ms

Poll.class.js

Poll.class.js

264 ms

monthlyCalendarBox.css

monthlyCalendarBox.css

160 ms

klein.png

klein.png

116 ms

dateS.png

dateS.png

115 ms

loginS.png

loginS.png

116 ms

submitS.png

submitS.png

117 ms

registerS.png

registerS.png

117 ms

titel_logo_rechts.gif

titel_logo_rechts.gif

198 ms

leer-1-1.png

leer-1-1.png

411 ms

indexS.png

indexS.png

224 ms

portalL.png

portalL.png

223 ms

portal_infobox.jpg

portal_infobox.jpg

504 ms

chat_new.jpg

chat_new.jpg

223 ms

minusS.png

minusS.png

295 ms

pollM.png

pollM.png

317 ms

threadNewM.png

threadNewM.png

325 ms

goToFirstNewPostS.png

goToFirstNewPostS.png

317 ms

goToLastPostS.png

goToLastPostS.png

400 ms

threadNewImportantM.png

threadNewImportantM.png

422 ms

attachmentsS.png

attachmentsS.png

421 ms

threadNewImportantClosedM.png

threadNewImportantClosedM.png

423 ms

threadM.png

threadM.png

504 ms

threadImportantM.png

threadImportantM.png

508 ms

pollS.png

pollS.png

520 ms

mcbCalendarS.png

mcbCalendarS.png

525 ms

mcbAppointmentS.png

mcbAppointmentS.png

526 ms

mcbPreviousS.png

mcbPreviousS.png

605 ms

mcbNextS.png

mcbNextS.png

609 ms

loginOptionsS.png

loginOptionsS.png

601 ms

libase-titel_hintergrund.gif

libase-titel_hintergrund.gif

613 ms

searchHeadS.png

searchHeadS.png

620 ms

titel_logo_links.gif

titel_logo_links.gif

615 ms

searchHeadOptionsS.png

searchHeadOptionsS.png

689 ms

mainMenu.png

mainMenu.png

638 ms

spacer.png

spacer.png

611 ms

subMenuOff.gif

subMenuOff.gif

623 ms

snakeM.png

snakeM.png

632 ms

tttM.png

tttM.png

633 ms

infoM.png

infoM.png

710 ms

mcbDayB.png

mcbDayB.png

602 ms

mcbDayBA.png

mcbDayBA.png

605 ms

print.css

print.css

105 ms

Accessibility Review

libase.de accessibility score

55

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

libase.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

libase.de SEO score

38

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

High

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

High

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    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.

Social Sharing Optimization

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: