Tools & Wizards About Us
testserver.ws screenshot

Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

testserver.ws

Testserver by REIKEM IT Systemhaus

Page Load Speed

1.4 sec in total

First Response

437 ms

Resources Loaded

875 ms

Page Rendered

105 ms

testserver.ws screenshot

About Website

Welcome to testserver.ws homepage info - get ready to check Testserver best content right away, or after learning these important things about testserver.ws

Visit testserver.ws

Key Findings

We analyzed Testserver.ws page load time and found that the first response time was 437 ms and then it took 980 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

testserver.ws performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.201

62/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

testserver.ws

437 ms

main.css

120 ms

logo_big_in.png

218 ms

logo_big_in_hover.png

313 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that all of those requests were addressed to Testserver.ws and no external sources were called. The less responsive or slowest element that took the longest time to load (437 ms) belongs to the original domain Testserver.ws.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.5 kB (16%)

Content Size

67.3 kB

After Optimization

56.7 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Testserver.ws main page is 67.3 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 5% of websites need less resources to load. Images take 55.6 kB which makes up the majority of the site volume.

HTML Optimization

-53%

Potential reduce by 443 B

  • Original 837 B
  • After minification 717 B
  • After compression 394 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 120 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 443 B or 53% of the original size.

Image Optimization

-2%

Potential reduce by 1.3 kB

  • Original 55.6 kB
  • After minification 54.3 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. Testserver images are well optimized though.

CSS Optimization

-81%

Potential reduce by 8.8 kB

  • Original 10.8 kB
  • After minification 8.9 kB
  • After compression 2.0 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. Testserver.ws needs all CSS files to be minified and compressed as it can save up to 8.8 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • Images
  • CSS

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

Network Requests Diagram

testserver.ws

testserver.ws

437 ms

main.css

main.css

120 ms

logo_big_in.png

logo_big_in.png

218 ms

logo_big_in_hover.png

logo_big_in_hover.png

313 ms

Accessibility Review

testserver.ws accessibility score

70

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

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

Links do not have a discernible name

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

testserver.ws 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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

testserver.ws SEO score

92

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

    N/A

  • Encoding

    N/A

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

testserver.ws

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