Tools & Wizards About Us
testando.de screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

testando.de

TESTANDO.de - Jetzt Restaurant - und Hoteltester werden!

Page Load Speed

4.5 sec in total

First Response

340 ms

Resources Loaded

4 sec

Page Rendered

208 ms

testando.de screenshot

About Website

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

TESTANDO testet Restaurants, Cafes, Bars und Hotels. Du bekommst bei jedem Test einen Teil Deiner Kosten erstattet. Jetzt anmelden und bis zu 75% sparen!

Visit testando.de

Key Findings

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

Performance Metrics

testando.de performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.19

65/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

testando.de

340 ms

www.testando.de

1177 ms

bootstrap.min.css

554 ms

styles.min.css

447 ms

modernizr.lib.min.js

333 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 79% of them (34 requests) were addressed to the original Testando.de, 7% (3 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Testando.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.2 kB (69%)

Content Size

476.9 kB

After Optimization

145.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Testando.de main page is 476.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. CSS take 174.5 kB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 77.6 kB

  • Original 82.3 kB
  • After minification 20.2 kB
  • After compression 4.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 62.2 kB, which is 75% 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 77.6 kB or 94% of the original size.

Image Optimization

-20%

Potential reduce by 10.3 kB

  • Original 52.9 kB
  • After minification 42.6 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. Obviously, TESTANDO needs image optimization as it can save up to 10.3 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 98.0 kB

  • Original 167.1 kB
  • After minification 166.9 kB
  • After compression 69.2 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 98.0 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 145.3 kB

  • Original 174.5 kB
  • After minification 174.4 kB
  • After compression 29.1 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. Testando.de needs all CSS files to be minified and compressed as it can save up to 145.3 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

testando.de

testando.de

340 ms

www.testando.de

www.testando.de

1177 ms

bootstrap.min.css

bootstrap.min.css

554 ms

styles.min.css

styles.min.css

447 ms

modernizr.lib.min.js

modernizr.lib.min.js

333 ms

jquery.min.js

jquery.min.js

694 ms

bootstrap.min.js

bootstrap.min.js

450 ms

tdo.min.js

tdo.min.js

339 ms

modernizr.js

modernizr.js

684 ms

index.js

index.js

718 ms

css

css

52 ms

testando.svg

testando.svg

330 ms

werde.png

werde.png

358 ms

muenchen.svgz

muenchen.svgz

585 ms

greyseparator.png

greyseparator.png

406 ms

greenseparator.png

greenseparator.png

444 ms

greenarrow.png

greenarrow.png

471 ms

pattern.png

pattern.png

661 ms

backsearch.jpg

backsearch.jpg

1331 ms

color.png

color.png

738 ms

button.png

button.png

779 ms

arrowright.png

arrowright.png

803 ms

icon1.png

icon1.png

907 ms

icon2.png

icon2.png

987 ms

icon3.png

icon3.png

1063 ms

icon4.png

icon4.png

1103 ms

icon5.png

icon5.png

1135 ms

shadow.png

shadow.png

1225 ms

footer_underline.png

footer_underline.png

1311 ms

footer_underline_large.png

footer_underline_large.png

1398 ms

twitter.png

twitter.png

1439 ms

facebook.png

facebook.png

1468 ms

pinterest-button.png

pinterest-button.png

1667 ms

munchen.png

munchen.png

1649 ms

analytics.js

analytics.js

45 ms

fbds.js

fbds.js

42 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

35 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

43 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

80 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1847 ms

118 ms

collect

collect

39 ms

21 ms

Accessibility Review

testando.de accessibility score

82

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

testando.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

Page has valid source maps

SEO Factors

testando.de SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

testando.de

Open Graph description is not detected on the main page of TESTANDO. 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: