4.4 sec in total
213 ms
3.9 sec
266 ms
Welcome to freespeech.org homepage info - get ready to check Free Speech best content for United States right away, or after learning these important things about freespeech.org
Free Speech TV is a 24-hour television network and multi-platform digital news source, currently available in 37 million television homes nationwide.
Visit freespeech.orgWe analyzed Freespeech.org page load time and found that the first response time was 213 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
freespeech.org performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value3.6 s
60/100
25%
Value3.5 s
88/100
10%
Value0 ms
100/100
30%
Value0.017
100/100
15%
Value3.6 s
91/100
10%
213 ms
26 ms
59 ms
91 ms
89 ms
Our browser made a total of 166 requests to load all elements on the main page. We found that 78% of them (130 requests) were addressed to the original Freespeech.org, 5% (8 requests) were made to and 2% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Livestream.com.
Page size can be reduced by 2.4 MB (50%)
4.8 MB
2.4 MB
In fact, the total size of Freespeech.org main page is 4.8 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. Javascripts take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 65.3 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 65.3 kB or 81% of the original size.
Potential reduce by 70.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. Free Speech images are well optimized though.
Potential reduce by 1.9 MB
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 1.9 MB or 73% of the original size.
Potential reduce by 360.2 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. Freespeech.org needs all CSS files to be minified and compressed as it can save up to 360.2 kB or 83% of the original size.
Number of requests can be reduced by 110 (71%)
154
44
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Free Speech. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
www.freespeech.org
213 ms
system.base.css
26 ms
system.menus.css
59 ms
system.messages.css
91 ms
system.theme.css
89 ms
date.css
89 ms
datepicker.1.7.css
91 ms
field.css
195 ms
node.css
92 ms
rpx_widgets.css
241 ms
user.css
182 ms
views.css
111 ms
browser_update_popup.css
111 ms
ctools.css
114 ms
facebook_pull.css
561 ms
nice_menus.css
137 ms
nice_menus_default.css
139 ms
black_drop.css
171 ms
quicktabs.css
372 ms
feedback_tab.css
198 ms
stylesheet.css
204 ms
actioncalendar.css
217 ms
menu.css
222 ms
frontpage.css
230 ms
mediapages.css
242 ms
secondarypages.css
248 ms
search.css
472 ms
admin.css
260 ms
alpha-reset.css
267 ms
alpha-mobile.css
272 ms
alpha-alpha.css
285 ms
formalize.css
324 ms
omega-text.css
298 ms
omega-branding.css
311 ms
omega-menu.css
559 ms
omega-forms.css
339 ms
oay0glg.js
133 ms
omega-visuals.css
521 ms
global.css
703 ms
freespeech-freespeech-default-normal.css
344 ms
freespeech-default-normal-12.css
337 ms
jquery.js
409 ms
jquery.once.js
418 ms
drupal.js
434 ms
jquery.cookie.js
529 ms
jquery.form.js
465 ms
ajax.js
448 ms
detect.js
474 ms
progress.js
450 ms
browser_update_popup.js
453 ms
dashlet.js
429 ms
grid.js
1069 ms
playerAjax.js
420 ms
jwplayer.js
471 ms
submit-form-tweak.js
422 ms
implementJwPlayer.js
419 ms
superfish.js
420 ms
jquery.bgiframe.min.js
421 ms
jquery.hoverIntent.minified.js
427 ms
nice_menus.js
426 ms
base.js
432 ms
black_drop.js
934 ms
ajax_view.js
425 ms
quicktabs.js
420 ms
viewer-comments.js
417 ms
vignettes_js_behavior_rotator.js
446 ms
googleanalytics.js
433 ms
fstv_small_navigation.js
421 ms
video-banner-animation.js
420 ms
video-dynamic-loader.js
380 ms
livestream-pause.js
887 ms
JQuery.Cycle.js
907 ms
fstv_iab_rotator.js
303 ms
timezone-controls.js
1021 ms
jquery.cookie.js
299 ms
mobile-timezone-controls.js
951 ms
mobile-schedule-block.js
823 ms
front-page-schedule-block.js
725 ms
main-menu-tweaks.js
804 ms
newsletter-tweak.js
746 ms
jquery.formalize.js
772 ms
omega-mediaqueries.js
762 ms
analytics.js
53 ms
d
146 ms
collect
10 ms
collect
52 ms
player
1197 ms
fstv-lattice.png
97 ms
fstv-top-bar.png
69 ms
video-player-title-gradient.png
67 ms
main-menu-active.png
69 ms
pipe-main-menu.png
304 ms
facebook-color.png
67 ms
twitter-color.png
96 ms
youtube-color.png
94 ms
search-bar-long.png
95 ms
search-icon.png
97 ms
fstv-logo_1_0.png
153 ms
fstv%20top%20banner.png
303 ms
video-player-title-gradient-tall.png
119 ms
video-player-quicktabs-active.png
117 ms
black-drop.png
299 ms
prev-bg.jpg
300 ms
next-bg.jpg
144 ms
see-full-schedule-btn.png
461 ms
giant%20slayer%20ad.png
319 ms
Screen%20Shot%202016-02-28%20at%2010.33.07%20PM.png
301 ms
icon-full-video.png
299 ms
RubioTrumpHoustonDebate640.png
302 ms
Screen%20Shot%202016-02-26%20at%2011.52.09%20AM.png
303 ms
BLM-Clinton-SC1-620x412.jpg
300 ms
Screen%20Shot%202016-02-26%20at%2011.47.59%20AM.png
302 ms
trump_2.jpg
301 ms
Screen%20Shot%202016-02-26%20at%2011.20.15%20AM.png
306 ms
Screen%20Shot%202016-02-26%20at%209.43.35%20AM.png
330 ms
button-more-link.png
314 ms
collection-frame.png
459 ms
hartmann%20thumbnail_0.png
329 ms
stephanie%20miller%20show%20thumbnail_0.png
485 ms
democracy%20now%20thumbnail_0.png
331 ms
bill%20press%20show%20thumbnail_0.png
591 ms
ring%20of%20fire%20thumbnail_2.png
349 ms
rpx.js
41 ms
gay%20usa%20thumbnail_0.png
308 ms
2XzJzDyloUAAAA=
9 ms
9DjgY3sdhRxx1zHEnnHTKaWecdc55F1yU7ZLLrrjqmutuyHHTLbfDG7vrnvseeCjXI3nyPfZEgacKPfNckRdeeuW1N94q9s57H34AuaVuywAA
10 ms
smear.jpg
330 ms
footer-gradient.jpg
420 ms
footer-banner-bg.png
366 ms
fstv-channel-sprite.png
391 ms
social-media-sprite.png
395 ms
news-letter-text-bg.png
396 ms
news-letter-submit-bg.png
400 ms
our-work.png
412 ms
rpx.js
58 ms
feedback-button.png
413 ms
block_1
598 ms
black-drop-gradient.png
244 ms
0OOBjex2FHHHXMcSecdMppZ5x1znkXXJTtksuuuOqa627IcdMtt8Mbu+ue+x54KNcjefI99kSBpwo981yRF1565bU33ir2znsffgC5pW7LAAA=
19 ms
0OOBjex2FHHHXMcSecdMppZ5x1znkXXJTtksuuuOqa627IcdMtt8Mbu+ue+x54KNcjefI99kSBpwo981yRF1565bU33ir2znsffgC5pW7LAAA=
17 ms
2J3JOLS4A
17 ms
Ynck4tLgA=
17 ms
2J3JOLS4A
16 ms
9idyTi0uAA==
15 ms
black-drop-selector.png
234 ms
transparent-preloader.png
371 ms
p.gif
125 ms
player_embed-2a04e27da6997d37e65783bc06e82623.css
80 ms
require-cbfc3f690e2109e37e09aefd8fe40332.js
145 ms
gtm.js
87 ms
beacon.js
55 ms
munchkin.js
58 ms
player-e3240c6d06b8b0ecb3145234a21ff2f8.js
73 ms
ga.js
220 ms
collect
25 ms
collect
25 ms
munchkin.js
19 ms
ga-audiences
183 ms
mixpanel-2.2.min.js
159 ms
cast_sender.js
106 ms
leastloaded.json
51 ms
e6e1ccbf-4564-4255-b109-ed93cc2a078f_224605.jpg
86 ms
__utm.gif
22 ms
__utm.gif
25 ms
38 ms
nr-852.min.js
45 ms
freespeech.org 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
freespeech.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
freespeech.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Freespeech.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 Freespeech.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.
freespeech.org
Open Graph description is not detected on the main page of Free Speech. 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: