Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

daum.net

Daum

Page Load Speed

5.6 sec in total

First Response

685 ms

Resources Loaded

4.7 sec

Page Rendered

197 ms

daum.net screenshot

About Website

Click here to check amazing Daum content for South Korea. Otherwise, check out these important facts you probably never knew about daum.net

이용자 선택권을 강화한 뉴스, 세상의 모든 정보를 연결하는 검색. Daum에서 나의 관심 콘텐츠를 즐겨보세요.

Visit daum.net

Key Findings

We analyzed Daum.net page load time and found that the first response time was 685 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

daum.net performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

daum.net

685 ms

www.daum.net

895 ms

html5shiv-3.7.0.min.js

434 ms

top.js

474 ms

152729032.png

1485 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Daum.net, 23% (18 requests) were made to T1.daumcdn.net and 18% (14 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Icon.daumcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 633.3 kB (34%)

Content Size

1.8 MB

After Optimization

1.2 MB

In fact, the total size of Daum.net main page is 1.8 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 136.8 kB

  • Original 170.5 kB
  • After minification 170.1 kB
  • After compression 33.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 136.8 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 84.3 kB

  • Original 1.1 MB
  • After minification 1.0 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. Daum images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 412.2 kB

  • Original 565.2 kB
  • After minification 497.2 kB
  • After compression 153.0 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 412.2 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (17%)

Requests Now

76

After Optimization

63

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

Accessibility Review

daum.net accessibility score

60

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-*] attributes do not match their roles

High

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

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

High

[role] values are not valid

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

High

<frame> or <iframe> elements do not have a title

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

daum.net best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

daum.net SEO score

90

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 Daum.net 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 Daum.net 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

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