5.9 sec in total
692 ms
4.9 sec
284 ms
Welcome to naver.kr homepage info - get ready to check NAVER best content right away, or after learning these important things about naver.kr
네이버 메인에서 다양한 정보와 유용한 컨텐츠를 만나 보세요
Visit naver.krWe analyzed Naver.kr page load time and found that the first response time was 692 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
naver.kr performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value15.8 s
0/100
25%
Value13.1 s
2/100
10%
Value3,300 ms
2/100
30%
Value0.1
89/100
15%
Value19.4 s
2/100
10%
692 ms
479 ms
627 ms
437 ms
1346 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Naver.kr, 55% (40 requests) were made to Img.naver.net and 10% (7 requests) were made to S.pm.naver.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Castbox.shopping.naver.com.
Page size can be reduced by 712.0 kB (59%)
1.2 MB
488.6 kB
In fact, the total size of Naver.kr main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 651.1 kB which makes up the majority of the site volume.
Potential reduce by 70.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 70.8 kB or 77% of the original size.
Potential reduce by 28.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. NAVER images are well optimized though.
Potential reduce by 485.5 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 485.5 kB or 75% of the original size.
Potential reduce by 127.2 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Naver.kr needs all CSS files to be minified and compressed as it can save up to 127.2 kB or 82% of the original size.
Number of requests can be reduced by 22 (31%)
71
49
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NAVER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
naver.kr
692 ms
www.naver.com
479 ms
main_v20160223.css
627 ms
api_atcmp_0319.css
437 ms
www.css
1346 ms
nlog_20160114.min.js
625 ms
loginv4.js
1575 ms
JEagleEyeClient_20120111.min.js
42 ms
m
1234 ms
sp_main_high151118.png
659 ms
btn_atcmp_down_on.gif
441 ms
img_atcmp15.gif
34 ms
1458453600663.jpg
691 ms
sp_vertical.png
652 ms
sp_main151118.png
654 ms
nmms_224940510.gif
651 ms
nmms_184056832.png
654 ms
blank.gif
651 ms
366.gif
656 ms
020.gif
655 ms
045.gif
657 ms
005.gif
655 ms
011.gif
657 ms
025.gif
657 ms
330.gif
742 ms
044.gif
655 ms
nsd184430988.jpg
657 ms
029.gif
657 ms
056.gif
658 ms
016.gif
658 ms
mobile_180425813968.jpg
658 ms
mobile_180200918946.jpg
659 ms
mobile_17451086328.jpg
683 ms
mobile_16444675136.jpg
659 ms
mobile_16390193266.jpg
660 ms
mobile_163651921673.jpg
661 ms
mobile_16354847760.jpg
662 ms
dummy_1X1.jpg
662 ms
btn_search.png
639 ms
dr
699 ms
sp_mn160223.png
597 ms
sp_rgt.png
595 ms
bg_newscast.gif
597 ms
sp_login_20150113.gif
257 ms
ipsec.nhn
215 ms
dr
707 ms
shopAdBox.nhn
1605 ms
jindo.all.20150511.min.js
11 ms
ntop1_20160319.min.js
3 ms
ntop2_20160114.min.js
5 ms
ntop3_20151216.min.js
5 ms
stop_message.png
342 ms
timeboard_v1.min.css
671 ms
common.min.css
472 ms
1_2934.jpg
8 ms
bg_timeboard.png
672 ms
it.min.js
4 ms
da.sibo.min.js
5 ms
da_access.png
5 ms
_shopboxR0005_v1.css
457 ms
lazyload.js
412 ms
sp_shop.png
19 ms
blank.gif
14 ms
da.picnic.min.js
3 ms
20160317135510-JjYZOEZN.gif
5 ms
mobile_16343265480.jpg
27 ms
1458438182130.jpg
26 ms
mobile_163326105356.jpg
20 ms
mobile_163150129589.jpg
59 ms
mobile_110816494627.jpg
20 ms
mobile_111126667894.jpg
20 ms
mobile_11151765125.jpg
21 ms
_shopboxR0003_v9.js
21 ms
naver.kr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
naver.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
naver.kr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naver.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Naver.kr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
naver.kr
Open Graph data is detected on the main page of NAVER. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: