Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

testament.de

testament.de - Testament Resources and Information.

Page Load Speed

1.3 sec in total

First Response

425 ms

Resources Loaded

652 ms

Page Rendered

247 ms

testament.de screenshot

About Website

Welcome to testament.de homepage info - get ready to check Testament best content right away, or after learning these important things about testament.de

testament.de is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, testament.de has it all. We hope you find w...

Visit testament.de

Key Findings

We analyzed Testament.de page load time and found that the first response time was 425 ms and then it took 899 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

testament.de performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value2,500 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.151

76/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

testament.de

425 ms

caf.js

39 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 Testament.de, 50% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (425 ms) belongs to the original domain Testament.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.8 kB (23%)

Content Size

106.7 kB

After Optimization

81.9 kB

In fact, the total size of Testament.de main page is 106.7 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. Only 10% of websites need less resources to load. Javascripts take 74.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 24.8 kB

  • Original 32.6 kB
  • After minification 32.5 kB
  • After compression 7.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. 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 24.8 kB or 76% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 74.1 kB
  • After minification 74.1 kB
  • After compression 74.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.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Testament. According to our analytics all requests are already optimized.

Accessibility Review

testament.de accessibility score

63

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

testament.de best practices score

83

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

testament.de SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Testament.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Testament.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 Testament. 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: