12.8 sec in total
186 ms
2.5 sec
10.2 sec
Click here to check amazing Fanstory content for United Kingdom. Otherwise, check out these important facts you probably never knew about 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 fanstory.comWe analyzed Fanstory.com page load time and found that the first response time was 186 ms and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fanstory.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value13.2 s
0/100
25%
Value10.8 s
6/100
10%
Value7,120 ms
0/100
30%
Value0.002
100/100
15%
Value29.2 s
0/100
10%
186 ms
323 ms
144 ms
136 ms
118 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 70% of them (86 requests) were addressed to the original Fanstory.com, 14% (17 requests) were made to Fanartreview.com and 3% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (777 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 1.2 MB (44%)
2.7 MB
1.5 MB
In fact, the total size of Fanstory.com main page is 2.7 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. 80% 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. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 114.1 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. This page needs HTML code to be minified as it can gain 16.3 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 114.1 kB or 84% of the original size.
Potential reduce by 85.9 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. Fanstory images are well optimized though.
Potential reduce by 416.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 416.0 kB or 66% of the original size.
Potential reduce by 567.9 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. Fanstory.com needs all CSS files to be minified and compressed as it can save up to 567.9 kB or 86% of the original size.
Number of requests can be reduced by 47 (39%)
119
72
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 29 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.fanstory.com
186 ms
sdk.js
323 ms
jquery.js
144 ms
smart-forms.css
136 ms
green.css
118 ms
css
108 ms
style.css
215 ms
_mobile.css
129 ms
karma-cool-blue.css
128 ms
secondary-cool-blue.css
130 ms
templates.css
199 ms
hoverex-all.css
207 ms
jquery-2.0.1.min.js
260 ms
jquery.hoverex.min.js
206 ms
jquery.foobar.2.1.css
211 ms
jquery.foobar.2.1.min.js
259 ms
logonew.png
181 ms
ccslider.css
179 ms
style.css
177 ms
t-5334518-452840.jpg
178 ms
t-4652468-257020.jpg
193 ms
dl2.jpg
178 ms
mainfivestar.jpg
236 ms
jquery.easing.1.3.min.js
192 ms
jquery.ccslider-3.0.2.min.js
434 ms
SHOWTIMEBOOK.JPG
193 ms
7482974-8985.jpg
193 ms
rvwsnws.jpg
334 ms
nwsend.jpg
346 ms
btnsnup.png
233 ms
fbsignup.png
234 ms
t-4412794-168616.jpg
189 ms
t-8963129-127613.jpg
231 ms
t-2926793-343025.jpg
191 ms
t-9762036-177361.jpg
380 ms
t-4860918-235476.jpg
336 ms
t-9499695-115127.jpg
335 ms
strfull.gif
322 ms
star+.gif
332 ms
4416385-622.jpg
341 ms
9907763-8484.jpg
343 ms
1907417-6982.jpg
346 ms
241849-5514.jpg
344 ms
nostar+.gif
345 ms
939562-2780.jpg
345 ms
6295347-338.jpg
346 ms
t-6817134-246738.jpg
316 ms
t-943762-170195.jpg
305 ms
t-5316846-151183.jpg
315 ms
t-3796851-186062.jpg
318 ms
t-2275107-124838.jpg
335 ms
t-7014888-359691.jpg
329 ms
t-4028708-170921.jpg
320 ms
t-7607989-391004.jpg
331 ms
t-9122897-410030.jpg
333 ms
4186594-4998.jpg
327 ms
show_ads.js
23 ms
custom-main.js
327 ms
superfish.js
320 ms
jquery.flexslider.js
321 ms
jquery.fitvids.js
319 ms
scrollWatch.js
309 ms
css
98 ms
jquery.isotope.js
241 ms
jquery.ui.core.min.js
241 ms
jquery.ui.widget.min.js
238 ms
jquery.ui.tabs.min.js
237 ms
jquery.ui.accordion.min.js
197 ms
jquery.prettyPhoto.js
191 ms
2450868-7758.jpg
189 ms
2794827-3768.jpg
190 ms
7856827-6164.jpg
190 ms
262016-3017.jpg
191 ms
8622855-1971.jpg
190 ms
4014661-7001.jpg
190 ms
3218102-7255.jpg
174 ms
4345170-7093.jpg
175 ms
2584523-8346.jpg
175 ms
6408096-6661.jpg
135 ms
6675445-5103.jpg
135 ms
9136417-3728.jpg
47 ms
8283198-3668.jpg
40 ms
8644841-2078.jpg
40 ms
4030954-3099.jpg
48 ms
748895-9770.jpg
38 ms
945918-8330.jpg
37 ms
8118736-2674.jpg
36 ms
2801453-1211.jpg
85 ms
5239179-4536.jpg
83 ms
7261875-6048.jpg
83 ms
9708132-954.jpg
83 ms
6882323-975.jpg
75 ms
5125797-5164.jpg
74 ms
379354-7863.jpg
73 ms
global-sprite.png
146 ms
loading.gif
146 ms
702dSPDCJf4
110 ms
bg-div-main.png
147 ms
bg-div-footer-top.png
146 ms
www-embed-player-vfltSWGRn.css
144 ms
www-embed-player.js
222 ms
base.js
283 ms
xd_arbiter.php
777 ms
AUrdvhejKSJD2XN0WEoLkNJn8VW-ISfFFTHwdQR0Ws4.js
56 ms
ad_status.js
76 ms
ca-pub-0044404662076377.js
30 ms
zrt_lookup.html
171 ms
show_ads_impl.js
170 ms
bg-footer-bottom-cool-blue.png
153 ms
ads
296 ms
analytics.js
13 ms
osd.js
17 ms
collect
23 ms
loader0.js
13 ms
small-white-arrow.png
76 ms
shadow.png
23 ms
shadow-button.png
23 ms
left-arrow.png
29 ms
right-arrow.png
29 ms
link-active.png
30 ms
link-bg.png
29 ms
slider-pause.png
29 ms
3332-705-10-3778.js
18 ms
fanstory.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fanstory.com 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fanstory.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanstory.com 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 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.
fanstory.com
Open Graph description is not detected on the main page of 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: