Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

geilos.de

geilos.de

Page Load Speed

1.2 sec in total

First Response

379 ms

Resources Loaded

710 ms

Page Rendered

84 ms

geilos.de screenshot

About Website

Welcome to geilos.de homepage info - get ready to check Geilos best content right away, or after learning these important things about geilos.de

This domain may be for sale!

Visit geilos.de

Key Findings

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

Performance Metrics

geilos.de performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

geilos.de

379 ms

saledefault.css

19 ms

style.css

21 ms

skenzo.css

22 ms

sale_form.js

199 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 14% of them (1 request) were addressed to the original Geilos.de, 57% (4 requests) were made to D32ffatx74qnju.cloudfront.net and 14% (1 request) were made to Parkingcrew.net. The less responsive or slowest element that took the longest time to load (379 ms) belongs to the original domain Geilos.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.3 kB (65%)

Content Size

92.3 kB

After Optimization

32.0 kB

In fact, the total size of Geilos.de main page is 92.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. Javascripts take 84.5 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 899 B

  • Original 1.7 kB
  • After minification 1.6 kB
  • After compression 780 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 899 B or 54% of the original size.

JavaScript Optimization

-65%

Potential reduce by 54.7 kB

  • Original 84.5 kB
  • After minification 84.5 kB
  • After compression 29.8 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 54.7 kB or 65% of the original size.

CSS Optimization

-77%

Potential reduce by 4.7 kB

  • Original 6.1 kB
  • After minification 4.1 kB
  • After compression 1.4 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. Geilos.de needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 77% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

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

Accessibility Review

geilos.de accessibility score

68

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

geilos.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

geilos.de SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geilos.de 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), while the claimed language is English. Our system also found out that Geilos.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 Geilos. 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: