2 sec in total
102 ms
1.6 sec
288 ms
Welcome to doubleheart.co.kr homepage info - get ready to check Double Heart best content right away, or after learning these important things about doubleheart.co.kr
아기가 선택한 1등 젖병&젖꼭지! 더블하트 공식몰
Visit doubleheart.co.krWe analyzed Doubleheart.co.kr page load time and found that the first response time was 102 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
doubleheart.co.kr performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value18.3 s
0/100
25%
Value7.5 s
27/100
10%
Value190 ms
91/100
30%
Value0.969
2/100
15%
Value16.2 s
5/100
10%
102 ms
145 ms
55 ms
108 ms
37 ms
Our browser made a total of 191 requests to load all elements on the main page. We found that 95% of them (181 requests) were addressed to the original Doubleheart.co.kr, 1% (2 requests) were made to Google-analytics.com and 1% (2 requests) were made to Ykbrand.co.kr. The less responsive or slowest element that took the longest time to load (677 ms) relates to the external source Gtp13.acecounter.com.
Page size can be reduced by 392.4 kB (23%)
1.7 MB
1.3 MB
In fact, the total size of Doubleheart.co.kr main page is 1.7 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 93.0 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 15.5 kB, which is 13% 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 93.0 kB or 77% of the original size.
Potential reduce by 65.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. Double Heart images are well optimized though.
Potential reduce by 190.3 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 190.3 kB or 62% of the original size.
Potential reduce by 43.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. Doubleheart.co.kr needs all CSS files to be minified and compressed as it can save up to 43.2 kB or 81% of the original size.
Number of requests can be reduced by 21 (11%)
188
167
The browser has sent 188 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Double Heart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
doubleheart.co.kr
102 ms
www.doubleheart.co.kr
145 ms
dh.min.css
55 ms
jquery-1.7.1.min.js
108 ms
modernizr.custom.2.5.3.js
37 ms
Google_Analytics.js
18 ms
h_slide.css
56 ms
h_slide.js
46 ms
jquery.slides.min.js
54 ms
jquery.easing.1.3.min.js
54 ms
camera.min.js
74 ms
script.min.js
54 ms
s_code.js
84 ms
conversion.js
14 ms
analytics.js
13 ms
mainBg.jpg
81 ms
LoginCheck_JS
134 ms
collect
12 ms
contEdge.png
46 ms
mlogo.png
324 ms
gnbBg.png
32 ms
util_login.gif
33 ms
util_join.gif
30 ms
util_support.gif
60 ms
util_sitemap.gif
62 ms
tm1.gif
62 ms
introBg.png
58 ms
sbar.gif
319 ms
tm1_s1.gif
61 ms
tm1_s2.gif
63 ms
tm1_s2_1.gif
322 ms
tm1_s2_2.gif
322 ms
tm1_s2_3.gif
324 ms
tm1_s2_4.gif
325 ms
tm1_s2_5.gif
320 ms
tm1_s2_6.gif
339 ms
tm1_s3.gif
324 ms
tm1_s3_1.gif
325 ms
tm1_s3_2.gif
327 ms
tm1_s3_3.gif
334 ms
tm1_s3_4.gif
328 ms
tm1_s3_5.gif
329 ms
tm1_s3_6.gif
330 ms
tm1_s3_7.gif
332 ms
tm1_s4.gif
333 ms
tm1_s5.gif
334 ms
tm2.gif
344 ms
eventBg.png
335 ms
tm2_s002.gif
335 ms
tm2_s4.gif
347 ms
tm2_s5.gif
339 ms
tm2_s6.gif
336 ms
tm3.gif
338 ms
clubBg.png
336 ms
tm3_s1.gif
322 ms
tm3_s2.gif
323 ms
tm3_s3.gif
323 ms
tm3_s4.gif
301 ms
tm4.gif
299 ms
mallBg.png
298 ms
tm4_s1.gif
300 ms
tm4_s2.gif
300 ms
tm5.gif
298 ms
storyBg.png
49 ms
tm5_s1.gif
54 ms
tm5_s2.gif
55 ms
tm5_s3.gif
45 ms
tm5_s4.gif
45 ms
tm5_s5.gif
45 ms
slideBg.gif
54 ms
p_01.png
44 ms
p_02.png
44 ms
p_03.png
56 ms
p_04.png
52 ms
p_05.png
42 ms
p_06.png
46 ms
p_01on.png
45 ms
more.png
66 ms
step1.png
58 ms
step1_best2.gif
44 ms
step1_best3.gif
55 ms
step1_best4.gif
63 ms
step1_best5.gif
74 ms
p_01.png
53 ms
p_02.png
55 ms
p_03.png
53 ms
p_04.png
54 ms
p_05.png
58 ms
p_06.png
81 ms
p_02on.png
99 ms
more.png
92 ms
step2.png
102 ms
step2_best1.gif
63 ms
step2_best2.gif
117 ms
step2_best3.gif
71 ms
step2_best4.gif
82 ms
step2_best5.gif
102 ms
p_03on.png
91 ms
step3.png
96 ms
step3_best1.gif
111 ms
step3_best2.gif
142 ms
step3_best3.gif
96 ms
step3_best4.gif
124 ms
step3_best5.gif
101 ms
p_04on.png
103 ms
step4.png
115 ms
step4_best1.gif
105 ms
step4_best2.gif
109 ms
step4_best3.gif
125 ms
step4_best4.gif
124 ms
step4_best5.gif
115 ms
p_05on.png
117 ms
step5.png
215 ms
acecounter_V70.js
128 ms
step5_best1.gif
116 ms
step5_best2.gif
117 ms
gtp13.acecounter.com
677 ms
step5_best3.gif
118 ms
step5_best4.gif
205 ms
step5_best5.gif
197 ms
p_06on.png
197 ms
step6.png
199 ms
step6_best1.gif
201 ms
step6_best2.gif
197 ms
step6_best3.gif
184 ms
step6_best4.gif
192 ms
step6_best5.gif
175 ms
cloude.png
180 ms
bottom.png
170 ms
main_BL.png
165 ms
guide_title.png
161 ms
guide_1.png
158 ms
guide_2.png
188 ms
guide_3.png
189 ms
guide_4.png
164 ms
guide_5.png
190 ms
main_BR.png
147 ms
dot_v.gif
170 ms
tit_newProuct.png
158 ms
635658120774941403.jpg
159 ms
635658117942706938.jpg
185 ms
635658122609068674.jpg
164 ms
tit_event.png
187 ms
6358600149454772690.jpg
164 ms
6358513216832622392.jpg
190 ms
tit_notice.png
159 ms
noti_more.png
178 ms
r.png
161 ms
doll.png
194 ms
rbaby2.png
188 ms
quick_qc.gif
182 ms
quick_mov1.png
195 ms
77 ms
LoginCheck
156 ms
gtp13.acecounter.com
507 ms
quick_mov2.png
95 ms
foot_logo.png
99 ms
s_cc.png
115 ms
txt_ccDesc.png
103 ms
link_faq.png
138 ms
link_qa.png
138 ms
modalClose.png
110 ms
s_privacy.png
127 ms
s_agreement.png
115 ms
s38351308186538
10 ms
s_sitemap.png
151 ms
sitemap_1.png
118 ms
sitemap_2.png
128 ms
sitemap_3.png
129 ms
sitemap_5.png
131 ms
sitemap_6.png
154 ms
sitemap_4.png
135 ms
sitemap_7.png
136 ms
42 ms
s_myActivity.png
145 ms
quickBg1.png
141 ms
modalBg.png
144 ms
innerBack.png
121 ms
sitemapBg.png
136 ms
icon.png
149 ms
note.png
123 ms
faqBox_top.gif
137 ms
faqBox_bottom.gif
131 ms
modalTop.png
129 ms
modalBottom.png
124 ms
modalTop_s.png
133 ms
modalBottom_s.png
116 ms
prev.png
114 ms
next.png
114 ms
camera-loader.gif
132 ms
slide1.jpg
172 ms
doubleheart.co.kr 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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
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.
doubleheart.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
doubleheart.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 doesn't use 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 Doubleheart.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 Doubleheart.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.
doubleheart.co.kr
Open Graph description is not detected on the main page of Double Heart. 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: