SPLYCE.GG Splyce


splyce.gg website information.

splyce.gg domain name is registered by .GG top-level domain registry. See the other sites registred in .GG domain zone.

Following name servers are specified for splyce.gg domain:

  • ns-1487.awsdns-57.org
  • ns-149.awsdns-18.com
  • ns-1767.awsdns-28.co.uk
  • ns-718.awsdns-25.net

and probably website splyce.gg is hosted by WIKIMEDIA - Wikimedia Foundation Inc., US web hosting company. Check the complete list of other most popular websites hosted by WIKIMEDIA - Wikimedia Foundation Inc., US hosting company.

According to Alexa traffic rank the highest website splyce.gg position was 88984 (in the world). The lowest Alexa rank position was 996301. Now website splyce.gg ranked in Alexa database as number 707898 (in the world).

Website splyce.gg Desktop speed measurement score (85/100) is better than the results of 80% of other sites and shows that the page is performing great on desktop computers.

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

Mobile speed measurement score of splyce.gg (63/100) is better than the results of 61.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Jan-16-2025 707,898-5,879
Jan-15-2025 702,019-1,539
Jan-14-2025 700,48036,967
Jan-13-2025 737,44736,524
Jan-12-2025 773,97115,638
Jan-11-2025 789,609-6,668
Jan-10-2025 782,941-36,541

Advertisement

splyce.gg 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.



splyce.gg 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:
splyce.gg

Domain Status:
Active

Registrant:
Splyce Inc

Registrar:
Instra Corporation (www.instra.com)

Relevant dates:
Registered on 27th October 2015 at 23:19:00.603
Registry fee due on 27th October each year

Registration status:
Registered until cancelled

Name servers:
ns-1487.awsdns-57.org
ns-149.awsdns-18.com
ns-1767.awsdns-28.co.uk
ns-718.awsdns-25.net

WHOIS lookup made on Sun, 17 Apr 2022 at 22:57:47 BST

This WHOIS information is provided for free by CIDR, operator of
the backend registry for domain names ending in GG, JE, and AS.

Copyright (c) and database right Island Networks 1996 - 2022.

You may not access this WHOIS server or use any data from it except
as permitted by our Terms and Conditions which are published
at http://www.channelisles.net/legal/whoisterms

They include restrictions and prohibitions on

- using or re-using the data for advertising;
- using or re-using the service for commercial purposes without a licence;
- repackaging, recompilation, redistribution or reuse;
- obscuring, removing or hiding any or all of this notice;
- exceeding query rate or volume limits.

The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

splyce.gg server information

Servers Location

IP Address
52.71.167.122
35.153.7.88
Region
Virginia
Virginia
City
Ashburn
Ashburn

splyce.gg desktop page speed rank

Last tested: 2018-08-30


Desktop Speed Good
85/100

splyce.gg Desktop Speed Test Quick Summary


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

Your page has 1 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://www.workable.com/assets/embed.js

Optimize CSS Delivery of the following:

https://splyce.gg/build/home_compiled-87528162a7.css
https://fonts.googleapis.com/css?family=Roboto:100,300,400,500,700

priority - 4 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.goroost.com/roostjs/wy3pmkmnhfz657vcc5rbwcox7griuo45 (expiration not specified)
https://s3.amazonaws.com/splyce-media/core/spinner_fe.gif (expiration not specified)
https://www.workable.com/assets/embed.js (expiration not specified)
https://syndication.twitter.com/settings (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-WZ7NFH (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/174222…6726?v=2.8.25&r=stable (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 2 Optimize images

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

Optimize the following images to reduce their size by 14.7KiB (71% reduction).

Compressing and resizing https://s3.amazonaws.com/splyce-media/core/splyce_…te_header.png?v=3.6.24 could save 14.7KiB (71% reduction).

priority - 0 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 668B (43% reduction).

Compressing https://pageconfig.goroost.com/pageconfig?appKey=w…s%3A%2F%2Fsplyce.gg%2F could save 486B (44% reduction).
Compressing https://pageview.goroost.com/pageview?rdt=null&rid…splyce.gg%2F&referrer= could save 182B (40% reduction).

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 567B (21% reduction).

Minifying https://pageconfig.goroost.com/pageconfig?appKey=w…s%3A%2F%2Fsplyce.gg%2F could save 245B (23% reduction).
Minifying https://pageview.goroost.com/pageview?rdt=null&rid…splyce.gg%2F&referrer= could save 161B (35% reduction).
Minifying https://splyce.gg/static/home?v=3.6.24 could save 161B (15% reduction) after compression.

splyce.gg Desktop Resources

Total Resources32
Number of Hosts15
Static Resources13
JavaScript Resources10
CSS Resources2

splyce.gg Desktop Resource Breakdown

splyce.gg mobile page speed rank

Last tested: 2017-12-05


Mobile Speed Bad
63/100

splyce.gg Mobile Speed Test Quick Summary


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

Your page has 3 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://www.workable.com/assets/embed.js
https://splyce.gg/build/js/vendor-cb38376bb3.js
https://splyce.gg/build/js/home_compiled-90b2d16bd4.js

Optimize CSS Delivery of the following:

https://splyce.gg/build/home_compiled-aa26e564a3.css
https://fonts.googleapis.com/css?family=Roboto:100,300,400,500,700

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 42% of the final above-the-fold content could be rendered with the full HTML response.

priority - 6 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.goroost.com/roostjs/wy3pmkmnhfz657vcc5rbwcox7griuo45 (expiration not specified)
https://s3.amazonaws.com/splyce-media/core/spinner_fe.gif (expiration not specified)
https://syndication.twitter.com/settings (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-WZ7NFH (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1742225816056726?v=2.8.1 (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://www.workable.com/assets/embed.js (11 hours)

priority - 0 Optimize images

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

Optimize the following images to reduce their size by 2.2KiB (11% reduction).

Compressing https://s3.amazonaws.com/splyce-media/core/splyce_…te_header.png?v=3.5.5c could save 2.2KiB (11% reduction).

splyce.gg Mobile Resources

Total Resources30
Number of Hosts15
Static Resources13
JavaScript Resources10
CSS Resources2

splyce.gg Mobile Resource Breakdown

splyce.gg mobile page usability

Last tested: 2017-12-05


Mobile Usability Good
98/100

splyce.gg Mobile Usability Test Quick Summary


priority - 2 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 <a href=""></a> is close to 2 other tap targets.

The tap target <a id="nav-about" href="about">About</a> and 3 others are close to other tap targets.

splyce.gg similar domains

Similar domains:
www.splyce.com
www.splyce.net
www.splyce.org
www.splyce.info
www.splyce.biz
www.splyce.us
www.splyce.mobi
www.plyce.gg
www.splyce.gg
www.wplyce.gg
www.swplyce.gg
www.wsplyce.gg
www.eplyce.gg
www.seplyce.gg
www.esplyce.gg
www.dplyce.gg
www.sdplyce.gg
www.dsplyce.gg
www.zplyce.gg
www.szplyce.gg
www.zsplyce.gg
www.xplyce.gg
www.sxplyce.gg
www.xsplyce.gg
www.aplyce.gg
www.saplyce.gg
www.asplyce.gg
www.slyce.gg
www.solyce.gg
www.spolyce.gg
www.soplyce.gg
www.sllyce.gg
www.spllyce.gg
www.slplyce.gg
www.spyce.gg
www.sppyce.gg
www.splpyce.gg
www.spplyce.gg
www.spoyce.gg
www.sployce.gg
www.spkyce.gg
www.splkyce.gg
www.spklyce.gg
www.splce.gg
www.spltce.gg
www.splytce.gg
www.spltyce.gg
www.splgce.gg
www.splygce.gg
www.splgyce.gg
www.splhce.gg
www.splyhce.gg
www.splhyce.gg
www.spluce.gg
www.splyuce.gg
www.spluyce.gg
www.splye.gg
www.splyxe.gg
www.splycxe.gg
www.splyxce.gg
www.splyde.gg
www.splycde.gg
www.splydce.gg
www.splyfe.gg
www.splycfe.gg
www.splyfce.gg
www.splyve.gg
www.splycve.gg
www.splyvce.gg
www.splyc.gg
www.splycw.gg
www.splycew.gg
www.splycwe.gg
www.splycs.gg
www.splyces.gg
www.splycse.gg
www.splycd.gg
www.splyced.gg
www.splycr.gg
www.splycer.gg
www.splycre.gg

splyce.gg 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.


splyce.gg 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.