1.6 sec in total
274 ms
1.2 sec
114 ms
Visit factly.com now to see the best up-to-date Factly content and also check out these interesting facts you probably never knew about factly.com
Factly has a huge collection of articles on various subjects. Just click on the appropriate category to read the articles and free reprint them.
Visit factly.comWe analyzed Factly.com page load time and found that the first response time was 274 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
factly.com performance score
274 ms
272 ms
94 ms
152 ms
154 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 94% of them (32 requests) were addressed to the original Factly.com, 3% (1 request) were made to Addme.com and 3% (1 request) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (371 ms) relates to the external source Addme.com.
Page size can be reduced by 63.6 kB (47%)
134.1 kB
70.5 kB
In fact, the total size of Factly.com main page is 134.1 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. Only 10% of websites need less resources to load. Javascripts take 57.3 kB which makes up the majority of the site volume.
Potential reduce by 8.7 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 2.3 kB, which is 20% 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 8.7 kB or 77% of the original size.
Potential reduce by 939 B
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. Factly images are well optimized though.
Potential reduce by 37.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 37.7 kB or 66% of the original size.
Potential reduce by 16.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. Factly.com needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 79% of the original size.
Number of requests can be reduced by 18 (60%)
30
12
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Factly. 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 CSS and as a result speed up the page load time.
factly.com
274 ms
www.factly.com
272 ms
mainstyle.css
94 ms
screen.css
152 ms
global.css
154 ms
splash.css
153 ms
jquery-1.3.2.min.js
285 ms
reset.css
71 ms
typography.css
71 ms
forms.css
72 ms
plugins.css
68 ms
button1-bm.gif
371 ms
logo_large.gif
70 ms
bg_search.gif
68 ms
btn_search_large.gif
69 ms
xyz_pic_1.jpg
132 ms
xyz_pic_2.jpg
70 ms
xyz_pic_3.jpg
131 ms
xyz_pic_4.jpg
133 ms
ico_caret.gif
135 ms
favorites.gif
169 ms
delicious.png
179 ms
google.png.jpg
212 ms
furl.png
212 ms
netscape.gif
217 ms
newsvine.png
218 ms
rawsugar.png
254 ms
reddit.png
278 ms
squidoo.png
277 ms
stumbled.png.gif
281 ms
technorati.png
282 ms
yahoo.png
294 ms
print.css
67 ms
button1-bm.gif
5 ms
factly.com SEO score
N/A
EN
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Factly.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), while the claimed language is English. Our system also found out that Factly.com main page’s claimed encoding is windows-1252. 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.
factly.com
Open Graph description is not detected on the main page of Factly. 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: