36.1 sec in total
594 ms
33.3 sec
2.2 sec
Welcome to loveloveme.com homepage info - get ready to check Loveloveme best content for South Korea right away, or after learning these important things about loveloveme.com
자체제작으로 사랑받는 감성데일리룩 럽미
Visit loveloveme.comWe analyzed Loveloveme.com page load time and found that the first response time was 594 ms and then it took 35.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 21 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
loveloveme.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value46.4 s
0/100
25%
Value26.5 s
0/100
10%
Value5,610 ms
0/100
30%
Value0.931
3/100
15%
Value36.3 s
0/100
10%
594 ms
1437 ms
59 ms
46 ms
59 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 16% of them (22 requests) were addressed to the original Loveloveme.com, 43% (59 requests) were made to Cafe24.poxo.com and 5% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Cafe24.poxo.com.
Page size can be reduced by 399.6 kB (4%)
9.1 MB
8.7 MB
In fact, the total size of Loveloveme.com main page is 9.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. 70% of websites need less resources to load. Images take 7.9 MB which makes up the majority of the site volume.
Potential reduce by 256.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. This page needs HTML code to be minified as it can gain 45.8 kB, which is 15% 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 256.6 kB or 85% of the original size.
Potential reduce by 7.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. Loveloveme images are well optimized though.
Potential reduce by 122.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 122.9 kB or 14% of the original size.
Potential reduce by 12.7 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. Loveloveme.com needs all CSS files to be minified and compressed as it can save up to 12.7 kB or 37% of the original size.
Number of requests can be reduced by 37 (36%)
104
67
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Loveloveme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
loveloveme.com
594 ms
loveloveme.com
1437 ms
jet.js
59 ms
jquery.min.js
46 ms
jquery.bxslider.min.js
59 ms
xeicon.min.css
64 ms
css
61 ms
nanumgothic.css
88 ms
across_adn_3.0.1.js
59 ms
js
79 ms
cid.generate.js
559 ms
wcslog.js
107 ms
adn_health_jsonp_chk.ad
222 ms
froala_style_ec.min.css
259 ms
optimizer.php
390 ms
optimizer_user.php
761 ms
keepgrow-service_2e58c6eb-5ba5-40d8-ad0a-97726424f768.js
40 ms
iife.min.js
64 ms
cta.js
1081 ms
ctad.js
882 ms
ld.js
19 ms
kp.js
150 ms
wp_astg_2.0_mall.js
22 ms
kakao.min.js
86 ms
i18n.php
1182 ms
optimizer.php
1371 ms
optimizer_user.php
879 ms
kg_kakaosync_6ca4ad08-3b35-46fd-9806-3b12bdcefa5a.js
125 ms
v2_6d614d9874e68694c4378c6b6965912d_4U1v0Q4NqD_top.jpg
1002 ms
txt_progress.gif
124 ms
img_loading.gif
125 ms
btn_close.gif
126 ms
fd8b9ad9ae515218b398668bc22e394e.gif
6468 ms
custom_21616347891868290.png
1002 ms
28f2a7ac543d893cd8002b7250e325a0.gif
5222 ms
custom_21716409366908433.png
1012 ms
ed951f8710c2a99aa2ffad6f0dfc6745.gif
11775 ms
custom_20916347891862845.png
1187 ms
f63ec815d8d1d39077e6fb32e55c1191.gif
20286 ms
93e465a76c132edcc63a3658db14edb0.gif
7871 ms
57fc7f84d6daada565d1f75eab4108b6.gif
7763 ms
b76b6fc04b92c0a9741b8a53df80921b.gif
10727 ms
b660cfb0e33dd112395c7ad85cad1b1c.gif
11898 ms
4e0d6c834e2e261ccde7d8a4ee6141f2.gif
10987 ms
6bbf795672140023507c6be6631ce0db.gif
13560 ms
46a980e10f2e8b5a5bc904a61fa3112a.gif
16803 ms
2c31698f275ad37cba28bd65cd1c4c6c.gif
15720 ms
e23e9acd213beab8882393ede1b4c46d.gif
17026 ms
9041d7ac5f7f0c4f459e7853639e2d46.gif
17106 ms
bf1d90893346a0dc7e57ccfea9165e8d.gif
17810 ms
4431e0def2cdc50dc48eebc2c8c49216.gif
20290 ms
736896b1dadc96085aa2989fb007f106.gif
20291 ms
627640e364b81093032fbd57cb11ad5b.gif
20290 ms
72a670c6700d0d6b50f3fb8fb516c3df.gif
20291 ms
c54c69fbf469c6e11d2eede46d52caf4.gif
20292 ms
c3822ce6f60341d030cef1f2edd8e198.gif
20292 ms
7c5bd81eeb50c3581e7a8759ca4e3591.gif
20293 ms
9a019cfc4c65d6234c7939315e477664.gif
20293 ms
5ebf994326206ad3b27445670f7f04a8.gif
20293 ms
775c5f7e5ede5fea20cf11f39856a834.gif
20293 ms
d9bc1ec75a6bc4a02c25f7e408b3a95a.gif
20292 ms
f85fd9a5346a1c1fd592c29ccc08a9c0.gif
20293 ms
26f74a7019ad3b389224db01ed88281e.gif
20293 ms
df630f0f1cbae07fd8c96e1f08bd4138.gif
20293 ms
4046d9b6683d438e428c710ea54976c7.gif
20293 ms
8a55e35e9027b59802d92d8f8b57baae.gif
20293 ms
2dbb2b2d66f3cea687bb9e25f6b9a50d.gif
20293 ms
KFOmCnqEu92Fr1Mu4mxM.woff
100 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
101 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
165 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
176 ms
PN_3Rfi-oW3hYwmKDpxS7F_D-djY.woff
178 ms
PN_oRfi-oW3hYwmKDpxS7F_LQv3LyVsg.woff
178 ms
PN_oRfi-oW3hYwmKDpxS7F_LXv7LyVsg.woff
177 ms
xeicon.ttf
98 ms
image_custom_1116850745916835.png
238 ms
0430.jpg
2651 ms
enp_mbris.min.js
1458 ms
init.js
1006 ms
enp_tracker_cafe24_smart.min.js
2022 ms
jfullscript.js
2442 ms
98b0e89777b46c60df5a7f7135d1f65b.js
470 ms
5d8327520d1d7894bff0184e17b9716f.jpg
565 ms
0624292557c63735847e3d45f6095db3.jpg
956 ms
da77ed7e99c08442781e3775d4fca40a.jpg
1123 ms
186cef5b0120f54cc60e6d80f93e338e.jpg
968 ms
86d41ab45bd7786e47f380801c852e99.jpg
339 ms
50c990f5c4eea335cb31f9a163663445.jpg
716 ms
8353f7191e5bee4e48a41d8df6db1c2f.jpg
955 ms
4bf35407c3c184f67b1f4d3e357dd91e.jpg
909 ms
060bd237b2a3273c816e94e90d824685.jpg
1099 ms
935ea93e491043299ff029695bea6186.jpg
1333 ms
c67ad4139c748b422caf6b67f219ee2b.jpg
1145 ms
syncframe
90 ms
event
650 ms
storage
703 ms
wpc.php
706 ms
fe2e28e7ad16229a33bcf9833c78a28d.gif
20284 ms
449575d494266e12f582e8dd8d728335.gif
20282 ms
7fd891bde90efb200aac57c55243b291.gif
20273 ms
slogan_ourspring.png
19682 ms
pixel
32 ms
usersync
659 ms
WIDER
58 ms
storage
188 ms
pixel
39 ms
smat-us
53 ms
wpg.php
177 ms
wpp.php
174 ms
wpg_a.php
175 ms
send
877 ms
send
1003 ms
insite_reset.css
1271 ms
insite_prevent.css
1279 ms
insite_common_v2.css
1286 ms
jquery.js
1464 ms
webutil.js
1291 ms
mbris.js
1292 ms
frame_insite.js
1445 ms
c279c57335a7becb1ca883d1f26e1984.gif
19651 ms
8b1b8ef0ccda7d42d73bbfa089c2f70e.gif
18271 ms
55e15488afea3c5d1eb7fdedb649ec13.gif
17740 ms
bda693b6fc606c0dec872a9ce95d6e6a.gif
19610 ms
ae59c3c4152fc7b50a4e86fe779c2e3e.gif
14799 ms
431aa66d1a1f2919ad2ce8b03d11ac6d.gif
16481 ms
09367099e1af0621c14386a1e06dcee8.gif
17152 ms
c7374e4e3a0c9af41772fba1edd91412.gif
16459 ms
6cb2429f5614e133c64adb21733ad47c.gif
17083 ms
520fc5dedeb25923f62cae548de495f6.gif
14919 ms
inis01.png
10871 ms
inis02.png
10646 ms
inis03.png
10755 ms
inis04.png
10067 ms
katalk.png
7771 ms
7e9479fbffdc4d91e952d7c878a40368.jpg
8344 ms
8c98934df6b1b87daf9a50bf7339bc65.jpg
8229 ms
de7c444c35e7b60e0d3d6c2ccb98ef68.jpg
8859 ms
bb513d586093b6d9c6fa3ac2368e890b.jpg
9044 ms
loveloveme.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
loveloveme.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
loveloveme.com SEO score
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 doesn't use legible font sizes
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loveloveme.com 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 Loveloveme.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.
loveloveme.com
Open Graph data is detected on the main page of Loveloveme. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: