6.7 sec in total
1.3 sec
5.2 sec
245 ms
Welcome to dosin.com homepage info - get ready to check Dosin best content right away, or after learning these important things about dosin.com
Visit dosin.comWe analyzed Dosin.com page load time and found that the first response time was 1.3 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
dosin.com performance score
1288 ms
255 ms
551 ms
315 ms
221 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dosin.com, 42% (38 requests) were made to Blogimgs.naver.net and 18% (16 requests) were made to T.static.blog.naver.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Gn.naver.com.
Page size can be reduced by 1.2 MB (75%)
1.6 MB
389.5 kB
In fact, the total size of Dosin.com main page is 1.6 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 202 B
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 202 B or 39% of the original size.
Potential reduce by 16.7 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, Dosin needs image optimization as it can save up to 16.7 kB or 57% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 919.5 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 919.5 kB or 74% of the original size.
Potential reduce by 261.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. Dosin.com needs all CSS files to be minified and compressed as it can save up to 261.2 kB or 84% of the original size.
Number of requests can be reduced by 66 (75%)
88
22
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dosin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
dosin.com
1288 ms
steve6
255 ms
Frameset-981964519.js
551 ms
PostList.nhn
315 ms
NBlogHidden.nhn
221 ms
Hidden-597428542.js
6 ms
MusicPlayer-449972894.js
17 ms
LayoutTopCommon-484882993.css
41 ms
player-846d457.css
57 ms
RemoveSubDomain-dea9950.js
63 ms
Jindo152-363950062.js
62 ms
LayoutTopCommon-730083628.js
61 ms
JindoComponent-318925938.js
81 ms
PostList-1027637939.css
60 ms
gnb_quirks_euckr.nhn
172 ms
likeit_blog.css
651 ms
likeit.css
652 ms
SeViewerBlog-165931490.css
77 ms
PostTopCommon-327917359.js
156 ms
splugin.js
628 ms
PostBottomCommon-1023812380.js
154 ms
PostBottomCommon_utf8-169531666.js
155 ms
likeIt.list.js
648 ms
allowSwfForChrome-7dd9772.js
142 ms
LayoutBottomCommon-902441421.js
137 ms
spc.gif
367 ms
PostList.nhn
272 ms
btn_confirm2.gif
706 ms
blogpfthumb.phinf.naver.net
1087 ms
0000_login.png
364 ms
btn_qk_set.gif
361 ms
btn_what2.gif
359 ms
btn_clse_ly2.gif
362 ms
spc.gif
362 ms
btn_urlcopy.gif
382 ms
btn_thin_close.gif
381 ms
btn_close8.gif
379 ms
ico_file.gif
383 ms
btn_download2.gif
383 ms
btn_cancel3.gif
383 ms
btn_close3.gif
403 ms
btn_close5.gif
402 ms
btn_confirm.gif
402 ms
btn_cancel.gif
406 ms
btn_close_1.gif
405 ms
btn_viewexif.gif
405 ms
btn_originaldn.gif
424 ms
tit_viewexif.gif
424 ms
ico_notice2.gif
423 ms
btn_close.gif
429 ms
btn_close3.gif
411 ms
btn_close.gif
410 ms
btn_ok.gif
426 ms
btn_close2.gif
426 ms
btn_confirm_pop2.gif
426 ms
btn_cancel_pop2.gif
428 ms
btn_close.gif
429 ms
ico_help.gif
679 ms
promo_npay.png
42 ms
bg_blog_menu.gif
1052 ms
bg_qk_ly2.gif
71 ms
0008_ico1_down.gif
68 ms
ico_tag.gif
10 ms
sp_post_btn.png
58 ms
lg_photoviewer.gif
73 ms
btn_blogsearch.gif
36 ms
btn_left.gif
17 ms
btn_right.gif
17 ms
btn_original2.png
19 ms
btn_close.gif
18 ms
0113_back.gif
52 ms
0103_image_1.gif
18 ms
shadow.png
41 ms
shadow02.png
41 ms
bg_not_available_word.gif
41 ms
WidgetListAsync.nhn
266 ms
0101_icon.gif
13 ms
btn_rst_clse.gif
24 ms
0008_arw.gif
94 ms
login_basic.gif
25 ms
spi_standard_20160222.css
55 ms
BlogTagListInfo.nhn
320 ms
index.html
1479 ms
icon_set.gif
48 ms
m
1429 ms
likeIt.list.main.js
22 ms
sp_spi_pc.png
63 ms
likeit.css
4 ms
likeit_blog.css
5 ms
getLoginStatus.nhn
1065 ms
dosin.com 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
<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.
dosin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
dosin.com 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dosin.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Dosin.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.
dosin.com
Open Graph description is not detected on the main page of Dosin. 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: