993 ms in total
22 ms
756 ms
215 ms
Visit factcheck.org now to see the best up-to-date Fact Check content for United States and also check out these interesting facts you probably never knew about factcheck.org
Visit factcheck.orgWe analyzed Factcheck.org page load time and found that the first response time was 22 ms and then it took 971 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
factcheck.org performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value5.7 s
16/100
25%
Value4.3 s
76/100
10%
Value1,030 ms
26/100
30%
Value0.172
69/100
15%
Value6.2 s
61/100
10%
22 ms
36 ms
33 ms
27 ms
44 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Factcheck.org, 42% (32 requests) were made to Cdn.factcheck.org and 33% (25 requests) were made to Origin.factcheck.org. The less responsive or slowest element that took the longest time to load (290 ms) relates to the external source Cdn.factcheck.org.
Page size can be reduced by 1.1 MB (28%)
4.0 MB
2.9 MB
In fact, the total size of Factcheck.org main page is 4.0 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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 75.5 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 75.5 kB or 76% of the original size.
Potential reduce by 393.1 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, Fact Check needs image optimization as it can save up to 393.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 383.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 383.4 kB or 65% of the original size.
Potential reduce by 273.5 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. Factcheck.org needs all CSS files to be minified and compressed as it can save up to 273.5 kB or 79% of the original size.
Number of requests can be reduced by 30 (43%)
69
39
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fact Check. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
factcheck.org
22 ms
www.factcheck.org
36 ms
style.css
33 ms
css
27 ms
css
44 ms
style-responsive.css
25 ms
wp-paginate.css.gzip
25 ms
jquery.js.gzip
26 ms
jquery-migrate.min.js.gzip
24 ms
addthis_widget.js
12 ms
output.css.gzip
20 ms
jquery.jplayer.min.js
100 ms
jquery.flexslider.min.js
33 ms
jquery.fancybox.pack.js
98 ms
jquery.fancybox-media.js
32 ms
jquery.mousewheel-3.0.6.pack.js
99 ms
jquery.theme.js
164 ms
wp-emoji-release.min.js
190 ms
ga.js
173 ms
TransparentWebLogo.png
275 ms
widgets.js
155 ms
DonateButton.png
166 ms
CNN-Debate.png
162 ms
Iraq-war2.png
164 ms
clinton_chicago.jpg
156 ms
supremecourt.jpg
164 ms
cbsgopdebate.jpg
164 ms
recruits-150x150.jpg
165 ms
CNN-Debate-150x150.png
165 ms
another_politician.jpg
168 ms
question.jpg
166 ms
berniesanders.jpg
166 ms
djtrump.jpg
165 ms
Aedes_aegypti-150x150.jpg
166 ms
tapper_-150x150.jpg
167 ms
Iraq-war2-150x150.png
172 ms
StandForTruth1.png
171 ms
factcheck-donationbutton.png
171 ms
schicheckrail.png
168 ms
PG2016frontpage_1.jpg
167 ms
CNN_factcheck-button_border.jpg
171 ms
EMAIL.png
171 ms
PartyLines.png
175 ms
FactCheckQuiz.png
175 ms
ViralSpiral.png
173 ms
OnTheAir.png
290 ms
Mailbag.png
175 ms
FlackCheck.png
249 ms
facebook_32.png
147 ms
tumblr_32.png
150 ms
twitter_32.png
149 ms
rss_32.png
156 ms
email_32.png
154 ms
sprite-h.png
153 ms
grad-page.png
163 ms
sidebar-right.png
162 ms
hr.png
162 ms
glass.png
166 ms
more-link.png
166 ms
TinyCheck.png
165 ms
nav-alt.png
168 ms
hr-light.png
167 ms
footer-to-top.png
169 ms
300lo.json
117 ms
QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf
92 ms
cj2hUnSRBhwmSPr9kS589-LrC4Du4e_yfTJ8Ol60xk0.ttf
92 ms
c92rD_x0V1LslSFt3-QEpmsGzsqhEorxQDpu60nfWEc.ttf
93 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
90 ms
League_Gothic-webfont.woff
91 ms
sh.7c7179124ea24ac6ba46caac.html
87 ms
__utm.gif
42 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
51 ms
__utm.gif
42 ms
collect
93 ms
syndication
111 ms
309033871935148034
286 ms
factcheck.org accessibility score
factcheck.org 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
factcheck.org SEO score
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 Factcheck.org 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 Factcheck.org 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.
factcheck.org
Open Graph description is not detected on the main page of Fact Check. 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: