Tools & Wizards About Us
inlife.de screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

inlife.de

INlife Holding Gmbh

Page Load Speed

3.3 sec in total

First Response

351 ms

Resources Loaded

2.9 sec

Page Rendered

85 ms

inlife.de screenshot

About Website

Click here to check amazing INlife content for Germany. Otherwise, check out these important facts you probably never knew about inlife.de

INlife Holding Gmbh Jobs

Visit inlife.de

Key Findings

We analyzed Inlife.de page load time and found that the first response time was 351 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

inlife.de performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

inlife.de

351 ms

inlife.de

454 ms

www.inlife.de

321 ms

www.inlife.de

575 ms

style.css

222 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that all of those requests were addressed to Inlife.de and no external sources were called. The less responsive or slowest element that took the longest time to load (670 ms) belongs to the original domain Inlife.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.7 kB (22%)

Content Size

270.0 kB

After Optimization

210.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-94%

Potential reduce by 50.6 kB

  • Original 53.9 kB
  • After minification 9.9 kB
  • After compression 3.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 44.0 kB, which is 82% 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 50.6 kB or 94% of the original size.

Image Optimization

-2%

Potential reduce by 1.8 kB

  • Original 122.2 kB
  • After minification 120.3 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. INlife images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 6.3 kB

  • Original 86.7 kB
  • After minification 86.6 kB
  • After compression 80.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-14%

Potential reduce by 992 B

  • Original 7.2 kB
  • After minification 7.2 kB
  • After compression 6.2 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. Inlife.de needs all CSS files to be minified and compressed as it can save up to 992 B or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (64%)

Requests Now

28

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INlife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

inlife.de

inlife.de

351 ms

inlife.de

inlife.de

454 ms

www.inlife.de

www.inlife.de

321 ms

www.inlife.de

www.inlife.de

575 ms

style.css

style.css

222 ms

style_shop.css

style_shop.css

334 ms

jquery.min.js

jquery.min.js

449 ms

stepcarousel.js

stepcarousel.js

336 ms

stepcarousel_shop.js

stepcarousel_shop.js

336 ms

hide_failpics.js

hide_failpics.js

334 ms

noFocusBorder.js

noFocusBorder.js

335 ms

slide_style.css

slide_style.css

443 ms

slide_style_shop.css

slide_style_shop.css

444 ms

jquery.min2.js

jquery.min2.js

564 ms

jquery.easing.min.js

jquery.easing.min.js

445 ms

slides.min.jquery.js

slides.min.jquery.js

446 ms

modernizr-2.5.3.min.js

modernizr-2.5.3.min.js

553 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

554 ms

jquery.fancybox.js

jquery.fancybox.js

561 ms

jquery.fancybox.css

jquery.fancybox.css

557 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

559 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

664 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

665 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

668 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

670 ms

www.inlife.de

www.inlife.de

112 ms

www.inlife.de

www.inlife.de

119 ms

logo.png

logo.png

113 ms

dirkmail.png

dirkmail.png

114 ms

arrow-prev.gif

arrow-prev.gif

113 ms

arrow-next.gif

arrow-next.gif

113 ms

navi-hover-kurz.png

navi-hover-kurz.png

113 ms

slider_stromvergleich.jpg

slider_stromvergleich.jpg

438 ms

pagination.png

pagination.png

178 ms

Accessibility Review

inlife.de accessibility score

74

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

inlife.de best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

inlife.de SEO score

69

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inlife.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 Inlife.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.

Social Sharing Optimization

inlife.de

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