Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

tauschpaar.de

Tauschbude ...so tauscht man heute - Flohmarkt und Secondhand

Page Load Speed

3 sec in total

First Response

294 ms

Resources Loaded

2.5 sec

Page Rendered

209 ms

About Website

Visit tauschpaar.de now to see the best up-to-date Tauschpaar content and also check out these interesting facts you probably never knew about tauschpaar.de

Stellen Sie in unserer Tauschplattform Ihre Artikel kostenlos ein. Inserieren Sie neue und gebrauchte Artikel umsonst bei unserer Tauschbörse gegen Tauschbons

Visit tauschpaar.de

Key Findings

We analyzed Tauschpaar.de page load time and found that the first response time was 294 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

tauschpaar.de performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

tauschpaar.de

294 ms

tauschbude.php

1149 ms

css.css

106 ms

jquery-ui.css

9 ms

jquery.min.js

17 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 7% of them (1 request) were addressed to the original Tauschpaar.de, 57% (8 requests) were made to De.tauschbu.de and 21% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source De.tauschbu.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.9 kB (45%)

Content Size

133.9 kB

After Optimization

73.9 kB

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

HTML Optimization

-66%

Potential reduce by 3.5 kB

  • Original 5.2 kB
  • After minification 4.5 kB
  • After compression 1.8 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. This page needs HTML code to be minified as it can gain 749 B, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 3.5 kB or 66% of the original size.

Image Optimization

-1%

Potential reduce by 542 B

  • Original 55.5 kB
  • After minification 55.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. Tauschpaar images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 11.7 kB

  • Original 19.5 kB
  • After minification 19.3 kB
  • After compression 7.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 11.7 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 44.3 kB

  • Original 53.6 kB
  • After minification 45.2 kB
  • After compression 9.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. Tauschpaar.de needs all CSS files to be minified and compressed as it can save up to 44.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (25%)

Requests Now

12

After Optimization

9

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

Accessibility Review

tauschpaar.de accessibility score

100

Accessibility Issues

Best Practices

tauschpaar.de best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

tauschpaar.de SEO score

93

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tauschpaar.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 Tauschpaar.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 Tauschpaar. 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: