9 sec in total
3.3 sec
5 sec
765 ms
Visit fancentric.fm now to see the best up-to-date Fancentric content and also check out these interesting facts you probably never knew about fancentric.fm
The power of a search engine with real-time email content automation and a drag-and-drop studio, capture content anywhere and share your stories everywhere.
Visit fancentric.fmWe analyzed Fancentric.fm page load time and found that the first response time was 3.3 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fancentric.fm performance score
3271 ms
116 ms
36 ms
50 ms
57 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fancentric.fm, 8% (12 requests) were made to Sumome.com and 7% (10 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Storyports.com.
Page size can be reduced by 1.9 MB (50%)
3.8 MB
1.9 MB
In fact, the total size of Fancentric.fm main page is 3.8 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 62.5 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 62.5 kB or 75% of the original size.
Potential reduce by 111.1 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. Fancentric images are well optimized though.
Potential reduce by 860.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 860.7 kB or 61% of the original size.
Potential reduce by 846.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. Fancentric.fm needs all CSS files to be minified and compressed as it can save up to 846.8 kB or 90% of the original size.
Number of requests can be reduced by 83 (71%)
117
34
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fancentric. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
storyports.com
3271 ms
3033840044.js
116 ms
css
36 ms
css
50 ms
css
57 ms
style.css
29 ms
tab.css
21 ms
shortcodes.css
21 ms
shortcodes_responsive.css
21 ms
magnific_popup.css
28 ms
jetpack.css
24 ms
jquery.js
29 ms
jquery-migrate.min.js
21 ms
tab.js
25 ms
load.sumome.com
371 ms
jquery-1.9.1.js
7 ms
jquery-migrate-1.2.1.js
18 ms
jquery-ui.js
17 ms
frontend-builder-global-functions.js
8 ms
photon.js
18 ms
devicepx-jetpack.js
8 ms
gprofiles.js
112 ms
wpgroho.js
9 ms
jquery.mobile.custom.min.js
15 ms
custom.js
11 ms
smoothscroll.js
8 ms
jquery.fitvids.js
10 ms
waypoints.min.js
13 ms
jquery.magnific-popup.js
15 ms
frontend-builder-scripts.js
16 ms
wp-embed.min.js
14 ms
e-201611.js
13 ms
wp-emoji-release.min.js
236 ms
style.css
39 ms
Screen-Shot-2015-04-29-at-12.39.02-PM.png
62 ms
Field_Guide_Cover.jpg
59 ms
Twitter-in-Email-Playbook.jpg
319 ms
jkz5
319 ms
videoinemailcover.jpg
53 ms
umg_grey.png
152 ms
interscrope_grey.png
54 ms
StoryPorts-Newsletter1.jpg
56 ms
storyports.png
55 ms
Screen-Shot-2015-10-02-at-10.30.40-AM.png
61 ms
Spotify.jpg
62 ms
blue_shape_bg.jpg
57 ms
Bryan1.jpg
56 ms
Jen_Ribble-Small.jpg
58 ms
10456003_10101472393658207_8499147645574389984_n.jpg
59 ms
macmillian_grey.png
53 ms
tvland_grey.png
54 ms
exacttarget_grey.png
115 ms
jduSEW07_j4sIG_ERxiq4Q.woff
27 ms
HXiERDIZdwFzjXlbcMq7XPesZW2xOQ-xsNqO47m55DA.woff
27 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
25 ms
boeCNmOCCh-EWFLSfVffDg.woff
24 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
24 ms
wkfQbvfT_02e2IWO3yYueQ.woff
23 ms
BVtM30trf7q_jfqYeHfjtA.woff
24 ms
ETmodules_v2_4.ttf
25 ms
Pq7I38KtY37kAe5aYFKrSA.woff
25 ms
lILlYDvubYemzYzN7GbLkBsxEYwM7FgeyaSgU71cLG0.woff
25 ms
gtm.js
214 ms
hovercard.css
58 ms
services.css
60 ms
316 ms
form.css
45 ms
piUtils.js
44 ms
g.gif
21 ms
roundtrip.js
79 ms
conversion_async.js
78 ms
analytics.js
46 ms
oct.js
75 ms
required.gif
103 ms
collect
18 ms
87 ms
adsct
155 ms
adsct
95 ms
83 ms
83 ms
pd.js
16 ms
analytics
229 ms
WTZAA5CHZVFFNLOSWZSID2.js
34 ms
50 ms
72 ms
85 ms
91 ms
ga-audiences
53 ms
fbevents.hashing.js
193 ms
out
8 ms
37 ms
out
22 ms
out
21 ms
out
30 ms
out
28 ms
out
29 ms
out
29 ms
out
34 ms
out
34 ms
45 ms
u.php
99 ms
adsct
40 ms
sync
19 ms
pixel
50 ms
29 ms
82 ms
27 ms
377928.gif
8 ms
sd
7 ms
23 ms
tap.php
13 ms
service.js
14 ms
service.js
41 ms
service.js
40 ms
service.js
44 ms
service.js
39 ms
service.js
40 ms
in
5 ms
sumome-smartbar-popup.css
59 ms
css
20 ms
sumome-welcome-popup.css
8 ms
sumome-scrollbox-popup.css
4 ms
sme-popup.css
11 ms
analytics
125 ms
embed_shepherd-v1.js
138 ms
99 ms
load
371 ms
load
237 ms
load
302 ms
load
361 ms
status
326 ms
nr-593.min.js
26 ms
2102b882ae28d718d504997fdfcb9d7766d080a7
36 ms
analytics
258 ms
0e5619d846
49 ms
intercom.21a35ffd.js
65 ms
iframe_shim
112 ms
status
259 ms
echo.515e8809.js
69 ms
E-v1.js
91 ms
css
58 ms
110 ms
108 ms
109 ms
106 ms
analytics
109 ms
_xyN3apAT_yRRDeqB3sPRg.woff
12 ms
scroll
114 ms
iframe_shim
25 ms
fancentric.fm SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fancentric.fm can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fancentric.fm 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.
fancentric.fm
Open Graph data is detected on the main page of Fancentric. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: