C-CEX.COM C-CEX.com - Crypto-currency exchange / MultiWallet


c-cex.com website information.

c-cex.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

No name server records were found.

and probably website c-cex.com is hosted by FASTLY - Fastly, US web hosting company. Check the complete list of other most popular websites hosted by FASTLY - Fastly, US hosting company.

According to Alexa traffic rank the highest website c-cex.com position was 15647 (in the world). The lowest Alexa rank position was 975128. Now website c-cex.com ranked in Alexa database as number 483552 (in the world).

Website c-cex.com Desktop speed measurement score (76/100) is better than the results of 61.81% of other sites shows that the page desktop performance can be improved.

c-cex.com Mobile usability score (70/100) is better than the results of 21.03% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of c-cex.com (62/100) is better than the results of 59.44% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-26-2024 483,552-3,011
Nov-25-2024 480,541-6,446
Nov-24-2024 474,09512,164
Nov-23-2024 486,259-13,658
Nov-22-2024 472,601-11,125
Nov-21-2024 461,47611,700
Nov-20-2024 473,1765,876

Advertisement

c-cex.com Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



c-cex.com whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Domain Name: C-CEX.COM
Registry Domain ID: 1840333801_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.ordertld.com
Registrar URL: http://www.ordertld.com
Updated Date: 2023-12-26T08:13:22Z
Creation Date: 2013-12-25T15:39:31Z
Registry Expiry Date: 2024-12-25T15:39:31Z
Registrar: CNOBIN INFORMATION TECHNOLOGY LIMITED
Registrar IANA ID: 3254
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.PARKINGCREW.NET
Name Server: NS2.PARKINGCREW.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-09-13T08:48:19Z

c-cex.com server information

Servers Location

IP Address
Country
Region
City

c-cex.com desktop page speed rank

Last tested: 2020-01-06


Desktop Speed Medium
76/100

c-cex.com Desktop Speed Test Quick Summary


priority - 16 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://cdn.syndication.twimg.com/widgets/timeline…&t=1684064&tz=GMT-0800 (5 minutes)
https://syndication.twitter.com/settings (10 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://c-cex.com/css/index.css (4 hours)
https://c-cex.com/css/style.css (4 hours)
https://c-cex.com/g.css (4 hours)
https://c-cex.com/i/cn.gif (4 hours)
https://c-cex.com/i/comodosecure.gif (4 hours)
https://c-cex.com/i/fr.gif (4 hours)
https://c-cex.com/i/gb.gif (4 hours)
https://c-cex.com/i/homebg.jpg (4 hours)
https://c-cex.com/i/i.gif (4 hours)
https://c-cex.com/i/l_silver.png (4 hours)
https://c-cex.com/i/mico_api.png (4 hours)
https://c-cex.com/i/mico_comm.png (4 hours)
https://c-cex.com/i/mico_fee.png (4 hours)
https://c-cex.com/i/mico_resp.png (4 hours)
https://c-cex.com/i/mico_sec.png (4 hours)
https://c-cex.com/i/mico_speed.png (4 hours)
https://c-cex.com/i/payeeraccept.png (4 hours)
https://c-cex.com/i/ru.gif (4 hours)
https://c-cex.com/js/amcharts.js (4 hours)
https://c-cex.com/js/canvas.js (4 hours)
https://c-cex.com/js/exporting.js (4 hours)
https://c-cex.com/js/highstock.js (4 hours)
https://c-cex.com/js/index.js (4 hours)
https://c-cex.com/js/jquery-2.1.4.min.js (4 hours)
https://c-cex.com/js/jquery-ui.min.js (4 hours)
https://c-cex.com/js/light.js (4 hours)
https://c-cex.com/js/serial.js (4 hours)
https://c-cex.com/js/vendor/d3-v2.js (4 hours)

priority - 10 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 10 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://c-cex.com/js/jquery-2.1.4.min.js
https://c-cex.com/js/jquery-ui.min.js
https://c-cex.com/js/highstock.js
https://c-cex.com/js/exporting.js
https://c-cex.com/js/vendor/d3-v2.js
https://c-cex.com/js/canvas.js
https://c-cex.com/js/index.js
https://c-cex.com/js/amcharts.js
https://c-cex.com/js/serial.js
https://c-cex.com/js/light.js

Optimize CSS Delivery of the following:

https://c-cex.com/g.css
https://c-cex.com/css/index.css
https://c-cex.com/css/style.css

priority - 2 Reduce server response time

In our test, your server responded in 0.43 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 1 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 10.8KiB (14% reduction).

Minifying https://c-cex.com/js/vendor/d3-v2.js could save 9KiB (13% reduction) after compression.
Minifying https://c-cex.com/js/index.js could save 1.7KiB (34% reduction) after compression.

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 6.3KiB (34% reduction).

Compressing https://c-cex.com/i/i.gif could save 1KiB (90% reduction).
Compressing https://c-cex.com/i/comodosecure.gif could save 958B (32% reduction).
Compressing https://pbs.twimg.com/profile_images/910586199521230848/9ZPMZ4Sm_normal.jpg could save 908B (47% reduction).
Compressing https://c-cex.com/i/payeeraccept.png could save 603B (20% reduction).
Compressing https://pbs.twimg.com/profile_images/589235535706656768/hboYQ-rP_normal.png could save 468B (18% reduction).
Compressing https://c-cex.com/i/fr.gif could save 440B (44% reduction).
Compressing https://c-cex.com/i/ru.gif could save 419B (42% reduction).
Compressing https://c-cex.com/i/gb.gif could save 406B (41% reduction).
Compressing https://c-cex.com/i/mico_api.png could save 348B (31% reduction).
Compressing https://c-cex.com/i/mico_comm.png could save 286B (29% reduction).
Compressing https://c-cex.com/i/mico_fee.png could save 157B (28% reduction).
Compressing https://c-cex.com/i/cn.gif could save 149B (26% reduction).
Compressing https://c-cex.com/i/mico_speed.png could save 122B (22% reduction).
Compressing https://c-cex.com/i/mico_resp.png could save 111B (26% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 550B (12% reduction).

Minifying https://c-cex.com/g.css could save 429B (11% reduction) after compression.
Minifying https://c-cex.com/css/index.css could save 121B (19% reduction) after compression.

c-cex.com Desktop Resources

Total Resources45
Number of Hosts7
Static Resources38
JavaScript Resources15
CSS Resources5

c-cex.com Desktop Resource Breakdown

c-cex.com mobile page speed rank

Last tested: 2018-05-12


Mobile Speed Bad
62/100

c-cex.com Mobile Speed Test Quick Summary


priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 10 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://c-cex.com/js/jquery-2.1.4.min.js
https://c-cex.com/js/jquery-ui.min.js
https://c-cex.com/js/highstock.js
https://c-cex.com/js/exporting.js
https://c-cex.com/js/vendor/d3-v2.js
https://c-cex.com/js/canvas.js
https://c-cex.com/js/index.js
https://c-cex.com/js/amcharts.js
https://c-cex.com/js/serial.js
https://c-cex.com/js/light.js

Optimize CSS Delivery of the following:

https://c-cex.com/g.css
https://c-cex.com/css/index.css
https://c-cex.com/css/style.css

priority - 21 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://cdn.syndication.twimg.com/widgets/timeline…&t=1695708&tz=GMT-0700 (5 minutes)
https://syndication.twitter.com/settings (10 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://c-cex.com/css/index.css (24 hours)
https://c-cex.com/css/style.css (24 hours)
https://c-cex.com/g.css (24 hours)
https://c-cex.com/i/cn.gif (24 hours)
https://c-cex.com/i/comodosecure.gif (24 hours)
https://c-cex.com/i/fr.gif (24 hours)
https://c-cex.com/i/gb.gif (24 hours)
https://c-cex.com/i/homebg.jpg (24 hours)
https://c-cex.com/i/i.gif (24 hours)
https://c-cex.com/i/l_silver.png (24 hours)
https://c-cex.com/i/mico_api.png (24 hours)
https://c-cex.com/i/mico_comm.png (24 hours)
https://c-cex.com/i/mico_fee.png (24 hours)
https://c-cex.com/i/mico_resp.png (24 hours)
https://c-cex.com/i/mico_sec.png (24 hours)
https://c-cex.com/i/mico_speed.png (24 hours)
https://c-cex.com/i/payeeraccept.png (24 hours)
https://c-cex.com/i/ru.gif (24 hours)
https://c-cex.com/js/amcharts.js (24 hours)
https://c-cex.com/js/canvas.js (24 hours)
https://c-cex.com/js/exporting.js (24 hours)
https://c-cex.com/js/highstock.js (24 hours)
https://c-cex.com/js/index.js (24 hours)
https://c-cex.com/js/jquery-2.1.4.min.js (24 hours)
https://c-cex.com/js/jquery-ui.min.js (24 hours)
https://c-cex.com/js/light.js (24 hours)
https://c-cex.com/js/serial.js (24 hours)
https://c-cex.com/js/vendor/d3-v2.js (24 hours)

priority - 4 Reduce server response time

In our test, your server responded in 0.20 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5.8KiB (31% reduction).

Compressing https://c-cex.com/i/i.gif could save 1KiB (90% reduction).
Compressing https://c-cex.com/i/comodosecure.gif could save 958B (32% reduction).
Compressing https://pbs.twimg.com/profile_images/589235535706656768/hboYQ-rP_bigger.png could save 855B (18% reduction).
Compressing https://c-cex.com/i/payeeraccept.png could save 603B (20% reduction).
Compressing https://c-cex.com/i/fr.gif could save 440B (44% reduction).
Compressing https://c-cex.com/i/ru.gif could save 419B (42% reduction).
Compressing https://c-cex.com/i/gb.gif could save 406B (41% reduction).
Compressing https://c-cex.com/i/mico_api.png could save 348B (31% reduction).
Compressing https://c-cex.com/i/mico_comm.png could save 286B (29% reduction).
Compressing https://c-cex.com/i/mico_fee.png could save 157B (28% reduction).
Compressing https://c-cex.com/i/cn.gif could save 149B (26% reduction).
Compressing https://c-cex.com/i/mico_speed.png could save 122B (22% reduction).
Compressing https://c-cex.com/i/mico_resp.png could save 111B (26% reduction).

c-cex.com Mobile Resources

Total Resources43
Number of Hosts6
Static Resources35
JavaScript Resources15
CSS Resources4

c-cex.com Mobile Resource Breakdown

c-cex.com mobile page usability

Last tested: 2018-05-12


Mobile Usability Medium
70/100

c-cex.com Mobile Usability Test Quick Summary


priority - 21 Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Login: renders only 5 pixels tall (13 CSS pixels).

Password: renders only 5 pixels tall (13 CSS pixels).

| renders only 6 pixels tall (16 CSS pixels).

Lost password renders only 6 pixels tall (16 CSS pixels).

CryptoCurrencies, and 1 others render only 8 pixels tall (20 CSS pixels).

Fiat trading,…n, API & more. renders only 6 pixels tall (16 CSS pixels).

Hot BTC markets: and 10 others render only 5 pixels tall (13 CSS pixels).

16.05 and 9 others render only 5 pixels tall (13 CSS pixels).

, and 8 others render only 5 pixels tall (13 CSS pixels).

Order advertising renders only 7 pixels tall (19 CSS pixels).

C-CEX exchange…authentication renders only 6 pixels tall (16 CSS pixels).

Our system is…mitting orders renders only 6 pixels tall (16 CSS pixels).

Our fully resp…es and tablets renders only 6 pixels tall (16 CSS pixels).

All trades hav…ifically noted renders only 6 pixels tall (16 CSS pixels).

Almost all fun…t our platform renders only 6 pixels tall (16 CSS pixels).

C-CEX exchange…ke new friends renders only 6 pixels tall (16 CSS pixels).

Apr 26, 2018 and 2 others render only 5 pixels tall (12 CSS pixels).

‎@CryptoCurrEncyX renders only 5 pixels tall (12 CSS pixels).

C-CEX.com and 2 others render only 5 pixels tall (14 CSS pixels).

@CryptoCurrEncyX and 2 others render only 5 pixels tall (13 CSS pixels).

Before sending…ddress at info and 2 others render only 5 pixels tall (14 CSS pixels).

bitcointalk.org/index.php?topi and 3 others render only 5 pixels tall (14 CSS pixels).

priority - 11 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <img id="gb" src="/i/gb.gif" class="hand"> is close to 1 other tap targets.

The tap target <img id="ru" src="/i/ru.gif" class="hand"> and 2 others are close to other tap targets.

The tap target <input type="text" name="login"> and 1 others are close to other tap targets.

The tap target <input type="submit"> is close to 2 other tap targets.

The tap target <a href="/?id=reg">Create account</a> is close to 1 other tap targets.

The tap target <a href="/?id=recover">Lost password</a> is close to 2 other tap targets.

The tap target <a href="/?p=ebh-btc">EBH: 16.05</a> and 8 others are close to other tap targets.

The tap target <a href="/?p=szc-btc">SZC: 13.72</a> and 8 others are close to other tap targets.

The tap target <a href="https://twitte…45148400357378" class="TweetAction Tw…dge web-intent"></a> and 1 others are close to other tap targets.

The tap target <a href="#" class="TweetAction Tw…-showShareMenu"></a> and 1 others are close to other tap targets.

The tap target <a href="https://t.co/fzODQ2HTfT" class="link customisable">https://bitcoi…#msg35676376 …</a> is close to 2 other tap targets.

The tap target <a href="https://t.co/fzODQ2HTfT" class="link customisable">https://bitcoi…#msg35676376 …</a> is close to 1 other tap targets.

priority - 10 Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

c-cex.com similar domains

Similar domains:
www.c-cex.com
www.c-cex.net
www.c-cex.org
www.c-cex.info
www.c-cex.biz
www.c-cex.us
www.c-cex.mobi
www.-cex.com
www.c-cex.com
www.x-cex.com
www.cx-cex.com
www.xc-cex.com
www.d-cex.com
www.cd-cex.com
www.dc-cex.com
www.f-cex.com
www.cf-cex.com
www.fc-cex.com
www.v-cex.com
www.cv-cex.com
www.vc-cex.com
www.ccex.com
www.c-ex.com
www.c-xex.com
www.c-cxex.com
www.c-xcex.com
www.c-dex.com
www.c-cdex.com
www.c-dcex.com
www.c-fex.com
www.c-cfex.com
www.c-fcex.com
www.c-vex.com
www.c-cvex.com
www.c-vcex.com
www.c-cx.com
www.c-cwx.com
www.c-cewx.com
www.c-cwex.com
www.c-csx.com
www.c-cesx.com
www.c-cdx.com
www.c-cedx.com
www.c-crx.com
www.c-cerx.com
www.c-crex.com
www.c-ce.com
www.c-cez.com
www.c-cexz.com
www.c-cezx.com
www.c-ces.com
www.c-cexs.com
www.c-ced.com
www.c-cexd.com
www.c-cec.com
www.c-cexc.com
www.c-cecx.com
www.c-cex.con

c-cex.com Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


c-cex.com TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.