Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

poison-bikes.de

Poison-Bikes - MEIN UNIKAT

Page Load Speed

2.7 sec in total

First Response

376 ms

Resources Loaded

2.2 sec

Page Rendered

140 ms

poison-bikes.de screenshot

About Website

Welcome to poison-bikes.de homepage info - get ready to check Poison Bikes best content for Germany right away, or after learning these important things about poison-bikes.de

Konfigurier dir dein eigenes E-Bike, Gravel oder Trekking Bike nach deinen Vorstellungen!

Visit poison-bikes.de

Key Findings

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

Performance Metrics

poison-bikes.de performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

92/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value5.8 s

66/100

10%

Network Requests Diagram

poison-bikes.de

376 ms

www.poison-bikes.de

607 ms

cc_core.js

104 ms

inhalt.css

206 ms

general.js

307 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 42.3 kB (52%)

Content Size

81.5 kB

After Optimization

39.2 kB

In fact, the total size of Poison-bikes.de main page is 81.5 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. 25% of websites need less resources to load. HTML takes 45.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 36.0 kB

  • Original 45.7 kB
  • After minification 44.7 kB
  • After compression 9.7 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 36.0 kB or 79% of the original size.

JavaScript Optimization

-18%

Potential reduce by 6.3 kB

  • Original 35.8 kB
  • After minification 35.8 kB
  • After compression 29.5 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 6.3 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (28%)

Requests Now

18

After Optimization

13

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

Accessibility Review

poison-bikes.de accessibility score

92

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.

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

Links do not have a discernible name

Best Practices

poison-bikes.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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

poison-bikes.de SEO score

90

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

High

Tap targets are not sized appropriately

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 Poison-bikes.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 Poison-bikes.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 Poison Bikes. 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: