2.4 sec in total
18 ms
2.3 sec
143 ms
Welcome to fictfact.com homepage info - get ready to check Fictfact best content for Canada right away, or after learning these important things about fictfact.com
FictFact will keep track of the books you're reading and give you a list of the books you need to read next.
Visit fictfact.comWe analyzed Fictfact.com page load time and found that the first response time was 18 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
fictfact.com performance score
18 ms
636 ms
138 ms
13 ms
11 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 17% of them (6 requests) were addressed to the original Fictfact.com, 11% (4 requests) were made to Apis.google.com and 8% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (748 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 254.4 kB (68%)
375.7 kB
121.3 kB
In fact, the total size of Fictfact.com main page is 375.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 218.9 kB which makes up the majority of the site volume.
Potential reduce by 23.8 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 3.7 kB, which is 11% 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 23.8 kB or 72% of the original size.
Potential reduce by 1.3 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. Obviously, Fictfact needs image optimization as it can save up to 1.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 130.4 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 130.4 kB or 60% of the original size.
Potential reduce by 99.0 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. Fictfact.com needs all CSS files to be minified and compressed as it can save up to 99.0 kB or 84% of the original size.
Number of requests can be reduced by 17 (50%)
34
17
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fictfact. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
fictfact.com
18 ms
www.fictfact.com
636 ms
bootstrap.min.css
138 ms
jquery-1.8.2.min.js
13 ms
bootstrap.min.js
11 ms
register.js
11 ms
mainstyle.css
10 ms
google_service.js
24 ms
google_ads.js
21 ms
quant.js
41 ms
fictfact-white-on-brown-text-only.png
38 ms
ir
41 ms
btn_donate_LG.gif
46 ms
analytics.js
48 ms
client:plusone.js
110 ms
all.js
285 ms
pixel;r=1413188308;a=p-62jOTq_XJVRJs;fpan=1;fpa=P0-601811957-1456766188209;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456766188208;tzo=-180;ref=;url=http%3A%2F%2Fwww.fictfact.com%2F;ogl=
15 ms
collect
14 ms
cb=gapi.loaded_0
42 ms
postmessageRelay
35 ms
cb=gapi.loaded_1
13 ms
api.js
27 ms
core:rpc:shindig.random:shindig.sha1.js
137 ms
2536007149-postmessagerelay.js
107 ms
141 ms
xd_arbiter.php
216 ms
xd_arbiter.php
421 ms
auth
52 ms
2637085964-postmessage.js
11 ms
nr-852.min.js
23 ms
f9205bfa33
51 ms
xd_arbiter.php
141 ms
login_button.php
76 ms
yD3uLzdmZ08.js
617 ms
pO2d5bFWS8j.png
708 ms
7_Tav3rWEg4.gif
748 ms
fictfact.com SEO score
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fictfact.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fictfact.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
fictfact.com
Open Graph description is not detected on the main page of Fictfact. 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: