SCA.COFFEE SCA


sca.coffee website information.

sca.coffee domain name is registered by .COFFEE top-level domain registry. See the other sites registred in .COFFEE domain zone.

No name server records were found.

and probably website sca.coffee is hosted by Akamai International B.V. web hosting company. Check the complete list of other most popular websites hosted by Akamai International B.V. hosting company.

According to Alexa traffic rank the highest website sca.coffee position was 28823 (in the world). The lowest Alexa rank position was 987982. Now website sca.coffee ranked in Alexa database as number 39228 (in the world).

Website sca.coffee Desktop speed measurement score (83/100) is better than the results of 76.15% of other sites and shows that the page is performing great on desktop computers.

sca.coffee Mobile usability score (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of sca.coffee (59/100) is better than the results of 52.41% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
May-20-2024 N/AN/A
May-19-2024 39,228-139
May-18-2024 39,089-525
May-17-2024 38,564106
May-16-2024 38,670-177
May-15-2024 38,493-135
May-14-2024 38,358-245

Advertisement

sca.coffee 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.



sca.coffee 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: sca.coffee
Registry Domain ID: aaea6fdce2d944e0915d54b7ced50a18-DONUTS
Registrar WHOIS Server: whois.wildwestdomains.com
Registrar URL: http://www.wildwestdomains.com
Updated Date: 2023-06-07T18:25:10Z
Creation Date: 2016-11-17T21:00:41Z
Registry Expiry Date: 2023-11-17T21:00:41Z
Registrar: Wild West Domains, LLC
Registrar IANA ID: 440
Registrar Abuse Contact Email: abuse@wildwestdomains.com
Registrar Abuse Contact Phone: +1.6029995816
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Domains By Proxy, LLC
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Arizona
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns57.domaincontrol.com
Name Server: ns58.domaincontrol.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-09-04T17:44:54Z

sca.coffee server information

Servers Location

IP Address
Country
Region
City

sca.coffee desktop page speed rank

Last tested: 2017-05-17


Desktop Speed Medium
83/100

sca.coffee Desktop Speed Test Quick Summary


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

Your page has 4 blocking script resources and 2 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://use.typekit.net/ik/-cJEUZU6okZ_ya1JyFaCFti…6IbMg6QJMHbMZE0nvwB.js
https://static.squarespace.com/universal/scripts-c…deeb075f6ac0f84-min.js
https://static1.squarespace.com/static/ta/55f0a9b0…scripts/site-bundle.js
https://ajax.googleapis.com/ajax/libs/jquery/2.2.0/jquery.min.js

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Rubik:400,300,500,300i,700,700i,900
https://static1.squarespace.com/static/sitecss/584…?&filterFeatures=false

priority - 2 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 27% of the final above-the-fold content could be rendered with the full HTML response.

priority - 1 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 5.5KiB (78% reduction).

Compressing https://sca.coffee/assets/ui-icons.svg could save 5.5KiB (78% reduction).

priority - 0 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://ssl.google-analytics.com/ga.js (2 hours)

sca.coffee Desktop Resources

Total Resources34
Number of Hosts8
Static Resources14
JavaScript Resources7
CSS Resources2

sca.coffee Desktop Resource Breakdown

sca.coffee mobile page speed rank

Last tested: 2019-03-06


Mobile Speed Bad
59/100

sca.coffee Mobile Speed Test Quick Summary


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

Your page has 4 blocking script resources and 2 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://use.typekit.net/ik/OxTC0ZndGMLME-U_VyrJ5Zv…msMgegI6MTMgolVYkb9.js
https://static.squarespace.com/universal/scripts-c…2d0bb29f24f9f91-min.js
https://static1.squarespace.com/static/ta/55f0a9b0…scripts/site-bundle.js
https://ajax.googleapis.com/ajax/libs/jquery/2.2.0/jquery.min.js

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Rubik:400,300,500,700,700i,300i
https://static1.squarespace.com/static/sitecss/584…?&filterFeatures=false

priority - 8 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 38% of the final above-the-fold content could be rendered with the full HTML response.

priority - 1 Optimize images

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

Optimize the following images to reduce their size by 8.9KiB (68% reduction).

Compressing and resizing https://static1.squarespace.com/static/584f6bbef5e…49436487/?format=1500w could save 8.9KiB (68% reduction).

priority - 1 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://ssl.google-analytics.com/ga.js (2 hours)

priority - 1 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 5.5KiB (78% reduction).

Compressing https://sca.coffee/assets/ui-icons.svg could save 5.5KiB (78% reduction).

sca.coffee Mobile Resources

Total Resources23
Number of Hosts9
Static Resources13
JavaScript Resources6
CSS Resources2

sca.coffee Mobile Resource Breakdown

sca.coffee mobile page usability

Last tested: 2019-03-06


Mobile Usability Good
100/100

sca.coffee similar domains

Similar domains:
www.sca.com
www.sca.net
www.sca.org
www.sca.info
www.sca.biz
www.sca.us
www.sca.mobi
www.ca.coffee
www.sca.coffee
www.wca.coffee
www.swca.coffee
www.wsca.coffee
www.eca.coffee
www.seca.coffee
www.esca.coffee
www.dca.coffee
www.sdca.coffee
www.dsca.coffee
www.zca.coffee
www.szca.coffee
www.zsca.coffee
www.xca.coffee
www.sxca.coffee
www.xsca.coffee
www.aca.coffee
www.saca.coffee
www.asca.coffee
www.sa.coffee
www.sxa.coffee
www.scxa.coffee
www.sda.coffee
www.scda.coffee
www.sfa.coffee
www.scfa.coffee
www.sfca.coffee
www.sva.coffee
www.scva.coffee
www.svca.coffee
www.sc.coffee
www.scq.coffee
www.scaq.coffee
www.scqa.coffee
www.scw.coffee
www.scaw.coffee
www.scwa.coffee
www.scs.coffee
www.scas.coffee
www.scsa.coffee
www.scz.coffee
www.scaz.coffee
www.scza.coffee

sca.coffee 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.


sca.coffee 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.