Report Summary

  • 0

    Performance

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

Page Load Speed

2.8 sec in total

First Response

324 ms

Resources Loaded

2.3 sec

Page Rendered

178 ms

traumoasen.de screenshot

About Website

Click here to check amazing Traumoasen content. Otherwise, check out these important facts you probably never knew about traumoasen.de

Visit traumoasen.de

Key Findings

We analyzed Traumoasen.de page load time and found that the first response time was 324 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

traumoasen.de performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

traumoasen.de

324 ms

index.php

568 ms

frontend.css

187 ms

google_service.js

15 ms

google_ads.js

17 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Traumoasen.de, 33% (6 requests) were made to Geniesserinnen.de and 11% (2 requests) were made to Partner.googleadservices.com. The less responsive or slowest element that took the longest time to load (572 ms) relates to the external source Getprofitadz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.6 kB (17%)

Content Size

68.8 kB

After Optimization

57.2 kB

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

HTML Optimization

-46%

Potential reduce by 294 B

  • Original 644 B
  • After minification 643 B
  • After compression 350 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 294 B or 46% of the original size.

Image Optimization

-3%

Potential reduce by 1.2 kB

  • Original 38.2 kB
  • After minification 37.0 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. Traumoasen images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-79%

Potential reduce by 10.1 kB

  • Original 12.7 kB
  • After minification 8.5 kB
  • After compression 2.6 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. Traumoasen.de needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

15

After Optimization

10

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

traumoasen.de accessibility score

67

Accessibility Issues

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

traumoasen.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

High

Missing source maps for large first-party JavaScript

SEO Factors

traumoasen.de SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Traumoasen.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Traumoasen.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 Traumoasen. 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: