Tools & Wizards About Us
dic.naver.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

dic.naver.com

네이버 사전 (NAVER dictionary)

Page Load Speed

4.7 sec in total

First Response

927 ms

Resources Loaded

3.6 sec

Page Rendered

156 ms

dic.naver.com screenshot

About Website

Click here to check amazing Dic NAVER content for South Korea. Otherwise, check out these important facts you probably never knew about dic.naver.com

영어, 국어, 한자, 일본어, 중국어를 포함한 67종 언어로 총 3000만 표제어를 제공하는 네이버사전

Visit dic.naver.com

Key Findings

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

Performance Metrics

dic.naver.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

12/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.793

5/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

dic.naver.com

927 ms

common.css

546 ms

gnb.css

497 ms

dichome-core-1.js

7 ms

ci_naver.gif

66 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original Dic.naver.com, 63% (10 requests) were made to Dicimg.naver.net and 6% (1 request) were made to Static.naver.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Static.gn.naver.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 377.0 kB (78%)

Content Size

485.4 kB

After Optimization

108.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dic.naver.com main page is 485.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 205.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 174.8 kB

  • Original 205.2 kB
  • After minification 168.8 kB
  • After compression 30.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 36.4 kB, which is 18% 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 174.8 kB or 85% of the original size.

Image Optimization

-23%

Potential reduce by 10.8 kB

  • Original 47.5 kB
  • After minification 36.6 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. Obviously, Dic NAVER needs image optimization as it can save up to 10.8 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-81%

Potential reduce by 101.3 kB

  • Original 124.9 kB
  • After minification 115.8 kB
  • After compression 23.6 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 101.3 kB or 81% of the original size.

CSS Optimization

-84%

Potential reduce by 90.0 kB

  • Original 107.8 kB
  • After minification 102.7 kB
  • After compression 17.7 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. Dic.naver.com needs all CSS files to be minified and compressed as it can save up to 90.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (40%)

Requests Now

15

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dic NAVER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

dic.naver.com

dic.naver.com

927 ms

common.css

common.css

546 ms

gnb.css

gnb.css

497 ms

dichome-core-1.js

dichome-core-1.js

7 ms

ci_naver.gif

ci_naver.gif

66 ms

bg_dichome.gif

bg_dichome.gif

31 ms

btn_search.gif

btn_search.gif

29 ms

ico_main_u.gif

ico_main_u.gif

482 ms

line_container.gif

line_container.gif

36 ms

sp_main.png

sp_main.png

76 ms

ico_trans.gif

ico_trans.gif

76 ms

banner_line.gif

banner_line.gif

75 ms

sp_footer.png

sp_footer.png

61 ms

bu_bar_n.gif

bu_bar_n.gif

61 ms

m

m

410 ms

gnb_utf8.nhn

gnb_utf8.nhn

1598 ms

Accessibility Review

dic.naver.com accessibility score

72

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

dic.naver.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

dic.naver.com SEO score

99

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dic.naver.com 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 Dic.naver.com 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.

Social Sharing Optimization

dic.naver.com

Open Graph data is detected on the main page of Dic NAVER. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: