5.2 sec in total
324 ms
4.4 sec
514 ms
Visit telepolis.de now to see the best up-to-date Telepolis content for Germany and also check out these interesting facts you probably never knew about telepolis.de
✓ kritisch, ✓ meinungsstark, ✓ informativ! Telepolis hinterfragt die digitale Gesellschaft und ihre Entwicklung in Politik, Wirtschaft & Medien.
Visit telepolis.deWe analyzed Telepolis.de page load time and found that the first response time was 324 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
telepolis.de performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value3.5 s
65/100
25%
Value4.7 s
68/100
10%
Value1,490 ms
14/100
30%
Value0.106
88/100
15%
Value10.2 s
25/100
10%
324 ms
365 ms
178 ms
180 ms
268 ms
Our browser made a total of 187 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Telepolis.de, 44% (82 requests) were made to Heise.de and 7% (13 requests) were made to Imagesrv.adition.com. The less responsive or slowest element that took the longest time to load (670 ms) relates to the external source Partner.vxcp.de.
Page size can be reduced by 615.5 kB (51%)
1.2 MB
600.7 kB
In fact, the total size of Telepolis.de main page is 1.2 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. 60% of websites need less resources to load. Images take 546.6 kB which makes up the majority of the site volume.
Potential reduce by 107.3 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 107.3 kB or 76% of the original size.
Potential reduce by 130.4 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. Obviously, Telepolis needs image optimization as it can save up to 130.4 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 377.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 377.7 kB or 72% of the original size.
Number of requests can be reduced by 90 (52%)
173
83
The browser has sent 173 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Telepolis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
telepolis.de
324 ms
365 ms
mobile-deflect.min.js
178 ms
navi_top2012.css
180 ms
frame_11.css
268 ms
element_01.css
183 ms
index_10.css
185 ms
jquery-1.7.2.min.js
365 ms
modernizr-01.js
266 ms
menu-04.js
272 ms
index-01.js
276 ms
iam.js
188 ms
66446,66442,66430,66444,223159,66424
110 ms
login.min.js
274 ms
webtrekk-v4-bundle-heise-2016-02-11.js
272 ms
rc
214 ms
gpt.js
33 ms
pubads_impl_82.js
6 ms
container.html
24 ms
heise_online_logo_top.gif
102 ms
heise_online_lupe.gif
93 ms
47711_ht.jpg
178 ms
80.png
90 ms
100.png
102 ms
140.png
104 ms
60.png
178 ms
p-news.svg
182 ms
tpack-kasten.png
274 ms
tp-top-cafe.svg
186 ms
tp-top-cafe-over.svg
190 ms
ebook_spalte-26.jpg
355 ms
buch43.jpg
354 ms
buch56.jpg
355 ms
buch48.jpg
375 ms
sp_1.gif
277 ms
tp.png
373 ms
lupe.svg
371 ms
lupe-hover.svg
448 ms
info.svg
445 ms
infoweg.svg
446 ms
infoweg-over.svg
468 ms
submit.png
463 ms
toggleheise.svg
464 ms
togglegoogle.svg
536 ms
top_rss.svg
538 ms
top_rss-over.svg
534 ms
top_mail.svg
554 ms
top_mail-over.svg
557 ms
top_google.svg
559 ms
top_google-over.svg
630 ms
top_twitter.svg
629 ms
top_twitter-over.svg
631 ms
top_facebook.svg
645 ms
top_facebook-over.svg
647 ms
top_forum.svg
648 ms
ads
275 ms
urls
668 ms
Electrolize-Regular.woff
627 ms
telepics.woff
623 ms
top_forum-over.svg
638 ms
top_mobil.svg
638 ms
top_mobil-over.svg
571 ms
popy.gif
633 ms
629 ms
heise_online_angebote_button.gif
647 ms
heise_online_lupe.png
645 ms
content_back.gif
563 ms
47720_0.jpg
572 ms
500x500
170 ms
osd.js
14 ms
47719_0.jpg
548 ms
47718_0.jpg
548 ms
47716_0.jpg
571 ms
47696_0.jpg
642 ms
47690_0.jpg
644 ms
47713_0.jpg
563 ms
47714_0.jpg
543 ms
47712_0.jpg
545 ms
47709_0.jpg
568 ms
47705_0.jpg
650 ms
47710_0.jpg
610 ms
adition.js
579 ms
js
478 ms
banner
197 ms
uid.html
172 ms
000000118743.png
89 ms
banner
516 ms
000000573667.jpg
163 ms
000000618542.jpg
281 ms
000000605863.jpg
283 ms
000000641204.jpg
280 ms
000000645382.jpg
283 ms
000000046503.png
275 ms
content_back2.gif
93 ms
coffeeback_3.gif
279 ms
ADTECH;target=_blank;grp=[group]
199 ms
ebook.gif
90 ms
widget.php
634 ms
mc.gif
130 ms
mw.gif
130 ms
print.gif
130 ms
15675219228372733599
27 ms
logoback.png
154 ms
suchtell.png
155 ms
suchback.png
157 ms
backmenu.png
164 ms
endba.png
158 ms
adServer.bs
50 ms
dtc
23 ms
dt
40 ms
adServer.bs
58 ms
allstars_update_range_800x250_fallback.jpg
48 ms
16935775437769929319
23 ms
288689636920174
237 ms
qs.ioam.de
217 ms
tx.io
211 ms
ADTECH;cfp=1;rndc=1458287611;target=_blank;grp=[group];adiframe=y
136 ms
45 ms
generic
35 ms
aol
35 ms
pixel
38 ms
ads
104 ms
container.html
30 ms
generic
29 ms
sync
30 ms
mapuser
240 ms
1x1.gif
103 ms
tx.io
110 ms
mapuser
269 ms
img;p=11042209561642;a=11042209570966;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=6263297597408477634
175 ms
acv
585 ms
000000013675.gif
133 ms
mapuser
507 ms
providerid=1037;userid=38c77b36-c859-4d75-b433-d404568760ea
341 ms
1x1.gif
142 ms
mapuser
333 ms
wt
592 ms
mapuser
325 ms
mapuser
306 ms
usermatch
23 ms
pixel.htm
79 ms
12901967733981505675
20 ms
usermatch
61 ms
1x1.gif
212 ms
vic.css.php
378 ms
vxcp_jQuery.js
670 ms
vxcp_Energy2.js
461 ms
vxcp_Common.js
599 ms
gr
24 ms
casale
13 ms
casale
26 ms
pixel.htm
65 ms
mapuser
222 ms
ddc.htm
50 ms
crum
55 ms
pixel
56 ms
rum
53 ms
crum
55 ms
Pug
77 ms
rtset
156 ms
u.php
199 ms
174 ms
um
220 ms
pixel
64 ms
rum
61 ms
setuid
135 ms
ddc.htm
121 ms
crum
132 ms
m
195 ms
sd
115 ms
bd
173 ms
tap.php
110 ms
sync
130 ms
mapuser
115 ms
xrefid.xgi
109 ms
rum
82 ms
bd
74 ms
NAX3037000600252780439
76 ms
merge
64 ms
lr.gif
53 ms
pixel.gif
39 ms
crum
20 ms
rum
16 ms
1.gif
91 ms
verivox-service-logo.png
200 ms
i12font.woff
499 ms
activeview
13 ms
telepolis.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.
telepolis.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
telepolis.de SEO score
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 Telepolis.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 Telepolis.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.
telepolis.de
Open Graph description is not detected on the main page of Telepolis. 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: