10.7 sec in total
986 ms
9.4 sec
312 ms
Welcome to fanfeed.de homepage info - get ready to check Fanfeed best content for Germany right away, or after learning these important things about fanfeed.de
The domain fanfeed.de is for sale. You can buy this domain now by buy-it-now at a fixed price with the escrow service of ELITEDOMAINS.
Visit fanfeed.deWe analyzed Fanfeed.de page load time and found that the first response time was 986 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fanfeed.de performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value1.8 s
100/100
10%
Value170 ms
92/100
30%
Value0.197
62/100
15%
Value3.0 s
96/100
10%
986 ms
344 ms
27 ms
9 ms
433 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 58% of them (91 requests) were addressed to the original Fanfeed.de, 6% (10 requests) were made to and 6% (10 requests) were made to Adserver.adtech.de. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Hal9000.redintelligence.net.
Page size can be reduced by 679.6 kB (27%)
2.5 MB
1.8 MB
In fact, the total size of Fanfeed.de main page is 2.5 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 56.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 56.3 kB or 73% of the original size.
Potential reduce by 60.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. Fanfeed images are well optimized though.
Potential reduce by 302.9 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 302.9 kB or 63% of the original size.
Potential reduce by 260.2 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. Fanfeed.de needs all CSS files to be minified and compressed as it can save up to 260.2 kB or 57% of the original size.
Number of requests can be reduced by 81 (60%)
134
53
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanfeed. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
fanfeed.de
986 ms
fonts.css
344 ms
css
27 ms
font-awesome.min.css
9 ms
animate.css
433 ms
iframeResizer.min.js
224 ms
mikado.css
223 ms
font-awesome.css
9 ms
polls-css.css
224 ms
style.css
545 ms
font-awesome.min.css
537 ms
jquery.js
756 ms
jquery-migrate.min.js
437 ms
jquery.easing.js
436 ms
jquery.Mikado.js
760 ms
addyn%7C3.0%7C59%7C5709269%7C0%7C1356%7CADTECH;cfp=1
106 ms
polls-js.js
443 ms
hoverIntent.js
447 ms
hoverIntent.min.js
540 ms
superfish.js
542 ms
lightbox.js
663 ms
jflickrfeed.min.js
664 ms
jquery.touchSwipe.min.js
750 ms
jquery.mousewheel.min.js
751 ms
jquery.flexslider-min.js
971 ms
jquery.slicknav.min.js
761 ms
scripts.js
978 ms
376C0B10B39D20E93.css
1334 ms
DAC.js
204 ms
ADTECH;loc=100
424 ms
rta.js
48 ms
prebid.js
28 ms
ad.js
390 ms
wp-emoji-release.min.js
114 ms
reset.css
111 ms
common.css
223 ms
bind
101 ms
logo.png
136 ms
logo-teamsports_small.png
136 ms
category-filter-arrow-down-green.png
216 ms
20x20-FC-Bayern.png
235 ms
20x20-Schalke-04.png
236 ms
20x20-BVB.png
237 ms
20x20-Leverkusen.png
333 ms
20x20-Wolfsburg.png
329 ms
20x20-MGladbach.png
441 ms
20x20-Mainz-05.png
438 ms
20x20-FC-Augsburg.png
441 ms
20x20-TSG-Hoffenheim.png
438 ms
20x20-han.96.png
545 ms
20X20-FC-Ingolstadt.png
549 ms
20x20-Hertha-BSC.png
650 ms
20x20-Werder-Bremen.png
653 ms
20x20-Eintrach-Frankfurt.png
653 ms
20x20-VfB-Stuttgart.png
656 ms
20x20-HSV.png
760 ms
20x20-FC-K%C3%B6ln.png
764 ms
20X20-SV-Darmstadt.png
870 ms
home-fanheat.png
873 ms
CdtCSBRWEAAxHKO.jpg-large-125x83.jpeg
875 ms
home-hot-posts-hot-indicator.png
877 ms
930702_heroa-125x83.jpg
975 ms
man-city-post-quality-hand-drawn-1024x576-125x83.jpg
985 ms
d0dc6c6a-e9d8-11e5-a4f7-f80f41fc63ce-125x83.jpg
1084 ms
Cdt8oyWUEAAov1D.jpg-large-125x83.jpeg
1093 ms
fcb-arsenal_0-125x83.jpg
1093 ms
category-overlay-videos.png
1098 ms
Bildschirmfoto-2016-03-17-um-16.09.01-370x214.png
1638 ms
category-flag-icon-videos.png
1207 ms
category-overlay-news.png
1303 ms
Cd05yKBXEAA0dOw-370x214.jpg
1421 ms
category-flag-icon-news.png
1318 ms
category-overlay-feedtures.png
1266 ms
RM4kcZ5MkDXu6tqFAJ+6P4TDwQBZuSm6s3bPLjOAXc3zgryRD6RvJMxu5vESzueCK8l3nDayhZyYLP285KV8lyZOPiPHlIeljK+PSG5w2eHH4rxS8YMUEi
11 ms
RM4kcZ5MkDXu6tqFAJ+6P4TDwQBZuSm6s3bPLjOAXc3zgryRD6RvJMxu5vESzueCK8l3nDayhZyYLP285KV8lyZOPiPHlIeljK+PSG5w2eHH4rxS9ZZUEy
10 ms
e8LzB4+NvJf8FmsFBQg==
10 ms
w4TgF3Ny5KMoS+kTyTsfs7BIt7ngjvZd7wGkpWsuDzprPSVbIc2bg4T+6THpcyPr7heYMnx99K8QvnI0EW
9 ms
t3CBb3PBJezbzlNZQsZcHnTWelq2Q5snFxntwnPe5lfHzJ8xJPjr+W4henzkHu
9 ms
bzkpXyXJk4+I8eUh6WMr49IbnDZ4cfivFLxgxQSI=
8 ms
bzkpXyXJk4+I8eUh6WMr49IbnDZ4cfivFL1llQTI=
8 ms
BZrBQUI=
8 ms
DhOAXc3LkoyhL6RPJOx+zsEi3ueCO9l3vAaSlay4POms9JVshzZuDhP7pMelzI+vuF5gyfH30rxC+cjQRY=
8 ms
t3CBb3PBJezbzlNZQsZcHnTWelq2Q5snFxntwnPe5lfHzJ8xJPjr+W4henzkHu
7 ms
fontawesome-webfont.woff
63 ms
fontawesome-webfont.woff
64 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
64 ms
dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf
64 ms
dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf
64 ms
sdk.js
168 ms
analytics.js
62 ms
sitelib.js
91 ms
netpoint-media.de.js
181 ms
fontawesome-webfont.woff
1491 ms
linkid.js
13 ms
MLS-Gehalt-Top-12-Saison-201516.jpg
2027 ms
collect
3 ms
collect
78 ms
gw.js
163 ms
augur.min.js
12 ms
_.htm
59 ms
category-flag-icon-feedtures.png
1300 ms
tottenham-bvb-600-370x214.jpg
1416 ms
csm_1930-H96Eintr241015_03_50755db23a-370x214.jpg
1523 ms
1458141064_852021_1458141304_doscolumnas_normal-370x214.jpg
1619 ms
145 ms
xd_arbiter.php
164 ms
xd_arbiter.php
269 ms
1
31 ms
Bildschirmfoto-2016-03-18-um-10.24.56-370x214.png
1833 ms
Golden-Shoe.jpg
2188 ms
generic
7 ms
generic
7 ms
module-icon-videos.png
1427 ms
Bildschirmfoto-2016-03-07-um-09.55.53-509x294.png
1977 ms
module-overlay-videos-large.png
1637 ms
CczwoJXWIAE1yCm-240x139.jpg
1640 ms
mapuid
11 ms
389868485.js
109 ms
module-overlay-videos-small.png
1752 ms
man-city-post-quality-hand-drawn-1024x576-240x139.jpg
1853 ms
Bildschirmfoto-2016-03-11-um-11.27.15-240x139.png
1941 ms
sidebar-videos-icon.png
1744 ms
Bildschirmfoto-2016-03-10-um-13.01.36-226x122.png
1966 ms
1458141064_852021_1458141304_doscolumnas_normal-226x122.jpg
1960 ms
PUMA-twitter-BVB-EL-Tottenham-Hotspur-226x122.jpg
1860 ms
sidebar-bilder-icon.png
1866 ms
postscribe.js
11 ms
ADTECH;loc=100;kvseite=home;grp=812;screenheight=768;screenwidth=1024;screendensity=1;kvscreenheight=768;kvscreenwidth=1024;kvscreendensity=1;kvviewportwidth=1680;kvviewportheight=1050;misc=1458393956811
106 ms
beginPersonalization
108 ms
Romelu-Lukaku-226x122.jpg
1870 ms
Toprak-Manchester-United-Transfer-226x122.jpg
1935 ms
Bildschirmfoto-2016-03-10-um-10.45.40-226x122.png
2169 ms
related-posts-hot-icon.png
1954 ms
nadj
134 ms
CdtCSBRWEAAxHKO.jpg-large-226x122.jpeg
1964 ms
widget-hot-posts-hot-indicator.png
1861 ms
930702_heroa-226x122.jpg
1879 ms
man-city-post-quality-hand-drawn-1024x576-226x122.jpg
1934 ms
ADTECH;loc=100;target=_blank;grp=812;misc=1458393957090
105 ms
arrow-scroll-top.png
1949 ms
addyn%7C3.0%7C59%7C5709732%7C0%7C16%7CADTECH;loc=100;target=_blank;grp=812;misc=1458393957199
103 ms
Default_Size_16_1x1.gif
12 ms
pixel
23 ms
generic
10 ms
match
7 ms
ADTECH;loc=100;kvseite=home;grp=812;screenheight=768;screenwidth=1024;screendensity=1;kvscreenheight=768;kvscreenwidth=1024;kvscreendensity=1;kvviewportwidth=1680;kvviewportheight=1050;misc=1458393956944
105 ms
pixel
26 ms
match
6 ms
match
5 ms
match
4 ms
match
5 ms
nadj
103 ms
neg.js
5 ms
ADTECH;loc=100;target=_blank;grp=812;misc=1458393957543
162 ms
addyn%7C3.0%7C59%7C5709733%7C0%7C225%7CADTECH;loc=100;target=_blank;grp=812;misc=1458393957710
105 ms
le48qic1we7j
4193 ms
adcount%7C2.0%7C59%7C5709733%7C0%7C225%7CAdId=13681502;BnId=2;ct=3452668915;st=5056;adcid=1;itime=393956782;reqtype=5;;
102 ms
fanfeed.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
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.
fanfeed.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
fanfeed.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanfeed.de can be misinterpreted by Google and other search engines. Our service has detected that English 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 Fanfeed.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.
fanfeed.de
Open Graph data is detected on the main page of Fanfeed. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: