7.7 sec in total
315 ms
7 sec
318 ms
Click here to check amazing MyFanbase content for Germany. Otherwise, check out these important facts you probably never knew about myfanbase.de
News, Episodenbeschreibungen und Reviews zu deinen liebsten TV- und Streaming-Serien sowie ausführliche Hintergrundinfos zu deinen Lieblingsstars bei myFanbase.
Visit myfanbase.deWe analyzed Myfanbase.de page load time and found that the first response time was 315 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
myfanbase.de performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.5 s
37/100
25%
Value7.7 s
25/100
10%
Value2,840 ms
3/100
30%
Value0.437
21/100
15%
Value9.3 s
31/100
10%
315 ms
3853 ms
205 ms
229 ms
232 ms
Our browser made a total of 204 requests to load all elements on the main page. We found that 29% of them (59 requests) were addressed to the original Myfanbase.de, 7% (14 requests) were made to Cdn.flashtalking.com and 5% (10 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Myfanbase.de.
Page size can be reduced by 1.6 MB (47%)
3.4 MB
1.8 MB
In fact, the total size of Myfanbase.de main page is 3.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. 75% 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.7 MB which makes up the majority of the site volume.
Potential reduce by 223.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 223.0 kB or 74% of the original size.
Potential reduce by 95.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. MyFanbase images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 66% of the original size.
Potential reduce by 172.7 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. Myfanbase.de needs all CSS files to be minified and compressed as it can save up to 172.7 kB or 86% of the original size.
Number of requests can be reduced by 106 (56%)
188
82
The browser has sent 188 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MyFanbase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 72 to 1 for JavaScripts and as a result speed up the page load time.
myfanbase.de
315 ms
www.myfanbase.de
3853 ms
default-201602-2.css
205 ms
myfanbase.min.E784DA26.js
229 ms
modernizr.js
232 ms
praeludium_myfanbase.js
227 ms
addthis_widget.js
46 ms
plusone.js
157 ms
container
188 ms
adex.js
286 ms
rc
251 ms
google_custom_search_watermark.gif
65 ms
noavatar92.png
51 ms
empty.gif
155 ms
logo.gif
156 ms
claim.png
154 ms
suche.gif
155 ms
2dcd8ddad6f10715059aa070e3cf5a5a.jpg
434 ms
115b655005aecabf1171e0ebbe7d1f44.jpg
433 ms
2b72e461189337c71c487466ac7dc6fd.jpg
272 ms
b1ffc328d3bfd420805bc4df4e84f223.jpg
434 ms
118cff8ce897e41d8bd7cc714cfe3708.jpg
382 ms
7c4d72ccf836ce5140e7ed8d0bf6e578.jpg
433 ms
marker.gif
432 ms
24401c3b34e269182ccf9466f7122b33.jpg
470 ms
cee365e9248e524dbbc4fd929028a936.jpg
470 ms
0da3f85df7791fc606029310be063d15.jpg
487 ms
db00a8c0c0a5fcb889620bf24cb5b96a.jpg
487 ms
68d2fbf9d42ab1abceb8845b2315bc2a.jpg
473 ms
324fca155f9b2512cd4402a641e46a96.jpg
493 ms
1550986e3abf004a909c273ef7f636a4.jpg
593 ms
30ddcbb5f3b6ed1ba47be90d6e1cfa9e.jpg
595 ms
857516f804b9cbf7b79dc54a12e2f880.jpg
593 ms
f81a72f9b2628d2c9931592c97dec989.jpg
593 ms
a454ff7a6aba65b517e3f213a3e5b570.jpg
593 ms
324138fb26da4c10bfe289ba86dfd67e.jpg
594 ms
ae23693ae999213f9ed821bcd07d4f98.jpg
701 ms
ae34fe8e9775810a4397ca5ebfbb7c0d.jpg
703 ms
82acad4ccff8650272b52a241df1c6d3.jpg
704 ms
d094c5070c5198e60d9e13bcbe106b5a.jpg
702 ms
96a36730b4442ac6ed85751d0c439793.jpg
697 ms
6f485bfd5d83e44d30b66631b221fa69.jpg
702 ms
7abcdf63da365a4fcd55c5068be679ae.jpg
799 ms
93dfbac1b1575f69b675ad478025a221.jpg
802 ms
edab8e7f205b8756da961267e472d4f9.jpg
803 ms
29d55276a7289a79470a1478f321c146.jpg
811 ms
5aec16823827f6b2150e532ab98192ab.jpg
812 ms
1617271.jpg
803 ms
play.png
894 ms
ga.js
24 ms
google_custom_search_watermark.gif
162 ms
__utm.gif
81 ms
layers.3643cb2e25fb91c29386.js
33 ms
all.js
78 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
70 ms
page
149 ms
1616590.jpg
761 ms
1616447.jpg
761 ms
45dc1b340a8515d8f1a46989ae9e3f58.jpg
762 ms
300lo.json
54 ms
bc15d9847423a2fc8a41e3b1ced3ce8c.jpg
750 ms
container
423 ms
sh.7c7179124ea24ac6ba46caac.html
63 ms
postmessageRelay
72 ms
gpt_call.sjs
164 ms
f9f69f321faeacf072cdf3fa17187444.jpg
649 ms
148 ms
t.js
163 ms
rs=AGLTcCP7QmyL0n7lWdJHyTR4Kc2wLBKSGg
22 ms
rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow
53 ms
rs=AGLTcCMg0-J6nGLfhba_oTPq7RA1FuMjBg
83 ms
xd_arbiter.php
48 ms
xd_arbiter.php
137 ms
photo.jpg
198 ms
api.js
126 ms
core:rpc:shindig.random:shindig.sha1.js
181 ms
2536007149-postmessagerelay.js
157 ms
grlryt2bdKIyfMSOhzd1eA.woff
168 ms
d-QWLnp4didxos_6urzFtg.woff
215 ms
vxNK-E6B13CyehuDCmvQvw.woff
244 ms
rs=AGLTcCMg0-J6nGLfhba_oTPq7RA1FuMjBg
44 ms
5e4f00d80f1dffbfb1ada8166650d8a2.jpg
583 ms
b9dc4d89a862e14d20190854e70ad9e6.jpg
586 ms
75d2fb0468bfb5c2cc128659de6e5b36.jpg
596 ms
prosieben.png
594 ms
sixx.png
592 ms
editorial.png
593 ms
gpt.js
45 ms
1.gif
134 ms
analytic.js
213 ms
215 ms
area-sprite-21A5E34D.png
1372 ms
rss.svg
653 ms
rs=AGLTcCMg0-J6nGLfhba_oTPq7RA1FuMjBg
14 ms
facebook.svg
648 ms
twitter.svg
644 ms
googleplus.svg
648 ms
pubads_impl_81.js
52 ms
tumblr.svg
641 ms
ads
342 ms
container.html
17 ms
youtube.svg
644 ms
yieldlabRedirect
259 ms
pixel
55 ms
improveDigitalRedirect
260 ms
rubiconRedirect
290 ms
pixel
14 ms
adxSyncDone
278 ms
pixel
18 ms
redirect
199 ms
cm.gif
89 ms
adscaleSyncDone
304 ms
2.gif
99 ms
2.gif
97 ms
match
4 ms
mtrcs_284704.js
197 ms
ads
46 ms
osd.js
9 ms
943 ms
ads
318 ms
mtrcs_284704.js
51 ms
expansion_embed.js
15 ms
ads
248 ms
bsredirect5.js
106 ms
adj
76 ms
beacon
64 ms
tap.php
483 ms
activeview
17 ms
bst2tv3.html
93 ms
verifyc.js
23 ms
aclk
51 ms
bsredirect5.js
15 ms
adj
73 ms
beacon
65 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
62 ms
lidar.js
59 ms
antenna2.js
80 ms
dvtp_src.js
104 ms
ca
91 ms
verifyc.js
42 ms
index.html
25 ms
firstevent
12 ms
aclk
31 ms
easeljs-0.8.1.min.js
131 ms
tweenjs-0.6.1.min.js
154 ms
movieclip-0.8.1.min.js
150 ms
preloadjs-0.6.1.min.js
158 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250.js
25 ms
dvtp_src_internal25.js
54 ms
pixel
246 ms
sbhK2lTE.js
39 ms
push
40 ms
event
123 ms
antenna2.js
121 ms
dvtp_src.js
127 ms
ca
126 ms
cTrvNaRi.html
7 ms
t2tv7.html
170 ms
visit.js
119 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
146 ms
index.html
102 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250_atlas_.json
89 ms
submit
297 ms
visit.js
65 ms
j-1644918-1300138.js
151 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_160x600_SP.js
32 ms
avs564.js
133 ms
pixel
42 ms
pixel
37 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250_atlas_.png
117 ms
push
117 ms
event.gif
135 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_160x600_SP_atlas_.json
108 ms
pixel
126 ms
pixel
124 ms
avs577.js
114 ms
event.gif
119 ms
event.gif
75 ms
event.gif
76 ms
event.gif
76 ms
event.jpg
60 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_160x600_SP_atlas_.png
58 ms
zdf_gaetjen_jonglage_800x250.html
329 ms
ftpagefold_v4.4.1.js
60 ms
sDm_BB_Pos.js
145 ms
event.jpg
34 ms
ft.stat
34 ms
Pix-1x1.gif
49 ms
sd
59 ms
mtrcs_284704.js
100 ms
pixel
12 ms
lc.js
55 ms
html5API.js
24 ms
txt_0.png
101 ms
txt_1.png
49 ms
arrow.png
68 ms
txt_1b.png
66 ms
zdf_logo.png
55 ms
play.svg
55 ms
mute.svg
108 ms
unmute.svg
103 ms
manifest.js
94 ms
jquery.min.js
60 ms
myfanbase.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
myfanbase.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
Page has valid source maps
myfanbase.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myfanbase.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Myfanbase.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
myfanbase.de
Open Graph data is detected on the main page of MyFanbase. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: