Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

2.5 sec in total

First Response

651 ms

Resources Loaded

1.7 sec

Page Rendered

137 ms

paul-kroening.de screenshot

About Website

Click here to check amazing Paul Kroening content. Otherwise, check out these important facts you probably never knew about paul-kroening.de

Portfolio | Homepage

Visit paul-kroening.de

Key Findings

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

Performance Metrics

paul-kroening.de performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

paul-kroening.de

651 ms

css.php

371 ms

functions.js

127 ms

style.css

114 ms

body_bg.jpg

109 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 12.7 kB (19%)

Content Size

68.3 kB

After Optimization

55.6 kB

In fact, the total size of Paul-kroening.de main page is 68.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 10% of websites need less resources to load. Images take 54.7 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 4.4 kB

  • Original 6.6 kB
  • After minification 6.5 kB
  • After compression 2.2 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 67% of the original size.

Image Optimization

-12%

Potential reduce by 6.4 kB

  • Original 54.7 kB
  • After minification 48.4 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, Paul Kroening needs image optimization as it can save up to 6.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-33%

Potential reduce by 1.1 kB

  • Original 3.4 kB
  • After minification 3.4 kB
  • After compression 2.3 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 1.1 kB or 33% of the original size.

CSS Optimization

-21%

Potential reduce by 754 B

  • Original 3.6 kB
  • After minification 3.5 kB
  • After compression 2.8 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. Paul-kroening.de needs all CSS files to be minified and compressed as it can save up to 754 B or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (57%)

Requests Now

21

After Optimization

9

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Paul Kroening. 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.

Accessibility Review

paul-kroening.de accessibility score

71

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

Form elements do not have associated labels

Best Practices

paul-kroening.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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

paul-kroening.de SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

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