Tools & Wizards About Us
werde-verrueckt.de screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

werde-verrueckt.de

Werde verrückt – wie du bekommst was du willst - Veit Lindau

Page Load Speed

6.5 sec in total

First Response

106 ms

Resources Loaded

3 sec

Page Rendered

3.5 sec

werde-verrueckt.de screenshot

About Website

Welcome to werde-verrueckt.de homepage info - get ready to check Werde Verrueckt best content for Germany right away, or after learning these important things about werde-verrueckt.de

Werde verrückt | Genug gewartet und gehofft? Nase voll von faulen Kompromissen? Was willst du wirklich-wirklich?

Visit werde-verrueckt.de

Key Findings

We analyzed Werde-verrueckt.de page load time and found that the first response time was 106 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

werde-verrueckt.de performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

werde-verrueckt.de

106 ms

1217 ms

classic-themes.min.css

204 ms

style-override.css

297 ms

style.css

298 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Werde-verrueckt.de, 95% (21 requests) were made to Veitlindau.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Veitlindau.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 458.2 kB (68%)

Content Size

674.5 kB

After Optimization

216.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Werde-verrueckt.de main page is 674.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. 45% of websites need less resources to load. HTML takes 505.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 435.5 kB

  • Original 505.8 kB
  • After minification 497.8 kB
  • After compression 70.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. 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.5 kB or 86% of the original size.

JavaScript Optimization

-13%

Potential reduce by 20.8 kB

  • Original 159.4 kB
  • After minification 159.4 kB
  • After compression 138.6 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 20.8 kB or 13% of the original size.

CSS Optimization

-21%

Potential reduce by 1.9 kB

  • Original 9.3 kB
  • After minification 9.3 kB
  • After compression 7.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. Werde-verrueckt.de needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (78%)

Requests Now

9

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

werde-verrueckt.de

werde-verrueckt.de

106 ms

1217 ms

classic-themes.min.css

classic-themes.min.css

204 ms

style-override.css

style-override.css

297 ms

style.css

style.css

298 ms

borlabs-cookie_1_de.css

borlabs-cookie_1_de.css

306 ms

borlabs-cookie-prioritize.min.js

borlabs-cookie-prioritize.min.js

309 ms

app.min.js

app.min.js

513 ms

jquery.min.js

jquery.min.js

332 ms

jquery-migrate.min.js

jquery-migrate.min.js

331 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

330 ms

Roboto-Light.woff

Roboto-Light.woff

204 ms

Roboto-Regular.woff

Roboto-Regular.woff

325 ms

Roboto-Medium.woff

Roboto-Medium.woff

325 ms

Roboto-Bold.woff

Roboto-Bold.woff

326 ms

work-sans-900.woff

work-sans-900.woff

105 ms

work-sans-700.woff

work-sans-700.woff

219 ms

work-sans-300.woff

work-sans-300.woff

282 ms

Roboto-LightItalic.woff

Roboto-LightItalic.woff

438 ms

Roboto-Italic.woff

Roboto-Italic.woff

438 ms

Roboto-MediumItalic.woff

Roboto-MediumItalic.woff

384 ms

Roboto-BoldItalic.woff

Roboto-BoldItalic.woff

401 ms

Accessibility Review

werde-verrueckt.de accessibility score

91

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

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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 valid value for its [lang] attribute.

Best Practices

werde-verrueckt.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

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

SEO Factors

werde-verrueckt.de SEO score

98

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 Werde-verrueckt.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 Werde-verrueckt.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

werde-verrueckt.de

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: