12.2 sec in total
2.9 sec
8.7 sec
576 ms
Visit tus-henrichenburg.de now to see the best up-to-date TuS Henrichenburg content and also check out these interesting facts you probably never knew about tus-henrichenburg.de
Vereinsseite des TuS Henrichenburg mit Jugend-, Senioren-, Alte Herren- und Turnabteilung im Herzen des Ruhrgebietes (Castrop-Rauxel)
Visit tus-henrichenburg.deWe analyzed Tus-henrichenburg.de page load time and found that the first response time was 2.9 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Tus-henrichenburg.de rating and web reputation
tus-henrichenburg.de performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value17.2 s
0/100
25%
Value15.4 s
1/100
10%
Value370 ms
70/100
30%
Value0.088
92/100
15%
Value13.4 s
11/100
10%
2921 ms
176 ms
200 ms
211 ms
213 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 64% of them (46 requests) were addressed to the original Tus-henrichenburg.de, 8% (6 requests) were made to Vb-waltrop.viele-schaffen-mehr.de and 7% (5 requests) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Tus-henrichenburg.de.
Page size can be reduced by 302.8 kB (34%)
883.3 kB
580.5 kB
In fact, the total size of Tus-henrichenburg.de main page is 883.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. 35% of websites need less resources to load. Images take 509.9 kB which makes up the majority of the site volume.
Potential reduce by 41.1 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 41.1 kB or 78% of the original size.
Potential reduce by 37.5 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. TuS Henrichenburg images are well optimized though.
Potential reduce by 196.7 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 196.7 kB or 68% of the original size.
Potential reduce by 27.5 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. Tus-henrichenburg.de needs all CSS files to be minified and compressed as it can save up to 27.5 kB or 83% of the original size.
Number of requests can be reduced by 38 (56%)
68
30
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TuS Henrichenburg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
tus-henrichenburg.de
2921 ms
style001.css
176 ms
phocadownload.css
200 ms
imgFrame.css
211 ms
agora_latest_b.css
213 ms
acajoom.css
214 ms
mootools-uncompressed.js
826 ms
caption.js
282 ms
gmaccessjs.js
304 ms
template.css
320 ms
red.css
325 ms
template.css
319 ms
01LJL4P84G000000VS541L4HVSSAM09C
298 ms
AC_OETags.js
389 ms
tus-henrichenburg.de
102 ms
TuS_Logo_Start.png
416 ms
TB-banner1-1.jpg
37 ms
09162534-7a59-4516-8bb0-553f473d6e1e.png
975 ms
search.jpg
114 ms
2a.png
401 ms
noavatar.jpg
117 ms
Fabrice%20Czaja.jpg
105 ms
pdf_button.png
114 ms
printButton.png
208 ms
emailButton.png
222 ms
topmenu_left.png
194 ms
topmenu_right.png
200 ms
topmenu_bg.png
290 ms
topmenu_over.jpg
300 ms
left_border.png
305 ms
right_border.png
307 ms
moduletable_bg.gif
391 ms
moduletable_bottom.png
403 ms
moduletable_top.gif
406 ms
moduletable_h3.png
419 ms
mainlevel_bg.gif
470 ms
button.jpg
470 ms
adscript.php
316 ms
TB-banner1-1.jpg
70 ms
user_top_bg.jpg
111 ms
2319 ms
WerbungUnten.htm
262 ms
user_top_left.jpg
122 ms
user_top_right.jpg
114 ms
separator.jpg
123 ms
content_bottom_bg.jpg
125 ms
border.gif
117 ms
content_bottom_right.jpg
188 ms
content_bottom_left.jpg
214 ms
componentheading.jpg
213 ms
bottom_right.png
220 ms
bottom_left.png
219 ms
bottom.png
224 ms
a
9 ms
s.gif
11 ms
jquery.min.js
91 ms
e.js
514 ms
a3fe05d6.png
287 ms
sprite.png
292 ms
pic.php
893 ms
logo.vsm.png
890 ms
jquery-1.8.3.min.js
1233 ms
1110 ms
t.js
1115 ms
1092 ms
simplepopin.css
628 ms
sdk.js
505 ms
184 ms
xd_arbiter.php
70 ms
154 ms
cnt_js.php
157 ms
cntcc
150 ms
tus-henrichenburg.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
tus-henrichenburg.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
tus-henrichenburg.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tus-henrichenburg.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 Tus-henrichenburg.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.
tus-henrichenburg.de
Open Graph description is not detected on the main page of TuS Henrichenburg. 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: