14.4 sec in total
5.8 sec
7.6 sec
985 ms
Visit m.daum.net now to see the best up-to-date M Daum content for South Korea and also check out these interesting facts you probably never knew about m.daum.net
다양한 콘텐츠를 소비하는 공간, 다음에서 당신의 관점을 넓혀보세요.
Visit m.daum.netWe analyzed M.daum.net page load time and found that the first response time was 5.8 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
m.daum.net performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.3 s
2/100
25%
Value10.9 s
6/100
10%
Value760 ms
39/100
30%
Value0.014
100/100
15%
Value16.2 s
5/100
10%
5820 ms
616 ms
456 ms
597 ms
598 ms
Our browser made a total of 15 requests to load all elements on the main page. We found that 7% of them (1 request) were addressed to the original M.daum.net, 53% (8 requests) were made to M2.daumcdn.net and 13% (2 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain M.daum.net.
Page size can be reduced by 605.7 kB (67%)
905.3 kB
299.6 kB
In fact, the total size of M.daum.net main page is 905.3 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. 15% of websites need less resources to load. HTML takes 813.6 kB which makes up the majority of the site volume.
Potential reduce by 596.1 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 596.1 kB or 73% of the original size.
Potential reduce by 1.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. M Daum images are well optimized though.
Potential reduce by 8.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 8.1 kB or 64% of the original size.
We found no issues to fix!
14
14
The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Daum. According to our analytics all requests are already optimized.
m.daum.net
5820 ms
logo_daum_rw.png
616 ms
20160222024926793.png
456 ms
014822849.png
597 ms
img_sg_v9.png
598 ms
ico_mtop_160219.png
598 ms
noimg_1_1.gif
595 ms
bar_graph_160222.png
693 ms
img_mtop_v14.png
434 ms
btn_swipe_v2.png
435 ms
tiara-iframe.min.js
291 ms
footsteps
1740 ms
roosevelt_sher.js
11 ms
bnr_layer_tarot.jpg
14 ms
bnr_layer_close.jpg
5 ms
m.daum.net accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
<frame> or <iframe> elements do not have a title
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.
m.daum.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
m.daum.net SEO score
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 M.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 M.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.
m.daum.net
Open Graph data is detected on the main page of M Daum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: