BLOG.ME 네이버 블로그

blog.me Website Information

Daily Unique Visits: 138,372

Daily Page Views: 830,232

Income Per Day: $1,660

Estimated Value: $1,195,200

This website is located in Korea, Republic of and is using following IP address 125.209.214.79. See the complete list of popular websites hosted in Korea, Republic of.

blog.me is registered under .ME top-level domain. Please check other sites in .ME zone.

Website blog.me is using the following name servers:

  • ns2.naver.com
  • ns1.naver.com

and is probably hosted by NHN-AS-KR NBP, KR. See the full list of other websites hosted by NHN-AS-KR NBP, KR.

The highest website blog.me position in Alexa rank database was 441 and the lowest rank position was 30492. Current position of blog.me in Alexa rank database is 10365.

Desktop speed score of blog.me (82/100) is better than the results of 77.31% of other sites and shows that the page is performing great on desktop computers.

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

Mobile speed score of blog.me (50/100) is better than the results of 31.51% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

blog.me Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


blog.me whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


Domain Name: BLOG.ME
Registry Domain ID: D108500000000002870-AGRS
Registrar WHOIS Server:
Registrar URL: http://www.gabia.com
Updated Date: 2018-03-30T04:25:51Z
Creation Date: 2008-04-29T17:59:12Z
Registry Expiry Date: 2019-04-29T17:59:12Z
Registrar Registration Expiration Date:
Registrar: Gabia, Inc.
Registrar IANA ID: 244
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization: NAVER Corp.
Registrant State/Province:
Registrant Country: KR
Name Server: NS1.NAVER.COM
Name Server: NS2.NAVER.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2018-07-19T02:59:12Z

blog.me server information

Servers Location

blog.me desktop page speed rank

Last tested: 2017-05-20


Desktop Speed Medium
82/100

blog.me Desktop Speed Test Quick Summary


priority - 18 Optimize images

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

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

