2.2 sec in total
160 ms
911 ms
1.1 sec
Click here to check amazing Classic Fanstory content for United Kingdom. Otherwise, check out these important facts you probably never knew about classic.fanstory.com
FanStory has been helping writers of all skill levels since the year 2000. You can get feedback for your writing, enter writing contests, and be a part of an online writing community.
Visit classic.fanstory.comWe analyzed Classic.fanstory.com page load time and found that the first response time was 160 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
classic.fanstory.com performance score
160 ms
48 ms
31 ms
30 ms
30 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 71% of them (65 requests) were addressed to the original Classic.fanstory.com, 18% (17 requests) were made to Fanartreview.com and 2% (2 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (730 ms) relates to the external source Fanstory.com.
Page size can be reduced by 430.2 kB (18%)
2.3 MB
1.9 MB
In fact, the total size of Classic.fanstory.com main page is 2.3 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.9 MB which makes up the majority of the site volume.
Potential reduce by 140.6 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 140.6 kB or 84% of the original size.
Potential reduce by 86.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. Classic Fanstory images are well optimized though.
Potential reduce by 184.0 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 184.0 kB or 70% of the original size.
Potential reduce by 19.4 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. Classic.fanstory.com needs all CSS files to be minified and compressed as it can save up to 19.4 kB or 82% of the original size.
Number of requests can be reduced by 26 (29%)
91
65
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Classic Fanstory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
classic.fanstory.com
160 ms
nodefire.js
48 ms
standard2.css
31 ms
standard.css
30 ms
stylesmenunew.css
30 ms
styles.css
29 ms
ocscript5.js
74 ms
style.css
36 ms
page.js
8 ms
jquery-1.3.2.js
192 ms
jquery.capSlide.js
15 ms
sdk.js
135 ms
t-5309744-53707.jpg
295 ms
imgeastr.jpg
730 ms
t-7757814-123101.jpg
292 ms
t-5413998-471344.jpg
292 ms
t-5406084-193332.jpg
288 ms
t-3968486-115563.jpg
288 ms
t-9934557-467726.jpg
291 ms
3031303lily-close.jpg
365 ms
t-5316846-151183.jpg
313 ms
t-4614992-112679.jpg
293 ms
t-2535418-151942.jpg
292 ms
t-4997678-111805.jpg
307 ms
t-8045863-410521.jpg
312 ms
t-2240091-210219.jpg
448 ms
t-9234577-464225.jpg
345 ms
t-7507814-159472.jpg
348 ms
t-8667266-240063.jpg
349 ms
t-4384090-118442.jpg
349 ms
logonew.png
125 ms
arrow1_down.gif
129 ms
mymes.png
129 ms
mywr.png
128 ms
myrd.gif
125 ms
smspcr.gif
156 ms
btnReadMenu.png
154 ms
btnSkipMenu.png
155 ms
btnMoreOptionsMenu.png
150 ms
btnJoinIn.gif
256 ms
btnLogin.gif
258 ms
btnMrCnts.gif
257 ms
spacer.gif
258 ms
sp2.png
259 ms
sp1.png
259 ms
sp3.png
260 ms
plyvidl.png
264 ms
strfull.gif
260 ms
star+.gif
260 ms
1158593-5473.jpg
262 ms
6954732-3455.jpg
261 ms
2262397-3818.jpg
264 ms
nostar+.gif
263 ms
1801330-3807.jpg
263 ms
5364632-8836.jpg
266 ms
6324014-69.jpg
264 ms
9918657-658.jpg
265 ms
btnFllLstng.gif
266 ms
5651553-2109.jpg
266 ms
965438-9826.jpg
271 ms
2347150-8083.jpg
266 ms
5325535-998.jpg
267 ms
7392755-1644.jpg
269 ms
5411196-8693.jpg
359 ms
sm13.html
265 ms
widgets.js
185 ms
4067555-9637.jpg
224 ms
7832364-3498.jpg
285 ms
9027655-5706.jpg
220 ms
9394597-5467.jpg
181 ms
1692859-6567.jpg
181 ms
9736374-785.jpg
193 ms
2386995-7648.jpg
190 ms
4735454-1382.jpg
216 ms
1559973-4211.jpg
216 ms
ldyrd2e.jpg
111 ms
inftny2.gif
110 ms
btnMoreFanStoryContests.gif
130 ms
btnMoreFanArtReviewContests.gif
129 ms
fsclsins.jpg
128 ms
btnlrnmre.jpg
127 ms
btnCntsInf.gif
127 ms
btnShr2.gif
146 ms
box2_bodyat.png
145 ms
box2_headat.png
145 ms
box1_bodyat.png
144 ms
box3_headt.png
141 ms
167 ms
xd_arbiter.php
47 ms
xd_arbiter.php
68 ms
ga.js
46 ms
__utm.gif
30 ms
classic.fanstory.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classic.fanstory.com 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 Classic.fanstory.com 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.
classic.fanstory.com
Open Graph description is not detected on the main page of Classic Fanstory. 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: