stw-thueringen.de Website Information

Daily Unique Visits: 1,052

Daily Page Views: 2,104

Income Per Day: $7

Estimated Value: $1,680

This website is located in Germany and is using following IP address 141.35.105.193. See the complete list of popular websites hosted in Germany.

stw-thueringen.de is registered under .DE top-level domain. Please check other sites in .DE zone.

Website stw-thueringen.de is using the following name servers:

dns-extern-02.uni-jena.de
dns-extern-01.uni-jena.de

and is probably hosted by 23media GmbH. See the full list of other websites hosted by 23media GmbH.

The highest website stw-thueringen.de position in Alexa rank database was 15163 and the lowest rank position was 998802. Current position of stw-thueringen.de in Alexa rank database is 681862.

Desktop speed score of stw-thueringen.de (78/100) is better than the results of 65.98% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of stw-thueringen.de (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed score of stw-thueringen.de (58/100) is better than the results of 50.23% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

stw-thueringen.de Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

stw-thueringen.de whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

Domain: stw-thueringen.de
Status: connect

stw-thueringen.de server information

Servers Location

stw-thueringen.de desktop page speed rank

Last tested: 2018-10-30

Desktop Speed Medium

78/100

stw-thueringen.de Desktop Speed Test Quick Summary

priority - 14Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 9 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.stw-thueringen.de/cms/js/cookies.js
https://www.stw-thueringen.de/cms/js/efa_fontsize.js
https://code.jquery.com/jquery-1.9.1.js
https://code.jquery.com/jquery-migrate-1.1.1.js
https://www.stw-thueringen.de/cms/js/jquery.easing.1.3.js
https://www.stw-thueringen.de/cms/js/jquery.slimmenu.min.js
https://www.stw-thueringen.de/cms/js/jquery.camera.min.js
https://www.stw-thueringen.de/cms/js/jquery.mobile.1.3.2.js
https://www.stw-thueringen.de/cms/js/jquery.cookie.js

Optimize CSS Delivery of the following:

https://www.stw-thueringen.de/cms/css/site.css
https://www.stw-thueringen.de/cms/css/style.css
https://www.stw-thueringen.de/cms/css/article_list.css
https://www.stw-thueringen.de/cms/css/skin.css
https://www.stw-thueringen.de/cms/css/camera.css
https://www.stw-thueringen.de/cms/css/slimmenu.css
https://www.stw-thueringen.de/cms/css/responsive.css
https://www.stw-thueringen.de/cms/css/responsive_start.css
https://www.stw-thueringen.de/cms/css/cookie_schwarz.css

priority - 5Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 47.1KiB (45% reduction).

Minifying https://code.jquery.com/jquery-1.9.1.js could save 37.8KiB (49% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/js/jquery.camera.min.js could save 4.5KiB (34% reduction) after compression.
Minifying https://code.jquery.com/jquery-migrate-1.1.1.js could save 2.1KiB (40% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/js/jquery.easing.1.3.js could save 1.2KiB (59% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/js/jquery.cookie.js could save 979B (30% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/js/jquery.slimmenu.min.js could save 361B (26% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/js/efa_fontsize.js could save 193B (14% reduction) after compression.

priority - 4Reduce server response time

In our test, your server responded in 0.58 seconds.

priority - 2Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 24.2KiB (16% reduction).

Compressing https://www.stw-thueringen.de/cms/upload/header_st…_stw.jpg?1540918851831 could save 8.2KiB (17% reduction).
Compressing https://www.stw-thueringen.de/cms/upload/header_st…_stw.jpg?1540918847927 could save 8KiB (17% reduction).
Compressing https://www.stw-thueringen.de/cms/upload/header_st…_stw.jpg?1540918847925 could save 7.7KiB (15% reduction).
Compressing https://www.stw-thueringen.de/cms/images/stw_button4.gif could save 204B (16% reduction).

priority - 2Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 39% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the HTML response:

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 2KiB (17% reduction).

Minifying https://www.stw-thueringen.de/cms/css/style.css could save 599B (17% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/css/camera.css could save 368B (19% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/css/site.css could save 348B (18% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/css/slimmenu.css could save 186B (14% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/css/skin.css could save 152B (31% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/css/article_list.css could save 137B (18% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/css/responsive.css could save 128B (13% reduction) after compression.
Minifying https://www.stw-thueringen.de/cms/css/responsive_start.css could save 107B (12% reduction) after compression.

stw-thueringen.de Desktop Resource Breakdown

Total Resources	40
Number of Hosts	3
Static Resources	38
JavaScript Resources	9
CSS Resources	9

stw-thueringen.de mobile page speed rank

Last tested: 2018-10-30

Mobile Speed Bad

58/100

stw-thueringen.de Mobile Speed Test Quick Summary

priority - 56Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 9 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 25% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the HTML response:

priority - 5Reduce server response time

In our test, your server responded in 0.56 seconds.

priority - 5Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 47.1KiB (45% reduction).

priority - 2Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 24.2KiB (16% reduction).

Compressing https://www.stw-thueringen.de/cms/upload/header_st…_stw.jpg?1540918859168 could save 8.2KiB (17% reduction).
Compressing https://www.stw-thueringen.de/cms/upload/header_st…_stw.jpg?1540918855264 could save 8KiB (17% reduction).
Compressing https://www.stw-thueringen.de/cms/upload/header_st…_stw.jpg?1540918855262 could save 7.7KiB (15% reduction).
Compressing https://www.stw-thueringen.de/cms/images/stw_button4.gif could save 204B (16% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 2KiB (17% reduction).

stw-thueringen.de Mobile Resource Breakdown

Total Resources	35
Number of Hosts	3
Static Resources	33
JavaScript Resources	9
CSS Resources	9

stw-thueringen.de mobile page usability

Last tested: 2018-10-30

Mobile Usability Good

99/100

stw-thueringen.de Mobile Usability Test Quick Summary

priority - 0Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/deutsch/index.html"></a> is close to 1 other tap targets.

stw-thueringen.de HTML validation

Errors

Malformed byte sequence: “fc”.

Line: 4 Column: - 27
"......" Line: 6 Column: - 51
"......" Line: 7 Column: - 54
"......" Line: 14 Column: - 97
"......" Line: 15 Column: - 52
"......" Line: 146 Column: - 82
"......" Line: 244 Column: - 91
"......" Line: 286 Column: - 126
"......" Line: 417 Column: - 75
"......" Line: 498 Column: - 84
"......" Line: 579 Column: - 24
"......" Line: 702 Column: - 68
"......" Line: 703 Column: - 96
"......" Line: 724 Column: - 903
"......" Line: 724 Column: - 921
"......" Line: 742 Column: - 275
"......" Line: 742 Column: - 287
"......" Line: 748 Column: - 568
"......" Line: 748 Column: - 581
"......"

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 122
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."

Bad value “https://www.w3.org/1999/xhtml” for the attribute “xmlns” (only “http://www.w3.org/1999/xhtml” permitted here).

Line: 2 Column: 123 - 44
"...onal.dtd"> <html xmlns="https://www.w3.org/1999/xhtml"> <head..."

Bad value “imagetoolbar” for attribute “http-equiv” on element “meta”.

Line: 12 Column: 1 - 47
"... days" /> <meta http-equiv="imagetoolbar" content="no" /> <meta..."

Internal encoding declaration “iso-8859-1” disagrees with the actual encoding of the document (“utf-8”).

Line: 61 Column: 1 - 86
"...o 4.8" /> <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=iso-8859-1" /> <meta..."

Bad value “application/xhtml+xml; charset=iso-8859-1” for attribute “content” on element “meta”: The legacy encoding declaration did not start with “text/html;”.

Line: 61 Column: 1 - 86
"...o 4.8" /> <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=iso-8859-1" /> <meta..."

Malformed byte sequence: “d6”.

Line: 212 Column: - 72
"......" Line: 727 Column: - 704
"......" Line: 727 Column: - 726
"......"

Malformed byte sequence: “e4”.

Line: 215 Column: - 80
"......" Line: 337 Column: - 78
"......" Line: 426 Column: - 90
"......" Line: 466 Column: - 94
"......" Line: 559 Column: - 25
"......" Line: 570 Column: - 20
"......" Line: 576 Column: - 21
"......" Line: 703 Column: - 91
"......" Line: 727 Column: - 836
"......" Line: 727 Column: - 850
"......" Line: 733 Column: - 422
"......" Line: 733 Column: - 441
"......" Line: 742 Column: - 599
"......" Line: 742 Column: - 612
"......" Line: 745 Column: - 855
"......" Line: 745 Column: - 875
"......" Line: 777 Column: - 175
"......"

Malformed byte sequence: “f6”.

Line: 235 Column: - 82
"......" Line: 247 Column: - 105
"......" Line: 283 Column: - 109
"......" Line: 420 Column: - 80
"......" Line: 588 Column: - 21
"......" Line: 703 Column: - 13
"......" Line: 704 Column: - 19
"......" Line: 730 Column: - 70
"......" Line: 730 Column: - 77
"......" Line: 742 Column: - 380
"......" Line: 742 Column: - 397
"......"

Malformed byte sequence: “dc”.

Line: 442 Column: - 61
"......" Line: 743 Column: - 179
"......" Line: 743 Column: - 189
"......"

Stray end tag “ul”.

Line: 504 Column: 9 - 13
"... </ul> <..."

Malformed byte sequence: “df”.

Line: 576 Column: - 31
"......" Line: 577 Column: - 29
"......" Line: 578 Column: - 34
"......" Line: 579 Column: - 32
"......" Line: 610 Column: - 31
"......"