Compressing https://blogfiles.pstatic.net/MjAxNzA1MTBfMjc2/MDA…%B7%CE%B1%D7%C8%A8.jpg could save 35KiB (69% reduction).
Compressing https://ssl.pstatic.net/tveta/libs/1162/1162347/20170428120323-EK1RHz6o.jpg could save 28.9KiB (62% reduction).
Compressing http://static.naver.net/common/gnb/2014/promo_npay.png could save 16.7KiB (88% reduction).
Compressing https://ssl.pstatic.net/static/common/gnb/2014/promo_npay.png could save 16.7KiB (88% reduction).
Compressing https://blogfiles.pstatic.net/MjAxNzA1MDhfOTUg/MDA…508_389X218_pholar.jpg could save 14.9KiB (51% reduction).
Compressing http://blogfiles9.naver.net/20150424_280/bloglabde…%CA_150422_100x100.jpg could save 5.7KiB (51% reduction).
Compressing https://blogfiles.pstatic.net/20150424_280/bloglab…%CA_150422_100x100.jpg could save 5.7KiB (51% reduction).
Compressing http://blogpfthumb.phinf.naver.net/MjAxNzA1MTVfODc…620/f%2B12.jpg?type=s2 could save 2.1KiB (14% reduction).
Compressing http://static.naver.net/common/gnb/banner/promo_npay_1705.png could save 1.9KiB (46% reduction).
Compressing https://ssl.pstatic.net/static/common/gnb/banner/promo_npay_1705.png could save 1.9KiB (46% reduction).
Compressing http://blogimgs.naver.net/imgs/section/btn_main_login.gif could save 1.4KiB (52% reduction).
Compressing https://blogimgs.pstatic.net/imgs/section/btn_main_login.gif could save 1.4KiB (52% reduction).
Compressing http://static.naver.net/blog/btn_lnb_menu5.png could save 1.3KiB (34% reduction).
Compressing https://ssl.pstatic.net/static/blog/btn_lnb_menu5.png could save 1.3KiB (34% reduction).
Compressing http://blogthumb2.naver.net/MjAxNzA1MDVfODMg/MDAxN…idonna/8.JPG?type=s140 could save 1.3KiB (14% reduction).
Compressing https://blogthumb.pstatic.net/MjAxNzA1MDVfODMg/MDA…idonna/8.JPG?type=s140 could save 1.3KiB (14% reduction).
Compressing http://static.naver.net/blog/logo_pcsection.png could save 1.1KiB (56% reduction).
Compressing https://ssl.pstatic.net/static/blog/logo_pcsection.png could save 1.1KiB (56% reduction).
Compressing http://blogimgs.naver.net/section/blog_home_banner_0125.png could save 1.1KiB (51% reduction).
Compressing https://blogimgs.pstatic.net/section/blog_home_banner_0125.png could save 1.1KiB (51% reduction).
Compressing http://static.naver.net/blog/h_official_blog.png could save 1.1KiB (64% reduction).
Compressing https://ssl.pstatic.net/static/blog/h_official_blog.png could save 1.1KiB (64% reduction).
Compressing http://static.naver.net/blog/btn_lnb_menu2_3.png could save 1.1KiB (32% reduction).
Compressing https://ssl.pstatic.net/static/blog/btn_lnb_menu2_3.png could save 1.1KiB (32% reduction).
Compressing http://blogimgs.naver.net/section/bg_topiclist_130820.gif could save 1KiB (88% reduction).
Compressing https://blogimgs.pstatic.net/section/bg_topiclist_130820.gif could save 1KiB (88% reduction).
Compressing https://blogimgs.pstatic.net/section/icon_set.gif could save 1KiB (72% reduction).
Compressing http://static.naver.net/blog/btn_lnb_menu1_1.png could save 971B (33% reduction).
Compressing https://ssl.pstatic.net/static/blog/btn_lnb_menu1_1.png could save 971B (33% reduction).
Compressing http://blogpfthumb.phinf.naver.net/20150820_14/jyk…G/DSCN5438.jpg?type=s2 could save 966B (13% reduction).
Compressing http://static.naver.net/blog/ico_officialblog.png could save 920B (66% reduction).
Compressing https://ssl.pstatic.net/static/blog/ico_officialblog.png could save 920B (66% reduction).
Compressing http://static.naver.net/blog/btn_lnb_menu3.png could save 911B (32% reduction).
Compressing https://ssl.pstatic.net/static/blog/btn_lnb_menu3.png could save 911B (32% reduction).
Compressing http://static.naver.net/blog/btn_n_dev_guide1.png could save 895B (55% reduction).
Compressing https://ssl.pstatic.net/static/blog/btn_n_dev_guide1.png could save 895B (55% reduction).
Compressing https://blogpfthumb-phinf.pstatic.net/data32/2008/…tamaraciel.jpg?type=s2 could save 844B (12% reduction).
Compressing http://mblogthumb1.phinf.naver.net/20131027_152/de…VERSION2.jpg?type=s140 could save 840B (12% reduction).
Compressing https://mblogthumb-phinf.pstatic.net/20131027_152/…VERSION2.jpg?type=s140 could save 840B (12% reduction).
Compressing http://static.naver.net/blog/btn_lnb_menu6.png could save 805B (24% reduction).
Compressing https://ssl.pstatic.net/static/blog/btn_lnb_menu6.png could save 805B (24% reduction).
Compressing https://blogthumb.pstatic.net/MjAxNzA1MjBfODkg/MDA…C%84%9C01.jpg?type=s88 could save 789B (17% reduction).
Compressing http://static.naver.net/blog/section/img_powerblog_mask.png could save 774B (62% reduction).
Compressing https://ssl.pstatic.net/static/blog/section/img_powerblog_mask.png could save 774B (62% reduction).
Compressing http://static.naver.net/blog/btn_lnb2_menu1.png could save 682B (54% reduction).
Compressing https://ssl.pstatic.net/static/blog/btn_lnb2_menu1.png could save 682B (54% reduction).
Compressing https://blogthumb.pstatic.net/MjAxNzA1MjBfMjYz/MDA…/IMG_0080.jpg?type=s88 could save 645B (15% reduction).
Compressing http://static.naver.net/blog/h_blog_dev_guide.png could save 610B (38% reduction).
Compressing https://ssl.pstatic.net/static/blog/h_blog_dev_guide.png could save 610B (38% reduction).
Compressing https://blogthumb.pstatic.net/MjAxNzA1MjFfMTYg/MDA…/DSC_2652.jpg?type=s88 could save 600B (15% reduction).
Compressing https://blogthumb.pstatic.net/MjAxNzA1MjBfMTY5/MDA…/IMG_3483.JPG?type=s88 could save 567B (15% reduction).
Compressing https://blogthumb.pstatic.net/MjAxNzA1MjFfMjI5/MDA…%EB%B2%84.jpg?type=s88 could save 522B (13% 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.pstatic.net/happyimg2/congad/congBanne…s.1.0.8.js?zone=000007 (2.9 minutes)
https://ssl.pstatic.net/happyimg2/application/real/congad/cc/blog_https.js (3 minutes)

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 5KiB (60% reduction).

Compressing https://veta.naver.com/fxshow?su=SU10053&da_dom_id=addiv&rui=20170521101518 could save 2.3KiB (63% reduction).
Compressing http://static.nid.naver.com/b4/enclogin/b4svc.js could save 1KiB (64% reduction).
Compressing https://static.nid.naver.com/b4/enclogin/b4svc.js could save 1KiB (64% reduction).
Compressing http://ad.naver.com/fxshow?su=SU10053&da_dom_id=addiv&rui=20170521101516 could save 553B (43% 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 3KiB (39% reduction).

Minifying http://static.gn.naver.net/js/clickcrD.js could save 1.5KiB (39% reduction) after compression.
Minifying https://static.nid.naver.com/js/clickcrD.js could save 1.5KiB (39% reduction) after compression.

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 919B (25% reduction).

Minifying https://veta.naver.com/fxshow?su=SU10053&da_dom_id=addiv&rui=20170521101518 could save 919B (25% reduction).

blog.me Desktop Resource Breakdown

Total Resources144
Number of Hosts24
Static Resources131
JavaScript Resources23
CSS Resources4

blog.me mobile page speed rank

Last tested: 2018-01-29


Mobile Speed Bad
50/100

blog.me Mobile Speed Test Quick Summary


priority - 40 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.

Remove render-blocking JavaScript:

http://t.static.blog.naver.net/nmobile/versioning/…pBundle1-1301620293.js
http://t.static.blog.naver.net/nmobile/versioning/NgAppBundle2-741357035.js
http://t.static.blog.naver.net/nmobile/versioning/NgTemplate-1830968934.js

Optimize CSS Delivery of the following:

http://t.static.blog.naver.net/nmobile/versioning/lego_w-105999950.css
http://t.static.blog.naver.net/nmobile/versioning/lego_view-196529423.css

priority - 35 Avoid landing page redirects

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

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

http://blog.me/
http://section.blog.naver.com/
http://m.blog.naver.com/?proxyReferer=
http://m.blog.naver.com/Recommendation.nhn

priority - 25 Optimize images

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

Optimize the following images to reduce their size by 249KiB (20% reduction).

Compressing http://static.naver.net/blog/sp_blog52.png could save 46.3KiB (23% reduction).
Compressing http://mblogthumb3.phinf.naver.net/MjAxODAxMTBfMzc…416BF536.JPG?type=w800 could save 37.3KiB (20% reduction).
Compressing http://mblogthumb3.phinf.naver.net/MjAxODAxMjJfODg…2_122951.jpg?type=w800 could save 29.5KiB (18% reduction).
Compressing http://mblogthumb3.phinf.naver.net/MjAxODAxMjRfNzc…IMG_1764.jpg?type=w800 could save 26.8KiB (17% reduction).
Compressing http://mblogthumb4.phinf.naver.net/MjAxODAxMDFfMjg…IMG_2042.JPG?type=w800 could save 25.9KiB (19% reduction).
Compressing http://mblogthumb1.phinf.naver.net/MjAxODAxMDhfNjY…IMG_2174.jpg?type=w800 could save 25.1KiB (19% reduction).
Compressing http://static.naver.net/blog/banner_mymenubot.png could save 24.4KiB (30% reduction).
Compressing http://mblogthumb4.phinf.naver.net/MjAxNzEyMTBfNzg…39737664.jpg?type=w800 could save 23KiB (16% reduction).
Compressing http://mblogthumb3.phinf.naver.net/MjAxODAxMjlfMjA…A1%BF%E4.jpg?type=s140 could save 1.4KiB (16% reduction).
Compressing http://mblogthumb4.phinf.naver.net/MjAxODAxMjhfMjY…C1%F6%29.jpg?type=s140 could save 1.2KiB (16% reduction).
Compressing http://mblogthumb1.phinf.naver.net/MjAxODAxMjlfMjA…IMG_9735.JPG?type=s140 could save 1.2KiB (13% reduction).
Compressing http://mblogthumb1.phinf.naver.net/MjAxODAxMjJfMjY…IMG_0703.JPG?type=s140 could save 1.2KiB (15% reduction).
Compressing http://mblogthumb4.phinf.naver.net/MjAxODAxMjlfNyA…IMG_6277.JPG?type=s140 could save 1.1KiB (14% reduction).
Compressing http://mblogthumb2.phinf.naver.net/MjAxODAxMjlfMTg…DSC_1631.JPG?type=s140 could save 1.1KiB (16% reduction).
Compressing http://mblogthumb1.phinf.naver.net/MjAxODAxMjlfMjQ…IMG_5992.JPG?type=s140 could save 1KiB (13% reduction).
Compressing http://mblogthumb2.phinf.naver.net/MjAxODAxMzBfMjE…ED%BE%CF.jpg?type=s140 could save 850B (12% reduction).
Compressing http://mblogthumb1.phinf.naver.net/MjAxODAxMjlfMjA…_%288%29.jpg?type=s140 could save 823B (13% reduction).
Compressing http://mblogthumb1.phinf.naver.net/MjAxODAxMjZfMjU…6_184622.jpg?type=s140 could save 620B (13% reduction).

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.

None of the final above-the-fold content could be rendered even 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 6.2KiB (50% reduction).

Compressing http://m.blog.naver.com/rego/RecommendationPostLis…orySeq=5&currentPage=1 could save 5.1KiB (53% reduction).
Compressing http://m.blog.naver.com/rego/TodayHotTopic.nhn could save 938B (43% reduction).
Compressing http://m.blog.naver.com/rego/BlogUserInfo.nhn could save 114B (36% reduction).

priority - 0 Reduce server response time

blog.me Mobile Resource Breakdown

Total Resources33
Number of Hosts10
Static Resources23
JavaScript Resources8
CSS Resources2

blog.me mobile page usability

Last tested: 2018-01-29


Mobile Usability Good
98/100

blog.me Mobile Usability Test Quick Summary


priority - 1 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="/PostList.nhn?…d=withborinuri" class="writer">보리누리</a> and 9 others are close to other tap targets.

blog.me Mobile Resource Breakdown

Total Resources33
Number of Hosts10
Static Resources23
JavaScript Resources8
CSS Resources2

blog.me HTML validation

Errors

The “charset” attribute on the “link” element is obsolete. Use an HTTP Content-Type header on the linked resource instead.

Line: 31 Column: 5 - 157
"...tle> <link rel="stylesheet" type="text/css" href="https://ssl.pstatic.net/t.static.blog/section/versioning/section_ngapp-4235603_https.css" charset="UTF-8" /> ..."

Attribute “bg-body-click” not allowed on element “body” at this point.

Line: 47 Column: 1 - 20
"... </head> <body bg-body-click> <ui-v..."

Stray start tag “script”.

Line: 50 Column: 1 - 8
"...> </body> <script> ..."

blog.me similar domains

Similar domains:
www.blog.com
www.blog.net
www.blog.org
www.blog.info
www.blog.biz
www.blog.us
www.blog.mobi
www.log.me
www.blog.me
www.vlog.me
www.bvlog.me
www.vblog.me
www.glog.me
www.bglog.me
www.gblog.me
www.hlog.me
www.bhlog.me
www.hblog.me
www.nlog.me
www.bnlog.me
www.nblog.me
www.bog.me
www.bpog.me
www.blpog.me
www.bplog.me
www.boog.me
www.bloog.me
www.bolog.me
www.bkog.me
www.blkog.me
www.bklog.me
www.blg.me
www.blig.me
www.bloig.me
www.bliog.me
www.blkg.me
www.blokg.me
www.bllg.me
www.blolg.me
www.bllog.me
www.blpg.me
www.blopg.me
www.blo.me
www.blof.me
www.blogf.me
www.blofg.me
www.blov.me
www.blogv.me
www.blovg.me
www.blot.me
www.blogt.me
www.blotg.me
www.blob.me
www.blogb.me
www.blobg.me
www.bloy.me
www.blogy.me
www.bloyg.me
www.bloh.me
www.blogh.me
www.blohg.me

blog.me Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


blog.me TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.