Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

classic.fanstory.com

Share your poetry and all your writing. Get feedback for your writing.

Page Load Speed

2.2 sec in total

First Response

160 ms

Resources Loaded

911 ms

Page Rendered

1.1 sec

classic.fanstory.com screenshot

About Website

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.com

Key Findings

We 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.

Performance Metrics

classic.fanstory.com performance score

0

Network Requests Diagram

classic.fanstory.com

160 ms

nodefire.js

48 ms

standard2.css

31 ms

standard.css

30 ms

stylesmenunew.css

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 Optimization Overview & Recommendations

Page size can be reduced by 430.2 kB (18%)

Content Size

2.3 MB

After Optimization

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.

HTML Optimization

-84%

Potential reduce by 140.6 kB

  • Original 167.2 kB
  • After minification 163.9 kB
  • After compression 26.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.

Image Optimization

-5%

Potential reduce by 86.2 kB

  • Original 1.9 MB
  • After minification 1.8 MB

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.

JavaScript Optimization

-70%

Potential reduce by 184.0 kB

  • Original 262.8 kB
  • After minification 214.9 kB
  • After compression 78.8 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.

CSS Optimization

-82%

Potential reduce by 19.4 kB

  • Original 23.6 kB
  • After minification 18.9 kB
  • After compression 4.3 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.

Requests Breakdown

Number of requests can be reduced by 26 (29%)

Requests Now

91

After Optimization

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.

SEO Factors

classic.fanstory.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: