Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

lilaweiss.de

www.lilaweiss.de - alles rund um den VfL Osnabrück

Page Load Speed

2 sec in total

First Response

382 ms

Resources Loaded

1.5 sec

Page Rendered

154 ms

lilaweiss.de screenshot

About Website

Visit lilaweiss.de now to see the best up-to-date Lilaweiss content for Germany and also check out these interesting facts you probably never knew about lilaweiss.de

Visit lilaweiss.de

Key Findings

We analyzed Lilaweiss.de page load time and found that the first response time was 382 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

lilaweiss.de performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

lilaweiss.de

382 ms

vfl_style.css

205 ms

cm

194 ms

logo_rstnet_hosting_kl.jpg

506 ms

titelbild9.jpg

508 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 69% of them (9 requests) were addressed to the original Lilaweiss.de, 15% (2 requests) were made to Ecx.images-amazon.com and 8% (1 request) were made to Rcm-de.amazon.de. The less responsive or slowest element that took the longest time to load (907 ms) belongs to the original domain Lilaweiss.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 31.8 kB (11%)

Content Size

281.3 kB

After Optimization

249.5 kB

In fact, the total size of Lilaweiss.de main page is 281.3 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. Images take 266.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 4.4 kB

  • Original 6.2 kB
  • After minification 6.2 kB
  • After compression 1.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. 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 4.4 kB or 71% of the original size.

Image Optimization

-7%

Potential reduce by 19.9 kB

  • Original 266.5 kB
  • After minification 246.6 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. Lilaweiss images are well optimized though.

CSS Optimization

-87%

Potential reduce by 7.4 kB

  • Original 8.5 kB
  • After minification 6.6 kB
  • After compression 1.1 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. Lilaweiss.de needs all CSS files to be minified and compressed as it can save up to 7.4 kB or 87% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

12

After Optimization

12

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lilaweiss. According to our analytics all requests are already optimized.

Accessibility Review

lilaweiss.de accessibility score

68

Accessibility Issues

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

Best Practices

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

lilaweiss.de SEO score

58

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilaweiss.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lilaweiss.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

Open Graph description is not detected on the main page of Lilaweiss. 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: