Access testo.de. Professionelle Messgeräte + Messsysteme des Weltmarktführers |

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value2,740 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.451

20/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

testo.de

357 ms

56 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Testo.de, 50% (1 request) were made to Testo.com. The less responsive or slowest element that took the longest time to load (357 ms) belongs to the original domain Testo.de.

Content Size

104.7 kB

After Optimization

101.2 kB

In fact, the total size of Testo.de main page is 104.7 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 83.6 kB which makes up the majority of the site volume.

HTML Optimization

-24%

Potential reduce by 38 B

Original 157 B
After minification 130 B
After compression 119 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. This page needs HTML code to be minified as it can gain 27 B, which is 17% 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 38 B or 24% of the original size.

Image Optimization

-4%

Potential reduce by 3.4 kB

Original 83.6 kB
After minification 80.2 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. Testo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

Original 21.0 kB
After minification 21.0 kB
After compression 20.9 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.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

DE
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Testo.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Testo.de main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

testo.de

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