5.3 sec in total
201 ms
697 ms
4.4 sec
Visit facebookcensorship.com now to see the best up-to-date Facebook Censorship content and also check out these interesting facts you probably never knew about facebookcensorship.com
Documentation of blatant political and religious censorship and harassment by Facebook
Visit facebookcensorship.comWe analyzed Facebookcensorship.com page load time and found that the first response time was 201 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
facebookcensorship.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value5.7 s
16/100
25%
Value3.1 s
93/100
10%
Value210 ms
88/100
30%
Value0
100/100
15%
Value8.0 s
43/100
10%
201 ms
32 ms
137 ms
103 ms
73 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 72% of them (51 requests) were addressed to the original Facebookcensorship.com, 11% (8 requests) were made to Apis.google.com and 8% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (342 ms) belongs to the original domain Facebookcensorship.com.
Page size can be reduced by 362.9 kB (15%)
2.5 MB
2.1 MB
In fact, the total size of Facebookcensorship.com main page is 2.5 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 62.1 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 62.1 kB or 73% of the original size.
Potential reduce by 77.7 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. Facebook Censorship images are well optimized though.
Potential reduce by 92.0 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 92.0 kB or 67% of the original size.
Potential reduce by 131.1 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. Facebookcensorship.com needs all CSS files to be minified and compressed as it can save up to 131.1 kB or 82% of the original size.
Number of requests can be reduced by 21 (31%)
67
46
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facebook Censorship. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
facebookcensorship.com
201 ms
plusone.js
32 ms
bootstrap.min.css
137 ms
bootstrap-responsive.min.css
103 ms
general_foundicons.css
73 ms
social_foundicons.css
71 ms
font-awesome.min.css
71 ms
css
24 ms
css
61 ms
css
69 ms
css
72 ms
css
69 ms
css
67 ms
custom.css
116 ms
cb=gapi.loaded_0
42 ms
Marriage8-19-15.jpg
72 ms
FBmarineCensor7-28-15.jpg
68 ms
FacebookHarassment2015-02-28.jpg
54 ms
FbookHarassment2015-02-22.jpg
120 ms
FBookPatriotNationSpank8-28.jpg
118 ms
FBcensor7-2-2013.jpg
129 ms
PayToSendMessageFB.jpg
128 ms
FBookNameHarassment03-13-20.jpg
122 ms
FBNameHarassment03-13-2013b.jpg
124 ms
FB-Harassment02-28-13.jpg
124 ms
FBHarassment02-28-13a.jpg
125 ms
FB-WorleyCensorship12-26-20.jpg
127 ms
PatriotGroupCensored.jpg
137 ms
FBHarassmentOnMyPage11-14-2.jpg
138 ms
FB-Seals_Screen-Shot-2012-10-28-at-3.54.jpg
269 ms
FBThreat10-13-2012.jpg
167 ms
FB-harassment10-8-2012.jpg
167 ms
Blocked08-202012.jpg
176 ms
DebaterFBscreen08202012.jpg
162 ms
FB-Block8-20-2012.jpg
163 ms
FBThreat8-20-2012.jpg
267 ms
FBthreat2012-06-20.jpg
270 ms
FB-threat04-28-2012.jpg
267 ms
Fbook-KeithStarnes4-15-2012.jpg
270 ms
FacebookCensorship3-2-2012.jpg
272 ms
FB-Harassment-BLOCKED10-28-.jpg
258 ms
FB-deleting-discussions10-3.jpg
261 ms
Facebook-censorship-9-28-20.jpg
264 ms
Facebook-Censorship-threat-.jpg
263 ms
Facebook-Threat--8-17-2011.jpg
262 ms
GodvineCensorship7-28-2011.jpg
258 ms
FB-Harassment7-11-2011.jpg
342 ms
asrbutton.png
56 ms
fwsbutton11.gif
30 ms
jquery.min.js
322 ms
bootstrap.min.js
243 ms
default.js
291 ms
ImpersonationOfSteveWinter7-9-2011.jpg
278 ms
FB-censorship-Page-ads5-30-.jpg
295 ms
12-29-2010Screenshot-Joseph.jpg
318 ms
FacebookCensorship11-3-2010.jpg
270 ms
Censorship-Obama-Facebook-1.jpg
269 ms
Facebook-NRA-censorship-7-1.jpg
271 ms
Facebook-Censorship-9-29-20.jpg
269 ms
Censorship-Screenshot-Faceb.jpg
264 ms
back.gif
279 ms
ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
10 ms
cb=gapi.loaded_1
18 ms
fastbutton
89 ms
postmessageRelay
52 ms
3193398744-postmessagerelay.js
31 ms
rpc:shindig_random.js
41 ms
cb=gapi.loaded_0
15 ms
cb=gapi.loaded_1
32 ms
grlryt2bdKIyfMSOhzd1eA.woff
42 ms
cb=gapi.loaded_0
6 ms
facebookcensorship.com accessibility score
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
facebookcensorship.com 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
Browser errors were logged to the console
Page has valid source maps
facebookcensorship.com 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
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facebookcensorship.com 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 Facebookcensorship.com 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.
facebookcensorship.com
Open Graph description is not detected on the main page of Facebook Censorship. 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: