4.2 sec in total
292 ms
2.7 sec
1.2 sec
Click here to check amazing Teezeh content for Germany. Otherwise, check out these important facts you probably never knew about teezeh.de
Thomas Cloer ist Corporate Communications Manager in München. Dieses private Blog betreibt der frühere COMPUTERWOCHE-Redakteur seit 2003.
Visit teezeh.deWe analyzed Teezeh.de page load time and found that the first response time was 292 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
teezeh.de performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value8.0 s
2/100
25%
Value7.3 s
28/100
10%
Value20 ms
100/100
30%
Value0.011
100/100
15%
Value4.7 s
80/100
10%
292 ms
505 ms
300 ms
308 ms
5 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 30% of them (20 requests) were addressed to the original Teezeh.de, 12% (8 requests) were made to Fonts.gstatic.com and 11% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source I1.wp.com.
Page size can be reduced by 836.4 kB (48%)
1.7 MB
902.5 kB
In fact, the total size of Teezeh.de main page is 1.7 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. 65% of websites need less resources to load. Javascripts take 871.9 kB which makes up the majority of the site volume.
Potential reduce by 47.9 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 47.9 kB or 77% of the original size.
Potential reduce by 16.2 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. Teezeh images are well optimized though.
Potential reduce by 596.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 596.5 kB or 68% of the original size.
Potential reduce by 175.8 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. Teezeh.de needs all CSS files to be minified and compressed as it can save up to 175.8 kB or 76% of the original size.
Number of requests can be reduced by 32 (59%)
54
22
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teezeh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
teezeh.de
292 ms
www.teezeh.de
505 ms
wp-emoji-release.min.js
300 ms
1456744293index.css
308 ms
font-awesome.min.css
5 ms
1456744293index.css
572 ms
1456744292index.css
414 ms
1456744293index.js
518 ms
1456744293index.js
287 ms
widgets.js
79 ms
1456744293index.js
207 ms
1456744293index.js
216 ms
1456744293index.js
225 ms
1456744293index.js
310 ms
1456744293index.js
317 ms
1456744293index.js
328 ms
devicepx-jetpack.js
57 ms
gprofiles.js
60 ms
1456744346index.js
495 ms
1456744293index.js
494 ms
1456744293index.js
496 ms
e-201609.js
4 ms
analytics.js
79 ms
sp4.jpg
1461 ms
55752f80fdd21f3cfc5d597ca4637adc
77 ms
targeting.png
1014 ms
NOMOS_Orion_weiss_02.jpg
636 ms
banner-igel-220x220px.png
883 ms
cc.png
71 ms
bad-santa.jpg
636 ms
logo-teezeh-mosaik-1200x280.png
587 ms
thomas-cloer-sq.jpg
585 ms
SL_1200GAE_7.jpg
882 ms
embed.html
75 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
123 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
488 ms
RFda8w1V0eDZheqfcyQ4ENqQynqKV_9Plp7mupa0S4g.ttf
564 ms
ZvcMqxEwPfh2qDWBPxn6nqp5NA6AAOjfQM_HmvD0shQ.ttf
564 ms
ZvcMqxEwPfh2qDWBPxn6ngvr42gIYPGl20Rgir8ypAU.ttf
710 ms
Genericons.svg
847 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
51 ms
So5lHxHT37p2SS4-t60SlP-h276deSBHSGl3jPkVKDo.ttf
711 ms
EYh7Vl4ywhowqULgRdYwIONfVQSuMy1q3WzzeUBr2Ns.ttf
710 ms
EYh7Vl4ywhowqULgRdYwIGOs5rKs1XhQYCgZqE8eCYU.ttf
710 ms
embed.min.css
64 ms
jquery.min.js
464 ms
embed.min.js
508 ms
collect
346 ms
hovercard.css
236 ms
services.css
258 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
326 ms
tweet.04d20138f67ab41d6b4af6cc583926d9.js
347 ms
g.gif
211 ms
USRV31500005
318 ms
mp4
316 ms
hls
326 ms
syndication
140 ms
676822907218231296
260 ms
tweets.json
161 ms
syndication
148 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
28 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
55 ms
fZ2A_k3N_normal.png
34 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
28 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
35 ms
SkODK5oq_normal.jpg
3 ms
teezeh.de accessibility score
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
Links do not have a discernible name
teezeh.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
teezeh.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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teezeh.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 Teezeh.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.
teezeh.de
Open Graph data is detected on the main page of Teezeh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: