5.4 sec in total
652 ms
3.9 sec
787 ms
Click here to check amazing Thorstenfaas content. Otherwise, check out these important facts you probably never knew about thorstenfaas.de
Visit thorstenfaas.deWe analyzed Thorstenfaas.de page load time and found that the first response time was 652 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
thorstenfaas.de performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value5.8 s
15/100
25%
Value10.4 s
8/100
10%
Value6,870 ms
0/100
30%
Value0.079
94/100
15%
Value31.9 s
0/100
10%
652 ms
187 ms
282 ms
470 ms
200 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 12% of them (17 requests) were addressed to the original Thorstenfaas.de, 31% (43 requests) were made to Swr.de and 14% (19 requests) were made to Swrmediathek.de. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Swr.de.
Page size can be reduced by 1.4 MB (61%)
2.4 MB
909.5 kB
In fact, the total size of Thorstenfaas.de main page is 2.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 43.0 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 43.0 kB or 77% of the original size.
Potential reduce by 44.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. Thorstenfaas images are well optimized though.
Potential reduce by 983.5 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 983.5 kB or 70% of the original size.
Potential reduce by 372.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. Thorstenfaas.de needs all CSS files to be minified and compressed as it can save up to 372.5 kB or 85% of the original size.
Number of requests can be reduced by 80 (62%)
130
50
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thorstenfaas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 67 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.thorstenfaas.de
652 ms
style.css
187 ms
comments.css
282 ms
jquery.js
470 ms
jquery-migrate.min.js
200 ms
wp-emoji-release.min.js
97 ms
26c700e0-e95b-11e5-9a86-0026b975e0ea.htm
681 ms
7726b580-e94c-11e5-a804-0026b975f2e6.htm
696 ms
_UkN0QLrjD4
396 ms
Uc_z8ulhmTk
395 ms
index.html
1961 ms
R4f8l6s6LH4
405 ms
tfklein.jpg
335 ms
radio.jpg
335 ms
sharepic.jpg
505 ms
spdcdu.png
334 ms
andere.png
335 ms
Logo_Wahlstudie-2016.jpg
636 ms
wahlbeiuns.jpg
505 ms
simple-smile.png
504 ms
Christmas_Logo_klein.jpg
634 ms
tf_polkom.jpg
646 ms
Vortragsreihe-Landtagswahl-20162.png
810 ms
widgets.js
323 ms
1f609.png
507 ms
likebox.php
177 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
34 ms
www-embed-player-vflfNyN_r.css
39 ms
www-embed-player.js
85 ms
base.js
132 ms
syndication
247 ms
252085565544071168
342 ms
ebiMDO3r-8l.css
374 ms
jGc-59L_9lo.css
441 ms
q68gy-v_YMF.js
577 ms
FJmpeSpHpjS.js
704 ms
0wM5s1Khldu.js
571 ms
1bNoFZUdlYZ.js
603 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
85 ms
ad_status.js
82 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
46 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
52 ms
jquery-1.6.4.min.js
786 ms
playerUtils.js
287 ms
xtjwrm_20001.js
332 ms
jwplayer.js
864 ms
utilityFunctions.js
230 ms
mediathek.js
542 ms
xtcore.js
547 ms
proxy.jpg
36 ms
proxy.jpg
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
17 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
17 ms
eWFdT1BH_normal.jpg
130 ms
d30e5af6754d873c520678224a4ca3b2_normal.jpeg
156 ms
C0l6De0h_normal.jpg
284 ms
HloBNfi-_normal.jpg
435 ms
CdfdrajWEAAmMUj.jpg:small
356 ms
CdfSbHnWwAAJPiC.jpg:small
358 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
29 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
61 ms
proxy.jpg
7 ms
proxy.jpg
22 ms
561318_396739057031512_1656539302_n.jpg
301 ms
11214181_903488849689861_5682186543494631552_n.jpg
439 ms
11214063_10154174945871111_3732031954976632843_n.jpg
505 ms
1450938_652166714806871_363147515_n.jpg
511 ms
12798949_109725662754100_396650689598430808_n.jpg
584 ms
12524045_1232580876758628_4654883307080613348_n.jpg
534 ms
wL6VQj7Ab77.png
73 ms
s7jcwEQH7Sx.png
73 ms
jot.html
2 ms
AjaxEntry
115 ms
AjaxEntry
140 ms
iam.js
631 ms
related.js
330 ms
visuallyImpaired.js
110 ms
tabPlayButton.js
113 ms
info.js
214 ms
swrsharing.js
326 ms
ardSubtitleFormat.js
326 ms
ivwng.js
213 ms
atInternet.js
214 ms
I6-MnjEovm5.js
68 ms
pQrUxxo5oQp.js
137 ms
hit.xiti
337 ms
hit.xiti
319 ms
base.css
11 ms
swr-base-container.css
39 ms
jquery-ui-1.10.4.css
21 ms
swrde-base-container.css
22 ms
index.css
103 ms
redirector.js
37 ms
1031717218.js
42 ms
jquery-1.7.2.mini.js
39 ms
jquery-ui-1-10-4.js
39 ms
jquery.waitforimages.js
37 ms
Application.js
37 ms
MediaMatcher.js
40 ms
iscroll.js
40 ms
BaseController.js
41 ms
AttributeSwapController.js
41 ms
CollapsibleController.js
42 ms
SlidableController.js
44 ms
SocialMediaController.js
43 ms
SortableController.js
43 ms
TableController.js
44 ms
targeting.js
44 ms
responsive-design-sammel-javascript.js
46 ms
swrplayer.js
44 ms
xtjwrm_20001.js
46 ms
jwplayer.js
51 ms
ggcmb390.js
51 ms
swrcollapsiblecontroller.js
51 ms
index.js
59 ms
xtcore.js
16 ms
event
93 ms
ardSubtitleFormat.js
45 ms
swrsharing.js
14 ms
visuallyImpaired.js
15 ms
info.js
44 ms
onlyOnePlayerPlays.js
14 ms
szmng.js
15 ms
atInternet.js
14 ms
agf.js
56 ms
related.js
58 ms
Fritz%20Frey%20mit%20Julia%20Kl%C3%B6ckner%20und%20Malu%20Dreyer%20im%20Studio.jpg
112 ms
index.png
101 ms
TheMix_LT_TT5_.woff
37 ms
TheSans_LT_TT5_.woff
39 ms
TheSans_LT_TT7_.woff
39 ms
hit.xiti
216 ms
tx.io
195 ms
tx.io
198 ms
tx.io
192 ms
swrde-print.css
3 ms
tx.io
100 ms
tx.io
99 ms
tx.io
98 ms
thorstenfaas.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
thorstenfaas.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
thorstenfaas.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Thorstenfaas.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 Thorstenfaas.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.
thorstenfaas.de
Open Graph description is not detected on the main page of Thorstenfaas. 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: