NAMU.WIKI 나무위키:대문 - 나무위키


namu.wiki website information.

namu.wiki domain name is registered by .WIKI top-level domain registry. See the other sites registred in .WIKI domain zone.

Following name servers are specified for namu.wiki domain:

  • dara.ns.cloudflare.com
  • nile.ns.cloudflare.com

and probably website namu.wiki 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 namu.wiki position was 8544 (in the world). The lowest Alexa rank position was 10024. Now website namu.wiki ranked in Alexa database as number 8655 (in the world).

Website namu.wiki Desktop speed measurement score (78/100) is better than the results of 65.98% of other sites shows that the page desktop performance can be improved.

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

Mobile speed measurement score of namu.wiki (66/100) is better than the results of 68.49% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-17-2024 8,65529
Nov-16-2024 8,684-51
Nov-15-2024 8,633-60
Nov-14-2024 8,573-3
Nov-13-2024 8,5700
Nov-12-2024 8,5700
Nov-11-2024 8,5700

Advertisement

namu.wiki 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.



namu.wiki 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: namu.wiki
Registry Domain ID: D7558245CNIC-GDREG
Registrar WHOIS Server: whois.dynadot.com
Registrar URL: https://www.dynadot.com/
Updated Date: 2022-07-24T02:01:45Z
Creation Date: 2015-04-11T19:54:14Z
Registry Expiry Date: 2030-04-11T23:59:59Z
Registrar: Dynadot LLC
Registrar IANA ID: 472
Registrar Abuse Contact Email: abuse@dynadot.com
Registrar Abuse Contact Phone: +1.6502620100
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization:
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: California
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 Street: 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 Street: 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: dara.ns.cloudflare.com
Name Server: nile.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-01-03T09:24:19Z

namu.wiki server information

Servers Location

IP Address
104.16.181.45
104.16.180.45
Region
Arizona
Arizona
City
Phoenix
Phoenix

namu.wiki desktop page speed rank

Last tested: 2019-06-18


Desktop Speed Medium
78/100

namu.wiki Desktop Speed Test Quick Summary


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

Your page has 13 blocking script resources and 12 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://namu.wiki/js/jquery-2.1.4.min.js?f9c7afd0
https://namu.wiki/js/dateformatter.js?508d6dd4
https://namu.wiki/js/intersection-observer.js?36e469ff
https://namu.wiki/js/theseed.js?24141115
https://namu.wiki/skins/senkawa/js/lib/jquery.pjax.js?700f7656
https://namu.wiki/skins/senkawa/js/lib/jquery.lazyload.min.js?5c01d7af
https://namu.wiki/skins/senkawa/js/lib/jquery-ui.min.js?557e2375
https://namu.wiki/skins/senkawa/js/lib/tether.min.js?e21e4520
https://namu.wiki/skins/senkawa/js/lib/super-treadmill.min.js?636aa086
https://namu.wiki/skins/senkawa/js/lib/bootstrap.min.js?a2f0eda8
https://namu.wiki/skins/senkawa/js/lib/nprogress.js?5fc208df
https://namu.wiki/skins/senkawa/js/namu.js?beddd0b2
https://namu.wiki/skins/senkawa/js/layout.js?f8d965cf

Optimize CSS Delivery of the following:

https://namu.wiki/css/diffview.css?05e3f5dd
https://namu.wiki/css/katex.min.css?7ee60c84
https://namu.wiki/css/wiki.css?2808316a
https://namu.wiki/skins/senkawa/css/lib/jquery-ui.min.css?971be4a6
https://namu.wiki/skins/senkawa/css/lib/bootstrap.min.css?f040bd43
https://namu.wiki/skins/senkawa/css/lib/ionicons.min.css?2d4234e8
https://namu.wiki/skins/senkawa/css/lib/nprogress.css?9dc52b7d
https://namu.wiki/skins/senkawa/css/bootstrap-fix.css?b43106c0
https://namu.wiki/skins/senkawa/css/layout.css?617b72a7
https://namu.wiki/skins/senkawa/css/wiki.css?d326c35b
https://namu.wiki/skins/senkawa/css/discuss.css?615e5e7c
https://namu.wiki/skins/senkawa/css/dark.css?35f16b60

priority - 6 Optimize images

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

Optimize the following images to reduce their size by 56.7KiB (43% reduction).

Compressing https://cdn-aitg.widerplanet.com/images/wp/41/22/4…f2260978d1e5e21322.jpg could save 31.3KiB (69% reduction).
Compressing https://cdn-aitg.widerplanet.com/images/wp/e6/db/e…f8d24d06496aac96db.jpg could save 9.1KiB (35% reduction).
Compressing https://tpc.googlesyndication.com/sadbundle/12485143450987014104/bg01.jpg could save 3.6KiB (24% reduction).
Compressing https://tpc.googlesyndication.com/sadbundle/12485143450987014104/bg03.jpg could save 3.4KiB (23% reduction).
Compressing https://tpc.googlesyndication.com/sadbundle/12485143450987014104/bg02.jpg could save 3.1KiB (24% reduction).
Compressing https://namu.live/static/ad/images/powerlink.png could save 2.8KiB (86% reduction).
Compressing https://cdn-aitg.widerplanet.com/images/tgad_information.png could save 1.3KiB (63% reduction).
Compressing https://tpc.googlesyndication.com/sadbundle/124851…4104/btn-learnmore.gif could save 922B (33% reduction).
Compressing https://namu.wiki/skins/senkawa/img/namuwiki_logo_kor_white_small.png could save 565B (12% reduction).
Compressing https://tpc.googlesyndication.com/sadbundle/124851…/HMA_logo_hor_blue.png could save 506B (18% reduction).
Compressing https://namu.wiki/skins/senkawa/css/lib/images/ui-…t_75_ffffff_40x100.png could save 112B (53% reduction).

priority - 3 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://namu.wiki/live-api/recent.json?slug=live&count=15 (30 seconds)
https://namu.wiki/sidebar.json (30 seconds)
https://www.google.com/recaptcha/api.js?render=exp…onload=recaptchaOnLoad (5 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://ssl.pstatic.net/adimg3.search/adpost/js/adpost_show_ads_v2.min.js (57.1 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://t1.daumcdn.net/adfit/static/ad.min.js (60 minutes)

priority - 3 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://namu.wiki/
https://namu.wiki/
https://namu.wiki/w/%EB%82%98%EB%AC%B4%EC%9C%84%ED%82%A4:%EB%8C%80%EB%AC%B8

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 59% 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 - 2 Reduce server response time

In our test, your server responded in 0.39 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 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 8.6KiB (61% reduction).

Compressing https://cdn.megadata.co.kr/js/media/1.2/MBSHandler.js could save 7.3KiB (73% reduction).
Compressing https://external.impression-neo.naver.com/api/v2/a…dle_naver_ads_response could save 1.3KiB (34% 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 3.8KiB (38% reduction).

Minifying https://cdn.megadata.co.kr/js/media/1.2/MBSHandler.js could save 3.8KiB (38% 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 578B (17% reduction).

Minifying https://namu.live/static/ad/powerlink.html?v=18 could save 291B (17% reduction) after compression.
Minifying https://namu.live/static/ad/powerlink_mobile.html?v=18 could save 287B (17% reduction) after compression.

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 383B (24% reduction).

Minifying https://namu.wiki/skins/senkawa/css/dark.css?35f16b60 could save 383B (24% reduction) after compression.

namu.wiki Desktop Resources

Total Resources103
Number of Hosts22
Static Resources61
JavaScript Resources37
CSS Resources12

namu.wiki Desktop Resource Breakdown

namu.wiki mobile page speed rank

Last tested: 2019-12-03


Mobile Speed Medium
66/100

namu.wiki Mobile Speed Test Quick Summary


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

Your page has 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.

Optimize CSS Delivery of the following:

https://namu.wiki/_nuxt/fd0658e808ae0512271e.css
https://namu.wiki/_nuxt/807866a8bfefae635e9b.css

priority - 12 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://namu.wiki/sidebar.json (30 seconds)
https://www.google.com/recaptcha/api.js?onload=vue…Loaded&render=explicit (5 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://www.googletagservices.com/activeview/js/cu…ner.js?cache=r20110914 (50 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://securepubads.g.doubleclick.net/pagead/js/rum.js (60 minutes)
https://namu.wiki/_nuxt/125ed4319f3927e3cc7e.js (24 hours)
https://namu.wiki/_nuxt/1e7c875605ecf8385b83.js (24 hours)
https://namu.wiki/_nuxt/228cdb4845078c515833.js (24 hours)
https://namu.wiki/_nuxt/455af0b672089799fb5d.js (24 hours)
https://namu.wiki/_nuxt/6e7cb2ece6dde3af1dce.js (24 hours)
https://namu.wiki/_nuxt/807866a8bfefae635e9b.css (24 hours)
https://namu.wiki/_nuxt/9223f9d929ffad0a1bc2.js (24 hours)
https://namu.wiki/_nuxt/94b6364f8c0d4abd972a.js (24 hours)
https://namu.wiki/_nuxt/b4d16c9085700e911990.js (24 hours)
https://namu.wiki/_nuxt/ed5800d4559c975d3d23.js (24 hours)
https://namu.wiki/_nuxt/fd0658e808ae0512271e.css (24 hours)
https://namu.wiki/_nuxt/img/31c7891.png (24 hours)

priority - 10 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://namu.wiki/
https://namu.wiki/
https://namu.wiki/w/%EB%82%98%EB%AC%B4%EC%9C%84%ED%82%A4:%EB%8C%80%EB%AC%B8

priority - 4 Optimize images

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

Optimize the following images to reduce their size by 38.5KiB (27% reduction).

Compressing and resizing https://w.namu.la/s/7744b80f6fa5262190bba52da210a8…386b0b3ac2f7c65594b8f9 could save 20.9KiB (94% reduction).
Compressing https://tpc.googlesyndication.com/daca_images/simgad/2329490395821306998 could save 8.1KiB (15% reduction).
Compressing https://w.namu.la/s/4c8234a384a3d2516c9035cd7bf975…c1f6f7b5109e7bee392c81 could save 6KiB (13% reduction).
Compressing https://tpc.googlesyndication.com/daca_images/simgad/3117865923635838688 could save 2.9KiB (20% reduction).
Compressing https://namu.wiki/_nuxt/img/31c7891.png could save 565B (12% reduction).

priority - 3 Reduce server response time

In our test, your server responded in 0.36 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.

namu.wiki Mobile Resources

Total Resources71
Number of Hosts22
Static Resources34
JavaScript Resources23
CSS Resources2

namu.wiki Mobile Resource Breakdown

namu.wiki mobile page usability

Last tested: 2019-12-03


Mobile Usability Good
95/100

namu.wiki Mobile Usability Test Quick Summary


priority - 4 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="/random" class=""></a> is close to 1 other tap targets.

The tap target <button type="button"></button> is close to 1 other tap targets.

The tap target <button type="button"></button> is close to 1 other tap targets.

The tap target <a href="/member/star/%…8C%80%EB%AC%B8" class="has-tooltip">5411</a> is close to 1 other tap targets.

The tap target <a href="/backlink/%EB%…8C%80%EB%AC%B8" class="">역링크</a> and 3 others are close to other tap targets.

The tap target <a href="/acl/%EB%82%98…8C%80%EB%AC%B8" class="">ACL</a> is close to 2 other tap targets.

The tap target <a href="/w/%EB%82%98%E…9C%84%ED%82%A4" class="wiki-link-internal">나무위키</a> is close to 1 other tap targets.

The tap target <a href="http://board.namu.wiki/notice">공지</a> and 5 others are close to other tap targets.

The tap target <a href="/NeededPages">작성이 필요한 문서</a> and 1 others are close to other tap targets.
The tap target <a href="/w/%ED%8C%8C%E…%EA%B3%A02.png" class="wiki-link-internal"></a> and 4 others are close to other tap targets.
The tap target <a href="/w/%EB%82%98%E…B0%A9%EC%B9%A8" class="wiki-link-internal">기본방침</a> and 35 others are close to other tap targets.
The tap target <a href="#"></a> is close to 1 other tap targets.

namu.wiki similar domains

Similar domains:
www.namu.com
www.namu.net
www.namu.org
www.namu.info
www.namu.biz
www.namu.us
www.namu.mobi
www.amu.wiki
www.namu.wiki
www.bamu.wiki
www.nbamu.wiki
www.bnamu.wiki
www.hamu.wiki
www.nhamu.wiki
www.hnamu.wiki
www.jamu.wiki
www.njamu.wiki
www.jnamu.wiki
www.mamu.wiki
www.nmamu.wiki
www.mnamu.wiki
www.nmu.wiki
www.nqmu.wiki
www.naqmu.wiki
www.nqamu.wiki
www.nwmu.wiki
www.nawmu.wiki
www.nwamu.wiki
www.nsmu.wiki
www.nasmu.wiki
www.nsamu.wiki
www.nzmu.wiki
www.nazmu.wiki
www.nzamu.wiki
www.nau.wiki
www.nanu.wiki
www.namnu.wiki
www.nanmu.wiki
www.naju.wiki
www.namju.wiki
www.najmu.wiki
www.naku.wiki
www.namku.wiki
www.nakmu.wiki
www.nam.wiki
www.namy.wiki
www.namuy.wiki
www.namyu.wiki
www.namh.wiki
www.namuh.wiki
www.namhu.wiki
www.namj.wiki
www.namuj.wiki
www.nami.wiki
www.namui.wiki
www.namiu.wiki

namu.wiki 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.


namu.wiki 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.