3.4 sec in total
141 ms
3.1 sec
142 ms
Visit factlets.info now to see the best up-to-date Factlets content and also check out these interesting facts you probably never knew about factlets.info
Earthquake shortens day
Visit factlets.infoWe analyzed Factlets.info page load time and found that the first response time was 141 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
factlets.info performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value5.7 s
16/100
25%
Value6.3 s
42/100
10%
Value2,250 ms
6/100
30%
Value0.01
100/100
15%
Value14.3 s
9/100
10%
141 ms
77 ms
53 ms
53 ms
90 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 26% of them (14 requests) were addressed to the original Factlets.info, 9% (5 requests) were made to Platform.twitter.com and 8% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Henleyglobal.com.
Page size can be reduced by 85.6 kB (44%)
194.4 kB
108.8 kB
In fact, the total size of Factlets.info main page is 194.4 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. 45% of websites need less resources to load. Javascripts take 122.2 kB which makes up the majority of the site volume.
Potential reduce by 35.4 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 35.4 kB or 78% of the original size.
Potential reduce by 746 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. Factlets images are well optimized though.
Potential reduce by 49.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 49.4 kB or 40% of the original size.
Potential reduce by 0 B
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.
Number of requests can be reduced by 21 (53%)
40
19
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Factlets. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
factlets.info
141 ms
visa.html
77 ms
uncompressed_style.css
53 ms
uncompressed_functions.js
53 ms
factletsinfo.js
90 ms
facebook.js
94 ms
widget.js
60 ms
factlets.js
99 ms
widgets.js
9 ms
page.js
6 ms
brand
14 ms
show_ads.js
14 ms
brand
23 ms
factlets.php
148 ms
cm
21 ms
cm
23 ms
hvri_2010_graph.png
460 ms
share_save_171_16.png
33 ms
image-3839355-10769819
34 ms
ir
35 ms
rss.gif
52 ms
email.gi
52 ms
KenJennings.gif
100 ms
PIV_Workaholics_S4_Hero_728x90-2._V345088863_.jpg
47 ms
30 ms
30 ms
gc-assoc-holiday_728x90._V165290625_.gif
47 ms
sm13.html
30 ms
10769819-1417806965542
51 ms
ca-pub-9278060909505395.js
84 ms
zrt_lookup.html
130 ms
show_ads_impl.js
80 ms
ga.js
7 ms
email.gif
68 ms
like.php
296 ms
ga.js
51 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
42 ms
__utm.gif
17 ms
factlets.info
82 ms
activity.php
153 ms
__utm.gif
110 ms
ads
48 ms
osd.js
40 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
25 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
32 ms
info.json
103 ms
Poach.html
50 ms
qeKvIRsJabD.js
23 ms
LVx-xkvaJ0b.png
15 ms
hvri_2010_graph.png
553 ms
jot.html
7 ms
267 ms
1280 ms
factlets.info 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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
factlets.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
factlets.info SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Factlets.info 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 Factlets.info 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.
factlets.info
Open Graph description is not detected on the main page of Factlets. 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: