4 sec in total
61 ms
3.4 sec
538 ms
Click here to check amazing Cc Great Fire content for Taiwan. Otherwise, check out these important facts you probably never knew about cc.greatfire.org
Welcome to the GreatFire Circumvention Central. We test all services inside the Great Firewall of China.
Visit cc.greatfire.orgWe analyzed Cc.greatfire.org page load time and found that the first response time was 61 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
cc.greatfire.org performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value3.6 s
60/100
25%
Value13.7 s
2/100
10%
Value16,590 ms
0/100
30%
Value0.517
15/100
15%
Value27.6 s
0/100
10%
61 ms
302 ms
526 ms
50 ms
954 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 44% of them (18 requests) were addressed to the original Cc.greatfire.org, 27% (11 requests) were made to Platform.twitter.com and 5% (2 requests) were made to Code.highcharts.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Cc.greatfire.org.
Page size can be reduced by 120.1 kB (31%)
383.5 kB
263.4 kB
In fact, the total size of Cc.greatfire.org main page is 383.5 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 221.4 kB which makes up the majority of the site volume.
Potential reduce by 22.9 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 22.9 kB or 70% of the original size.
Potential reduce by 0 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. Cc Great Fire images are well optimized though.
Potential reduce by 97.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 97.0 kB or 44% of the original size.
Potential reduce by 174 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. Cc.greatfire.org has all CSS files already compressed.
Number of requests can be reduced by 23 (64%)
36
13
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cc Great Fire. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
cc.greatfire.org
61 ms
cc.greatfire.org
302 ms
en
526 ms
css
50 ms
common.css
954 ms
chartist.min.css
289 ms
jquery-ui.min.css
283 ms
script.js
39 ms
cc-logo-300.png
289 ms
mc-validate.js
63 ms
jquery-1.11.3.min.js
284 ms
jquery-ui.min.js
287 ms
checkout.js
561 ms
common.js
548 ms
chartist.min.js
542 ms
highcharts.js
59 ms
highcharts-more.js
79 ms
phone.jpg
538 ms
greatfire-logo.png
1239 ms
checkout.js
27 ms
background.jpg
257 ms
footer.png
277 ms
ajax-loader.gif
265 ms
AvenirLTStd-Book.woff
988 ms
widgets.js
57 ms
q.stripe.com
269 ms
analytics.js
47 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
47 ms
collect
39 ms
settings
109 ms
js
74 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
4 ms
GreatFireChina
1025 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
6 ms
runtime-b1c52fd0a13ead5fcf6b.js
15 ms
modules-96ebc7ac3ad66d681a3d.js
17 ms
main-babd9234dc048fb47339.js
25 ms
_app-a9c9f1a99e4414675fb1.js
93 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
98 ms
_buildManifest.js
113 ms
_ssgManifest.js
112 ms
cc.greatfire.org 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.
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
cc.greatfire.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cc.greatfire.org 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cc.greatfire.org 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 Cc.greatfire.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.
cc.greatfire.org
Open Graph data is detected on the main page of Cc Great Fire. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: