Access jr.naver.com. 쥬니어 네이버

jr.naver.com screenshot

23

Performance

Renders faster than
42% of other websites
80

Accessibility

Visual factors better than
that of 49% of websites
83

Best Practices

More advanced features
available than in
55% of websites
82

SEO

Google-friendlier than
44% of websites

First Response

1.1 sec

Resources Loaded

6.7 sec

Page Rendered

367 ms

jr.naver.com screenshot

About Website

Visit jr.naver.com now to see the best up-to-date Jr Naver content for South Korea and also check out these interesting facts you probably never knew about jr.naver.com

Visit jr.naver.com

Key Findings

We analyzed Jr.naver.com page load time and found that the first response time was 1.1 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

jr.naver.com

1069 ms

jrnaver_151126.css

694 ms

naver_web_player_2004_min.js

1676 ms

rmcplayer3_ext_p2p_20131004.js

719 ms

jindo.min.1.5.1.js

276 ms

Our browser made a total of 155 requests to load all elements on the main page. We found that 4% of them (6 requests) were addressed to the original Jr.naver.com, 63% (98 requests) were made to Image.jr.naver.com and 17% (26 requests) were made to Dthumb.phinf.naver.net. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Image.jr.naver.com.

Content Size

3.3 MB

After Optimization

2.3 MB

In fact, the total size of Jr.naver.com main page is 3.3 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 78.5 kB

Original 92.9 kB
After minification 72.6 kB
After compression 14.4 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. This page needs HTML code to be minified as it can gain 20.3 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 78.5 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 84.9 kB

Original 2.0 MB
After minification 1.9 MB

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. Jr Naver images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 807.3 kB

Original 1.1 MB
After minification 1.0 MB
After compression 283.1 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 807.3 kB or 74% of the original size.

CSS Optimization

-80%

Potential reduce by 37.0 kB

Original 46.0 kB
After minification 40.4 kB
After compression 9.0 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. Jr.naver.com needs all CSS files to be minified and compressed as it can save up to 37.0 kB or 80% of the original size.

Requests Now

154

After Optimization

131

The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jr 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 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

KO
Encoding

EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jr.naver.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Korean. Our system also found out that Jr.naver.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

jr.naver.com

Open Graph description is not detected on the main page of Jr Naver. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: