34.1 sec in total
1.8 sec
31.8 sec
507 ms
Welcome to danielhanps.com homepage info - get ready to check Danielhanps best content for South Korea right away, or after learning these important things about danielhanps.com
부산 서면, 부산화상치료, 부산화상흉터, 부산열상치료, 부산안면골절, 부산고압산소치료, 부산당뇨발치료, 부산당뇨발, 부산가슴성형, 부산안면윤곽, 디에이치 한승열원장, 돌출눈, 돌출눈수술, 편두통치료, 편두통, 부산눈썹문신, dh반영구, 부산성형외과전문의, 부산이물질제거, 부산 양악수술, 코성형, 눈성형, 부산성형외과순위, 부산비염수술, 부산성형외과여의사, ...
Visit danielhanps.comWe analyzed Danielhanps.com page load time and found that the first response time was 1.8 sec and then it took 32.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
danielhanps.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value7.9 s
3/100
25%
Value9.8 s
10/100
10%
Value310 ms
78/100
30%
Value0.162
72/100
15%
Value9.7 s
29/100
10%
1802 ms
802 ms
559 ms
1090 ms
1067 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 89% of them (108 requests) were addressed to the original Danielhanps.com, 2% (3 requests) were made to S.ytimg.com and 2% (2 requests) were made to Adlog.adinsight.co.kr. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Danielhanps.com.
Page size can be reduced by 619.4 kB (15%)
4.1 MB
3.5 MB
In fact, the total size of Danielhanps.com main page is 4.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. 50% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 46.3 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 7.5 kB, which is 14% 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 46.3 kB or 84% of the original size.
Potential reduce by 191.9 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. Danielhanps images are well optimized though.
Potential reduce by 370.9 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 370.9 kB or 81% of the original size.
Potential reduce by 10.4 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. Danielhanps.com needs all CSS files to be minified and compressed as it can save up to 10.4 kB or 81% of the original size.
Number of requests can be reduced by 17 (15%)
116
99
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Danielhanps. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
danielhanps.com
1802 ms
style.css
802 ms
slideX.css
559 ms
control.bxSlider.css
1090 ms
normal.js
1067 ms
jquery.js
5752 ms
jquery.easing.1.3.js
1350 ms
jquery.bxslider.js
2025 ms
control.bxslider.js
2475 ms
CommonMenu.js
2274 ms
slideX.js
2520 ms
common.js
2978 ms
trs_esc.js
892 ms
analytics.js
137 ms
sr.gif
776 ms
main_logo.jpg
239 ms
log.php
223 ms
main_menu01.jpg
262 ms
main_menu01_01.jpg
261 ms
main_menu01_02.jpg
469 ms
main_menu01_03.jpg
520 ms
main_menu01_04.jpg
521 ms
main_menu01_05.jpg
762 ms
main_menu01_06.jpg
800 ms
main_menu01_07.jpg
777 ms
main_menu01_08.jpg
954 ms
main_menu01_09.jpg
1053 ms
main_menu02.jpg
1052 ms
main_menu02_01.jpg
2103 ms
main_menu02_02.jpg
1323 ms
main_menu03.jpg
1323 ms
main_menu03_01.jpg
1574 ms
main_menu03_02.jpg
1575 ms
main_menu03_03.jpg
1827 ms
main_menu04.jpg
1826 ms
main_menu04_01.jpg
2080 ms
main_menu04_02.jpg
2079 ms
main_menu05.jpg
2400 ms
main_menu05_01.jpg
2401 ms
main_menu05_02.jpg
2400 ms
main_menu05_03.jpg
2630 ms
main_sns_ban01.jpg
2647 ms
main_sns_ban02.jpg
2645 ms
main_sns_ban03.jpg
2793 ms
main_sns_ban04.jpg
3018 ms
main_info.jpg
4216 ms
main_visual01.jpg
13647 ms
main_visual02.jpg
20222 ms
main_visual03.jpg
5544 ms
arr_le.png
3018 ms
arr_ri.png
3351 ms
main_btn_ov.png
3350 ms
p48y30Lemo4
284 ms
collect
71 ms
NanumGothic.woff
3339 ms
main_btn.png
3319 ms
main_ban01.jpg
6312 ms
www-embed-player-webp-vflEdCXO2.css
136 ms
www-embed-player.js
173 ms
base.js
279 ms
main_ban_20160118.jpg
5880 ms
main_ban02_01.jpg
6050 ms
main_ban02_02.jpg
5601 ms
F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js
145 ms
ad_status.js
144 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
195 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
197 ms
main_ban02_03.jpg
5903 ms
ASP_Conf.js
1013 ms
main_ban02_04.jpg
5820 ms
main_ban02_05.jpg
6431 ms
main_ban02_06.jpg
6055 ms
main_ban02_07.jpg
5792 ms
main_ban02_08.jpg
6148 ms
m_eventBan_05.jpg
6223 ms
m_eventBan_03.png
7313 ms
m_eventBan_01.jpg
6738 ms
main_ban04.jpg
6333 ms
main_ban05.jpg
6171 ms
main_ban06_tab01.jpg
6313 ms
main_ban06_tab02_ov.jpg
6191 ms
main_ban07_title.jpg
7087 ms
%EC%8A%A4%ED%81%AC%EB%A6%B0%EC%83%B72016-04-03%EC%98%A4%ED%9B%8411.47.34.png
13457 ms
main_ban08_title.jpg
6201 ms
%E3%85%8B-01.jpg
15382 ms
main_intro_tab_img01.jpg
6478 ms
main_intro_tab_01ov.jpg
6470 ms
main_intro_tab_02.jpg
6700 ms
main_intro_tab_03.jpg
6768 ms
main_intro_tab_04.jpg
6780 ms
main_intro_tab_img02.jpg
8381 ms
main_intro_ban_01_01.png
10174 ms
main_intro_ban_02.jpg
9596 ms
main_intro_ban_03.jpg
12001 ms
footer.jpg
10571 ms
guick_login_btn.jpg
10283 ms
NanumGothic.ttf
20006 ms
guick_join_btn.jpg
8822 ms
guick_01.jpg
8533 ms
guick_02.jpg
8519 ms
guick_03.jpg
8524 ms
guick_04.jpg
8744 ms
guick_ban.jpg
9165 ms
guick_top_btn.jpg
8913 ms
phone_small.png
8930 ms
phone_img_01.png
8779 ms
phone_img_02.jpg
8782 ms
phone_img_03.jpg
8751 ms
phone_img_04.jpg
8445 ms
phone_img_05.jpg
8286 ms
phone_img_btn.jpg
8197 ms
phone_img_06.png
8066 ms
guick_06.jpg
8139 ms
pop_20151027.jpg
9266 ms
pop_20151005_02.jpg
8727 ms
pop_close_btn.jpg
8040 ms
1116_pop.jpg
8227 ms
m_eventBan_04.png
9174 ms
%ED%94%BC%EB%B6%80%EA%B3%BC-%EC%9D%B4%EB%B2%A4%ED%8A%B8_%ED%99%88%ED%8E%98%EC%9D%B4%EC%A7%80_%ED%8C%9D%EC%97%85_%EC%9D%B4%EB%AF%B8%EC%A7%80%EC%88%98%EC%A0%95_160119.jpg
10411 ms
main_intro_bg.jpg
11431 ms
phone_img_07.png
8691 ms
main_menu01_ov.jpg
8818 ms
danielhanps.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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
danielhanps.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
danielhanps.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Danielhanps.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Danielhanps.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
danielhanps.com
Open Graph description is not detected on the main page of Danielhanps. 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: