Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

steinhage.net

Mijn website: Christoffel Steinhage

Page Load Speed

1.4 sec in total

First Response

274 ms

Resources Loaded

783 ms

Page Rendered

316 ms

steinhage.net screenshot

About Website

Welcome to steinhage.net homepage info - get ready to check Steinhage best content for Netherlands right away, or after learning these important things about steinhage.net

Wie ik ben en wat ik doe.

Visit steinhage.net

Key Findings

We analyzed Steinhage.net page load time and found that the first response time was 274 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

steinhage.net performance score

0

Network Requests Diagram

steinhage.net

274 ms

left.php

94 ms

home.php

181 ms

fader.js

92 ms

showdate.js

178 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 6.6 kB (30%)

Content Size

21.7 kB

After Optimization

15.1 kB

In fact, the total size of Steinhage.net main page is 21.7 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 13.8 kB which makes up the majority of the site volume.

HTML Optimization

-48%

Potential reduce by 435 B

  • Original 907 B
  • After minification 865 B
  • After compression 472 B

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 435 B or 48% of the original size.

Image Optimization

-4%

Potential reduce by 524 B

  • Original 13.8 kB
  • After minification 13.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. Steinhage images are well optimized though.

JavaScript Optimization

-84%

Potential reduce by 4.6 kB

  • Original 5.4 kB
  • After minification 3.0 kB
  • After compression 844 B

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 4.6 kB or 84% of the original size.

CSS Optimization

-70%

Potential reduce by 1.1 kB

  • Original 1.6 kB
  • After minification 1.3 kB
  • After compression 476 B

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. Steinhage.net needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 70% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

10

After Optimization

10

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

Accessibility Review

steinhage.net accessibility score

33

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

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

Best Practices

steinhage.net 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

SEO Factors

steinhage.net SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Steinhage.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Steinhage.net main page’s claimed encoding is . 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 Steinhage. 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: