46.9 sec in total
802 ms
36.8 sec
9.3 sec
Click here to check amazing Cnet content for South Korea. Otherwise, check out these important facts you probably never knew about cnet.co.kr
Visit cnet.co.krWe analyzed Cnet.co.kr page load time and found that the first response time was 802 ms and then it took 46.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
cnet.co.kr performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value19.2 s
0/100
25%
Value16.1 s
0/100
10%
Value70 ms
99/100
30%
Value0.03
100/100
15%
Value9.0 s
33/100
10%
802 ms
18852 ms
669 ms
455 ms
106 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 79% of them (118 requests) were addressed to the original Cnet.co.kr, 5% (7 requests) were made to Tenping.kr and 4% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (18.9 sec) belongs to the original domain Cnet.co.kr.
Page size can be reduced by 1.9 MB (32%)
6.1 MB
4.2 MB
In fact, the total size of Cnet.co.kr main page is 6.1 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. 55% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 262.6 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 262.6 kB or 87% of the original size.
Potential reduce by 265.1 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. Cnet images are well optimized though.
Potential reduce by 502.4 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 502.4 kB or 73% of the original size.
Potential reduce by 912.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. Cnet.co.kr needs all CSS files to be minified and compressed as it can save up to 912.2 kB or 83% of the original size.
Number of requests can be reduced by 41 (29%)
139
98
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cnet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
cnet.co.kr
802 ms
www.cnet.co.kr
18852 ms
star-rating.css
669 ms
validationEngine.jquery.css
455 ms
nanumgothic.css
106 ms
js_composer.css
1759 ms
css
146 ms
css
199 ms
css
198 ms
main.min.css
3183 ms
font-awesome.min.css
4017 ms
custom-7a15e73863.css
3820 ms
media.min.css
2665 ms
royalslider.css
2917 ms
style.css
4075 ms
ubermenu.min.css
4793 ms
jquery.js
4834 ms
jquery-migrate.min.js
4555 ms
bootstrap.js
5332 ms
star-rating.js
4953 ms
modernizr.js
5012 ms
svg-icons.min.js
5470 ms
_hcd_.js
5308 ms
style.css
1295 ms
analytics.js
165 ms
cnet-mini-logo.png
780 ms
search_btn.png
477 ms
korea_edition.png
478 ms
Cnetkorea_logo_full.png
974 ms
Logo_floating.jpg
777 ms
btn_search.png
973 ms
20160407_facebook_live_examples.jpg
1859 ms
20160408_win10_2in1_intel.jpg
1953 ms
770Alexaeastereggs.jpg
2359 ms
20160406_cnetkorea_to_open_wearable_run_title.jpg
2522 ms
770CamPlus.jpg
2605 ms
20160404_drone_shoot.jpg
2869 ms
770VRrollercoaster.jpg
4183 ms
20160401_intel_unite.jpg
3934 ms
NanumGothic-Regular.woff
462 ms
NanumGothic-Bold.woff
735 ms
NanumGothic-ExtraBold.woff
852 ms
collect
50 ms
collect
377 ms
20160331_komatrade_title.jpg
3046 ms
770CarTech101Autostartstop1.jpg
1434 ms
arrows.png
433 ms
jquery.event.drag-1.5.min.js
471 ms
jquery.touchSlider.js
4688 ms
face.png
2253 ms
Google-.png
7329 ms
Comment.png
1699 ms
ASUS_ZDNet_Webbanner_ME581CL_300x180_F.jpg
6618 ms
770Bosevssonos.jpg
3842 ms
20160406_sony_heargo_designer_title.jpg
3505 ms
20160406_phone_half_save_title.jpg
4248 ms
770TomorrowDaily335.jpg
5341 ms
880Trekz.jpg
6102 ms
770lgg5fRIENDS3.jpg
5397 ms
770samsungGtabpros.jpg
5884 ms
770Nokias60000cameramakesvideoforVRheadset.jpg
6991 ms
20160331_win10_anniversary_update_title.jpg
6586 ms
20160329_luna_watch_title.jpg
7198 ms
20160328_pro_laptop_vol02_title.jpg
7168 ms
GAZE-POP-UP2.jpg
7844 ms
770432-Everything-we-know-about-Nike-s-new-self-lacing-shoe-The-Nike-HyperAdapt-1.0.mp4_20160328_094954.718.jpg
8938 ms
20160322_lge_g5_title.jpg
7286 ms
770432-no-layer-The-history-of-the-telephone.jpg
7873 ms
20160324_win10_edu.jpg
7883 ms
20160324_microsoft_tay_title.jpg
7873 ms
20160324_pebble_lay_off_title.jpg
8132 ms
20160322_intel_security_title.jpg
8165 ms
top5-batman-880495.jpg
10348 ms
main@x90
1024 ms
20160329_luna_watch_title-70x53.jpg
7820 ms
20160322_lge_g5_title-70x53.jpg
7823 ms
20160308_canvio_premium_title-70x53.jpg
8245 ms
20160307_cas1_title-70x53.jpg
7980 ms
20160217_verus_elevencore_title-70x53.jpg
7998 ms
20160125_imac_5k_2015_title-70x53.jpg
8089 ms
20160121_sol_title-70x53.jpg
8205 ms
20160105_huawei_y6_title-70x53.jpg
8364 ms
20151228_zikto_walk_title-70x53.jpg
8382 ms
20151223_nexus6p_title-70x53.jpg
8409 ms
770lgg5fRIENDS3-70x53.jpg
8515 ms
adsbytenping.min.js
1453 ms
ubermenu.min.js
8210 ms
ubermenu.sticky.min.js
7410 ms
jquery.royalslider.js
8416 ms
external.nhn
665 ms
wearable_run-3.jpg
12906 ms
plugins.min.js
8071 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
57 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
57 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
58 ms
iframeResizer.min.js
234 ms
desktop-tablet.min.js
6956 ms
showadbox
248 ms
sp_postwidget_150409.png
659 ms
IjV4_UvDJfnUDolD3-8CgtJgvh5Q.jpg
1461 ms
post_base.js
699 ms
jindo_component.js
688 ms
mug.pubcenter.postWidget.js
659 ms
style.css
267 ms
jquery.min.js
86 ms
iframeResizer.contentWindow.min.js
536 ms
2016040803330001_Dis_20160408091616.jpg
5198 ms
icon-person_ad.png
270 ms
logo_ad.png
475 ms
collect
25 ms
desktop.min.js
5688 ms
main.min.js
6716 ms
js_composer_front.js
5716 ms
20160331_komatrade_title-70x53.jpg
5347 ms
20160328_pro_laptop_vol02_title-70x53.jpg
5751 ms
%EC%95%84%EC%9D%B4%ED%8C%A8%EB%93%9C%ED%94%84%EB%A1%9C-70x53.jpg
5330 ms
20160311_apple_event_invitation-70x53.jpg
6256 ms
20151215_cyber_threat_title-70x53.jpg
6117 ms
20151214_onedrive_storage_howto_title-70x53.jpg
5678 ms
20151211_ios_mail_drop_howto_title-70x53.jpg
5649 ms
Untitled-11-70x53.jpg
5252 ms
news
6324 ms
android-6-marshmallow1-70x53.jpg
4755 ms
20151023_iphone6s_ap_howto_title-70x53.jpg
4490 ms
w10-review-surface-nate-70x53.jpg
4281 ms
coco.png
4644 ms
cnet_logo_footer.png
3914 ms
clean-site.png
3898 ms
cnet_face.png
3889 ms
cnet_twit.png
3795 ms
cnet_google.png
3728 ms
cnet_youtube.png
3705 ms
cnet_rss.png
3715 ms
main_icon1.png
3739 ms
main_icon2.png
3847 ms
main_icon3.png
3977 ms
main_icon4.png
3748 ms
main_icon5.png
3809 ms
main_icon6.png
3860 ms
main_icon7.png
3879 ms
main_icon8.png
3775 ms
main_icon9_01.png
3679 ms
main_icon10.png
4797 ms
main_icon11.png
3589 ms
main_icon12.png
3412 ms
clock.png
3250 ms
wl6.js
3514 ms
fontawesome-webfont.woff
2756 ms
news
2584 ms
cnet.co.kr accessibility score
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
Buttons do not have an accessible name
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.
cnet.co.kr 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
cnet.co.kr 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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cnet.co.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 Cnet.co.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.
cnet.co.kr
Open Graph description is not detected on the main page of Cnet. 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: