WHOOING.COM 후잉가계부(whooing)


whooing.com website information.

whooing.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.

According to Alexa traffic rank the highest website whooing.com position was 20792 (in the world). The lowest Alexa rank position was 659211. Current position of whooing.com in Alexa rank database is below 1 million.

Website whooing.com Desktop speed measurement score (58/100) is better than the results of 33.06% of other sites shows that the page desktop performance can be improved.

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

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

Weekly Rank Report

DateRankChange
Jan-24-2022 N/AN/A
Jan-23-2022 N/AN/A
Jan-22-2022 N/AN/A
Jan-21-2022 N/AN/A
Jan-20-2022 N/AN/A
Jan-19-2022 N/AN/A
Jan-18-2022 N/AN/A

Advertisement

whooing.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.



whooing.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: WHOOING.COM
Registry Domain ID: 1669082551_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.dotname.co.kr
Registrar URL: http://www.dotname.co.kr
Updated Date: 2018-02-10T08:34:01Z
Creation Date: 2011-07-27T12:44:08Z
Registry Expiry Date: 2027-07-27T12:44:08Z
Registrar: Dotname Korea Corp.
Registrar IANA ID: 1132
Registrar Abuse Contact Email: abuse@dotnamekorea.com
Registrar Abuse Contact Phone: +82.7070900820
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS-1509.AWSDNS-60.ORG
Name Server: NS-1689.AWSDNS-19.CO.UK
Name Server: NS-332.AWSDNS-41.COM
Name Server: NS-611.AWSDNS-12.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-04-27T00:50:03Z

whooing.com server information

Servers Location

IP Address
Country
Region
City

whooing.com desktop page speed rank

Last tested: 2016-08-30


Desktop Speed Bad
58/100

whooing.com Desktop Speed Test Quick Summary


priority - 49 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 481.4KiB (69% reduction).

Compressing https://d1e6kzvaj69zen.cloudfront.net/js/default.js?v=2 could save 111.2KiB (72% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/highcharts/highcharts.js could save 94.3KiB (63% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/jquery-ui…custom.min.js?v=197772 could save 64.7KiB (74% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/jquery-1.9.1.min.js could save 58.4KiB (64% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/css/custom.css?v=u2535555at3 could save 42.3KiB (77% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/utilities.js?v=255n543 could save 23.8KiB (68% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/highcharts/highcharts-more.js could save 14.1KiB (63% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/language/ko/lang_ui.js could save 14KiB (72% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/css/jquery-ui-1.10.3.custom.css?v=2 could save 11.5KiB (82% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/awesomebox.js?v=23nhthnt could save 8.9KiB (68% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/css/web.css?v=n2h54562ih could save 8.3KiB (69% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/css/common.css?v=n55a3i could save 5.1KiB (68% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/css/icons.css?v=u2 could save 4.7KiB (80% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/lang/ko.js?_=h could save 4.6KiB (58% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/highcharts/modules/exporting.js could save 4KiB (57% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/jquery.tipsy.js?v=u22 could save 2.6KiB (64% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/jquery.history.min.js?_=bant could save 2.5KiB (72% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/render/lab_list.js?_=ae could save 2.3KiB (60% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/js/index2.js?_=1472583438079 could save 2.2KiB (61% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/language/ko/lang_forum.js could save 1.7KiB (59% reduction).

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

Your page has 13 blocking script resources and 8 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://d1e6kzvaj69zen.cloudfront.net/js/jquery-1.9.1.min.js
https://d1e6kzvaj69zen.cloudfront.net/language/ko/lang_ui.js
https://d1e6kzvaj69zen.cloudfront.net/language/ko/lang_forum.js
https://d1e6kzvaj69zen.cloudfront.net/js/jquery-ui…custom.min.js?v=197772
https://d1e6kzvaj69zen.cloudfront.net/js/jquery.history.min.js?_=bant
https://d1e6kzvaj69zen.cloudfront.net/js/jquery.tipsy.js?v=u22
https://d1e6kzvaj69zen.cloudfront.net/js/lang/ko.js?_=h
https://d1e6kzvaj69zen.cloudfront.net/js/utilities.js?v=255n543
https://d1e6kzvaj69zen.cloudfront.net/js/awesomebox.js?v=23nhthnt
https://d1e6kzvaj69zen.cloudfront.net/js/highcharts/highcharts.js
https://d1e6kzvaj69zen.cloudfront.net/js/highcharts/highcharts-more.js
https://d1e6kzvaj69zen.cloudfront.net/js/highcharts/modules/exporting.js
https://d1e6kzvaj69zen.cloudfront.net/js/default.js?v=2

Optimize CSS Delivery of the following:

https://d1e6kzvaj69zen.cloudfront.net/css/reset.css?v=2
https://d1e6kzvaj69zen.cloudfront.net/css/icons.css?v=u2
https://d1e6kzvaj69zen.cloudfront.net/css/common.css?v=n55a3i
https://d1e6kzvaj69zen.cloudfront.net/css/web.css?v=n2h54562ih
https://cdn.jsdelivr.net/font-nanum/1.0/nanumbarun…c/nanumbarungothic.css
https://d1e6kzvaj69zen.cloudfront.net/css/custom.css?v=u2535555at3
https://d1e6kzvaj69zen.cloudfront.net/css/jquery-ui-1.10.3.custom.css?v=2
https://d1e6kzvaj69zen.cloudfront.net/skins/1/set_1.css?v=2

priority - 7 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://whooing.com/
https://www.whooing.com/
https://whooing.com/

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

priority - 2 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://d1e6kzvaj69zen.cloudfront.net/language/ko/lang_forum.js (expiration not specified)
https://d1e6kzvaj69zen.cloudfront.net/language/ko/lang_ui.js (expiration not specified)
https://s3-ap-northeast-1.amazonaws.com/whooingprofile/p0.jpg (expiration not specified)
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 18.7KiB (40% reduction).

Compressing https://d1e6kzvaj69zen.cloudfront.net/img/index/typo_ko.png could save 10.3KiB (37% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/img/trustlogo.png could save 1.9KiB (28% reduction).
Compressing and resizing https://s3-ap-northeast-1.amazonaws.com/whooingprofile/p0.jpg could save 1.8KiB (75% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/img/sns_google.gif could save 1.3KiB (59% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/img/input.png could save 1KiB (72% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/img/btn.png could save 935B (79% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/img/shadow.png could save 901B (32% reduction).
Compressing https://d1e6kzvaj69zen.cloudfront.net/img/banner_e.png could save 690B (26% reduction).

priority - 0 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 1.7KiB (49% reduction).

Minifying https://d1e6kzvaj69zen.cloudfront.net/js/jquery.history.min.js?_=bant could save 1.7KiB (49% reduction).

whooing.com Desktop Resources

Total Resources50
Number of Hosts9
Static Resources42
JavaScript Resources16
CSS Resources8

whooing.com Desktop Resource Breakdown

whooing.com mobile page speed rank

Last tested: 2019-12-10


Mobile Speed Bad
56/100

whooing.com Mobile Speed Test Quick Summary


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

Your page has 13 blocking script resources and 10 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://whooing.com/include/assets/js/jquery-1.9.1.min.js
https://whooing.com/include/language/en/lang_ui.js
https://whooing.com/include/language/en/lang_forum.js
https://whooing.com/include/assets/js/jquery-ui-1.…custom.min.js?v=197772
https://whooing.com/include/assets/js/jquery.history.min.js?_=bant
https://whooing.com/include/assets/js/jquery.tipsy.js?v=u22
https://whooing.com/include/assets/js/lang/en.js?_=h
https://whooing.com/include/assets/js/utilities.js?v=25a25n543
https://whooing.com/include/assets/js/awesomebox.js?v=23nhthnt
https://whooing.com/include/assets/js/highcharts/highcharts.js
https://whooing.com/include/assets/js/highcharts/highcharts-more.js
https://whooing.com/include/assets/js/highcharts/modules/exporting.js
https://whooing.com/include/assets/js/default.js?v=1568272850

Optimize CSS Delivery of the following:

https://whooing.com/include/assets/css/reset.css?v=2
https://whooing.com/include/assets/css/icons.css?v=u2
https://whooing.com/include/assets/css/common.css?v=n55a3i
https://whooing.com/include/assets/css/web.css?v=n2h54562ih
https://cdn.jsdelivr.net/font-nanum/1.0/nanumbarun…c/nanumbarungothic.css
https://whooing.com/include/assets/css/custom.css?v=u2535555at3
https://whooing.com/include/assets/css/jquery-ui-1.10.3.custom.css?v=2
https://whooing.com/include/assets/skins/1/set_1.css?v=2
https://whooing.com/include/assets/css/mobile.css?_=a5nthaonteh
https://whooing.com/include/assets/css/phone.css?_=na3tthtowt

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 2% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

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://s3-ap-northeast-1.amazonaws.com/whooingprofile/p0.jpg (expiration not specified)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/231352…2906?v=2.9.14&r=stable (20 minutes)
https://www.google-analytics.com/plugins/ua/ecommerce.js (60 minutes)
https://www.googleadservices.com/pagead/conversion.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 4 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 37.9KiB (38% reduction).

Minifying https://whooing.com/include/assets/js/default.js?v=1568272850 could save 24.2KiB (36% reduction) after compression.
Minifying https://whooing.com/include/assets/js/utilities.js?v=25a25n543 could save 8.6KiB (45% reduction) after compression.
Minifying https://whooing.com/include/assets/js/awesomebox.js?v=23nhthnt could save 3.2KiB (45% reduction) after compression.
Minifying https://whooing.com/include/assets/js/lang/en.js?_=h could save 665B (25% reduction) after compression.
Minifying https://whooing.com/include/assets/js/jquery.tipsy.js?v=u22 could save 594B (29% reduction) after compression.
Minifying https://whooing.com/include/assets/js/jquery.history.min.js?_=bant could save 357B (38% reduction) after compression.
Minifying https://whooing.com/include/assets/js/index2.js?_=1575950292862 could save 309B (18% reduction) after compression.

priority - 2 Optimize images

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

Optimize the following images to reduce their size by 19.3KiB (49% reduction).

Compressing https://whooing.com/include/assets/img/index/mainindex_screencast.jpg could save 14.4KiB (51% reduction).
Compressing https://whooing.com/include/assets/img/trustlogo.png could save 1.9KiB (28% reduction).
Compressing https://s3-ap-northeast-1.amazonaws.com/whooingprofile/p0.jpg could save 1.2KiB (51% reduction).
Compressing https://whooing.com/include/assets/img/btn.png could save 953B (81% reduction).
Compressing https://whooing.com/include/assets/img/input.png could save 874B (61% reduction).

priority - 1 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 5.9KiB (20% reduction).

Minifying https://whooing.com/include/assets/css/custom.css?v=u2535555at3 could save 2.9KiB (19% reduction) after compression.
Minifying https://whooing.com/include/assets/css/jquery-ui-1.10.3.custom.css?v=2 could save 1.1KiB (31% reduction) after compression.
Minifying https://whooing.com/include/assets/css/web.css?v=n2h54562ih could save 750B (18% reduction) after compression.
Minifying https://whooing.com/include/assets/css/common.css?v=n55a3i could save 460B (17% reduction) after compression.
Minifying https://whooing.com/include/assets/css/phone.css?_=na3tthtowt could save 446B (15% reduction) after compression.
Minifying https://whooing.com/include/assets/css/mobile.css?_=a5nthaonteh could save 364B (18% reduction) after compression.

whooing.com Mobile Resources

Total Resources50
Number of Hosts10
Static Resources39
JavaScript Resources20
CSS Resources10

whooing.com Mobile Resource Breakdown

whooing.com mobile page usability

Last tested: 2019-12-10


Mobile Usability Good
96/100

whooing.com Mobile Usability Test Quick Summary


priority - 3 Configure the viewport

Your page specifies a fixed-width mobile viewport. Consider using a responsive viewport to allow your page to render properly on all devices.

Configuring a viewport specifying width=device-width instead of width=320.1 will allow your page to adapt for devices of various widths. This may require additional work if the styling on your page relies on a fixed-width layout.

whooing.com similar domains

Similar domains:
www.whooing.com
www.whooing.net
www.whooing.org
www.whooing.info
www.whooing.biz
www.whooing.us
www.whooing.mobi
www.hooing.com
www.whooing.com
www.qhooing.com
www.wqhooing.com
www.qwhooing.com
www.ahooing.com
www.wahooing.com
www.awhooing.com
www.shooing.com
www.wshooing.com
www.swhooing.com
www.ehooing.com
www.wehooing.com
www.ewhooing.com
www.wooing.com
www.wbooing.com
www.whbooing.com
www.wbhooing.com
www.wgooing.com
www.whgooing.com
www.wghooing.com
www.wyooing.com
www.whyooing.com
www.wyhooing.com
www.wuooing.com
www.whuooing.com
www.wuhooing.com
www.wjooing.com
www.whjooing.com
www.wjhooing.com
www.wnooing.com
www.whnooing.com
www.wnhooing.com
www.whoing.com
www.whioing.com
www.whoioing.com
www.whiooing.com
www.whkoing.com
www.whokoing.com
www.whkooing.com
www.whloing.com
www.wholoing.com
www.whlooing.com
www.whpoing.com
www.whopoing.com
www.whpooing.com
www.whoiing.com
www.whooiing.com
www.whoking.com
www.whooking.com
www.wholing.com
www.whooling.com
www.whoping.com
www.whooping.com
www.whoong.com
www.whooung.com
www.whooiung.com
www.whoouing.com
www.whoojng.com
www.whooijng.com
www.whoojing.com
www.whookng.com
www.whooikng.com
www.whooong.com
www.whooiong.com
www.whoooing.com
www.whooig.com
www.whooibg.com
www.whooinbg.com
www.whooibng.com
www.whooihg.com
www.whooinhg.com
www.whooihng.com
www.whooijg.com
www.whooinjg.com
www.whooimg.com
www.whooinmg.com
www.whooimng.com
www.whooin.com
www.whooinf.com
www.whooingf.com
www.whooinfg.com
www.whooinv.com
www.whooingv.com
www.whooinvg.com
www.whooint.com
www.whooingt.com
www.whoointg.com
www.whooinb.com
www.whooingb.com
www.whooiny.com
www.whooingy.com
www.whooinyg.com
www.whooinh.com
www.whooingh.com
www.whooing.con

whooing.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.


whooing.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.