Show

Blog.me 네이버 블로그

Need help with your SEO?
Online Status
Online

Server IP address resolved: Yes
Http response code: 200
Response time: 1.38 sec.
Last Checked: 02/27/2019

Blog.me receives about six hundred thousand unique visitors and nine hundred thousand pageviews per day. The estimated value of blog.me is ten million USD. Each unique visitor makes about 1.58 pageviews on average.

Over the time blog.me has been ranked as high as 519 in the world, while most of its traffic comes from Korea, where it reached as high as 15 position.

It’s good for blog.me that their server is also located in Korea, as that enables the majority of their visitors to benefit from a much faster page load time.

At the time of the last check (January 28, 2019) blog.me has a valid and up-to-date wildcard SSL certificate that expires on January 02, 2020.

According to Google Safe Browsing, Google Safe Search, Symantec and Web of Trust blog.me is quite a safe domain.

Mobile-Friendly test indicates that blog.me is well optimized for mobile and tablet devices, however website page loading time could be improved.

Global Rank
757
Average Load Time
0.32sec
Links In Count
6,502
Website Value
$12.0 M
Overview
Last Updated: 06/16/2019
Overall result - "blog.me" is SAFE.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Last Updated: 01/12/2019
NCS "blog.me" OK.

Norton ConnectSafe evaluates blog.me for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search
Last Updated: 10/10/2016
GSS "blog.me" OK.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing
Last Updated: 02/18/2019
Malware not found at "blog.me".
"blog.me" is not a phishing page.
"blog.me" does not install unwanted software.
"blog.me" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 01/09/2019
SA "blog.me" OK.

McAfee assesses blog.me for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze blog.me for mature or inappropriate content, only security checks are evaluated.

Web of Trust
Last Updated: 01/09/2019
WOT "blog.me" VERY GOOD.

The WOT calculates reputation of the blog.me. This reputation system receives ratings from users and information from third-party sources, assesses the blog.me for safety features and confirms, whether blog.me is suitable for children.

SSL Information
Domain *.blog.me
Issuer DigiCert SHA2 Secure Server CA
Algorithm RSA-SHA256
Valid form 12/28/2016
Expiration 01/02/2020
Signed Certificate is not self signed
Additional Domains *.blog.me
blog.me
Server Location
Gyeonggi-do
Republic of
Korea
ASN Information

ASN ID: 23576
ASN Title: NHN-AS-KR NBP, KR

Last Update: 05/29/2019

% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

% Information related to 'AS23552 - AS23601'

as-block: AS23552 - AS23601
descr: KRNIC-ASBLOCK-AP
descr: KRNIC
descr: Korea Network Information Center
country: KR
admin-c: HM127-AP
tech-c: HM127-AP
remarks: Block of 50 AS numbers from AS23552to AS23601
remarks: for assignment to KRNIC members
remarks: Authoritative information regarding AS Number
remarks: assignments made from within this block can also be
remarks: queried at whois.nic.or.kr
mnt-by: APNIC-HM
mnt-lower: MNT-KRNIC-AP
last-modified: 2008-09-04T06:40:26Z
source: APNIC

person: Host Master
address: 135 Jungdae-ro Songpa-gu Seoul
country: KR
phone: +82-2-405-5118
e-mail: hostmaster@nic.or.kr
nic-hdl: HM127-AP
mnt-by: MNT-KRNIC-AP
last-modified: 2016-03-15T04:20:59Z
source: APNIC

% Information related to 'AS23552 - AS24575'

as-block: AS23552 - AS24575
descr: APNIC ASN block
remarks: These AS numbers are further assigned by APNIC
remarks: to APNIC members and end-users in the APNIC region
remarks: AS23889 has been transfered to AfriNIC
admin-c: HM20-AP
tech-c: HM20-AP
mnt-by: APNIC-HM
mnt-lower: APNIC-HM
last-modified: 2009-09-29T06:04:16Z
source: APNIC

role: APNIC Hostmaster
address: 6 Cordelia Street
address: South Brisbane
address: QLD 4101
country: AU
phone: +61 7 3858 3100
fax-no: +61 7 3858 3199
e-mail: helpdesk@apnic.net
admin-c: AMS11-AP
tech-c: AH256-AP
nic-hdl: HM20-AP
remarks: Administrator for APNIC
notify: hostmaster@apnic.net
mnt-by: MAINT-APNIC-AP
last-modified: 2013-10-23T04:06:51Z
source: APNIC

% Information related to 'AS23576'

% Abuse contact for 'AS23576' is 'hostmaster@nic.or.kr'

aut-num: AS23576
as-name: nhn-AS-KR
descr: NBP
country: KR
admin-c: AM1569-AP
tech-c: AM1569-AP
import: from AS10026
action pref=90;
accept ANY
import: from AS2914
action pref=90;
accept ANY
import: from AS3386
action pref=90;
accept ANY
import: from AS9318
action pref=90;
accept ANY
export: to AS10026
announce AS23576
export: to AS2914
announce AS23576
export: to AS3386
announce AS23576
export: to AS9318
announce AS23576
default: to AS10026
action pref=90;
networks ANY
mnt-by: MNT-KRNIC-AP
mnt-irt: IRT-KRNIC-KR
last-modified: 2016-10-25T06:08:41Z
source: APNIC

irt: IRT-KRNIC-KR
address: Seocho-ro 398, Seocho-gu, Seoul, Korea
e-mail: hostmaster@nic.or.kr
abuse-mailbox: hostmaster@nic.or.kr
admin-c: IM574-AP
tech-c: IM574-AP
auth: # Filtered
mnt-by: MNT-KRNIC-AP
last-modified: 2017-10-19T07:36:36Z
source: APNIC

person: AS Manager
address: Gyeonggi-do Bundang-gu, Seongnam-si Buljeong-ro 6
country: KR
phone: +82-31-1588-3820
e-mail: dl_noc@navercorp.com
nic-hdl: AM1569-AP
mnt-by: MNT-KRNIC-AP
last-modified: 2017-11-23T05:54:31Z
source: APNIC

% Information related to 'AS23576'

aut-num: AS23576
as-name: nhn-AS-KR-KR
descr: NBP
country: KR
import: from AS9318 action pref=100 accept ANY
import: from AS3386 action pref=100 accept ANY
import: from AS10026 action pref=90 accept ANY
import: from AS2914 action pref=90 accept ANY
export: to AS9318 announce AS23576
export: to AS3386 announce AS23576
export: to AS10026 announce AS23576
export: to AS2914 announce AS23576
admin-c: KK531-KR
tech-c: ER531-KR
mnt-by: MNT-KRNIC-AP
mnt-irt: IRT-KRNIC-KR
changed: hostmaster@nic.or.kr
source: KRNIC

person: AS Manager
address: Gyeonggi-do Bundang-gu, Seongnam-si Buljeong-ro 6
address: 6
country: KR
phone: +82-31-1588-3820
e-mail: dl_noc@navercorp.com
nic-hdl: ER531-KR
mnt-by: MNT-KRNIC-AP
changed: hostmaster@nic.or.kr
source: KRNIC

person: AS Manager
address: Gyeonggi-do Bundang-gu, Seongnam-si Buljeong-ro 6
address: 6
country: KR
phone: +82-31-1588-3820
e-mail: dl_noc@navercorp.com
nic-hdl: KK531-KR
mnt-by: MNT-KRNIC-AP
changed: hostmaster@nic.or.kr
source: KRNIC

% This query was served by the APNIC Whois Service version 1.88.15-46 (WHOIS-US4)

HTML Metatags
Title
네이버 블로그
The title is too short, it may not provide search engines and users with enough information to understand the relevancy of your page. You should try to keep the length of the title somewhere between at least 10 characters and 70 characters.
Description
The description is too short. If a description is too short, the search engines may add text found elsewhere on the page. Note that search engines may show a different description from the one you have authored if they feel it may be more relevant to a user's search.
Encoding
UTF-8
You should always specify the encoding used for an HTML page. If you don't, you risk that characters in your content are incorrectly interpreted. This is not just an issue of human readability, increasingly machines need to understand your data too.
Language
ko Korean
Identifying the language of your content allows you to automatically do a number of things, from changing the look and behavior of a page, to assisting search engines in extracting information. If part of the page uses text in a different language, you can add a language attribute with a different value to the element that surrounds that content.
Language Region
Not Found
Images
Attribute ALT
Success, no any <img> without defined ALT attribute. Alt text is helpful to end users if they have images disabled or if the image does not properly load.
As a general rule, search engines do not interpret the content of image files. The text provided in the <img alt> attribute enables the site owner to provide relevant information to the search engine and to the end user.
H1-H6 Tags Information

For search engines, <H> tags helps understand the structure of the text on a page better. For users, headings are like anchors in a wall of text, navigating them through the page and making it easier to digest. The <h1> tag reinforces the core keyword(s) found in the <title>, <description>, and the <body>. We recommend that the <h1> tag includes keywords that reflect the contents of the page and that it is not longer than 150 characters in length, but don’t overuse the tags and the keywords in them. Keep it readable for users.

H1
The H1 tag is missing
Your H1 introduces the topic your page is all about, just as a title tells a reader what a book is all about. Add a header to the page by using a H1 tag and place it within the BODY of the page source.
H2
The H2s are akin to book chapters, describing the main topics you’ll cover in sections of the article.
H3
Subsequent headers, H3s to H6s, serve as additional sub-headings within each section, just as a book chapter may be split up by multiple sub-topics.
H4
H5
H6
Iframes Information
iFrame
iFrames not found.
Since search engines consider the content in iframes to belong to another website, the best you can hope for is no effect on SEO. Iframes tend to neither help nor hurt your search engine ranking. For this reason, it’s best to refrain from using iframes on main pages that you want to rank high in search engine results. Instead, fill high-priority pages with useful, unique content and save iframes for other pages.
Code To Text Ratio
Code To Text Ratio
0.22 %
A good code to text ratio is anywhere from 25 to 70 percent. This percentage refers to the visible text ratio, as opposed to HTML elements, image tags and other non-visible information. This has become especially apparent since search engines, such as Google, released the Panda update which placed importance on content-driven sites.
Favicons

Favicons are the little piece of graphic that represents your brand on browser tabs, bookmark lists, search history, search ads and even search results. These files are placed in a file called favicon.ico and placed in the root directory of a website. There are no direct SEO effects of having favicons. However, there may be indirect benefits such as increased usability of site and bookmarks. It makes your website look more professional and help a users to remember your site while browsing through multiple URLs. If you want to get mentioned benefits you have to specify icons for different web browsers and sometimes even for different mobiles.

Default Favicon
Line 13, https://section.blog.naver.com/favicon.ico?2
Backup icon for most desktop browsers (if no icon of the right size is found). Tag format <link rel="shortcut icon" href="path-to-16x16-icon.ico" type="image/x-icon" />
16x16 Optional Favicon
Standard icon for outdated browsers or small resolution hand held devices. Tag format <link rel="icon" type="image/png" sizes="16x16" href="path-to-16x16.png">
32x32 Optional Favicon
Standard for most desktop browsers. Tag format <link rel="icon" sizes="32x32" href="path-to-32x32.png">
96x96 Optional Favicon
Mostly used as GoogleTV icon. Tag format <link rel="icon" type="image/png" sizes="96x96" href="path-to-96x96.png">
Default Apple Icon
Backup icon for apple devices (if no icon of the right size is found). Preferrable size 60x60. Tag format <link rel="apple-touch-icon" sizes="72x72" href="path-to-small-icon.png">
180x180 Apple Icon
iPhone 6 plus icons. Tag format <link rel="apple-touch-icon" sizes="180x180" href="path-to-180x180.png">
152x152 Apple Icon
iPad, iPad mini icons. Tag format <link rel="apple-touch-icon" sizes="152x152" href="path-to-icon-152x152.png">
167x167 Apple Icon
iPad Pro icon. Tag format <link rel="apple-touch-icon" sizes="167x167" href="path-to-167x167.png">
Robots.txt Information

Robots.txt is a text file that website owners can create to tell search engine bots how to crawl and index pages on their site.

Robots File
Robots File Loaded successfully (/robots.txt)
You can have multiple lines of instructions to allow or disallow specific URLs and add multiple sitemaps. If you do not disallow a URL, then search engine bots assume that they are allowed to crawl it.
Disallow
1 record(s)
Other User-Agent
1 record(s)
Default User-Agent
Not found
Sitemap

A sitemap is an XML file where is provided information about each URL: when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. Search engines crawling bots read this file to more efficiently and intelligently crawl your site and to find URLs that may be isolated from rest of the site's content.

Default Sitemap
Sitemap File failed Loaded (/sitemap.xml)
Your site will benefit from having a sitemap.
WHOIS

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-11-08T12:43:21Z

DNS Records
HostA RecordTTL
blog.me125.209.214.79300
HostMX RecordPriorityTTL
HostNS RecordTTL
blog.mens2.naver.com86400
blog.mens1.naver.com86400
HostTXT RecordTTL

ns1.naver.com
TTL: 300
Email address: webmaster.naver.com
Serial: 2016080101
Refresh: 21600
Retry: 1800
Expire: 1209600
Minimum: 180

Errors
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" /> ..."
Line: 47 Column: 1 - 20
"... </head> <body bg-body-click> <ui-v..."
Line: 50 Column: 1 - 8
"...> </body> <script> ..."

Last tested: 05/20/2017

Desktop
Desktop Speed
82%
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).

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)

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

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.

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

Desktop Resource Breakdown
Total Resources144
Number of Hosts24
Static Resources131
JavaScript Resources23
CSS Resources4

Last tested: 01/29/2018

Mobile
Mobile Usability
98%
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 final.

Mobile Speed
50%
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

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

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

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.

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

Mobile Resource Breakdown
Total Resources33
Number of Hosts10
Static Resources23
JavaScript Resources8
CSS Resources2