9.2 sec in total
1.6 sec
7.1 sec
579 ms
Welcome to lovedl.co.kr homepage info - get ready to check Lovedl best content right away, or after learning these important things about lovedl.co.kr
재회상담은 심리상담이 아니라, 연애상담이다. 재회상담을 받으면 재회성공 확률은? 재회상담을 받으면 재회에 100% 성공하는게 절대 아니다. 마치 100% 성공하는 것처럼 말하는 곳이 있다면 거짓이다. 그 근거 또한 명확한데, 상담이라는 방법이 가진 한계점 때문이다.
Visit lovedl.co.krWe analyzed Lovedl.co.kr page load time and found that the first response time was 1.6 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lovedl.co.kr performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value33.6 s
0/100
25%
Value18.8 s
0/100
10%
Value5,900 ms
0/100
30%
Value0.019
100/100
15%
Value35.0 s
0/100
10%
1550 ms
1435 ms
1613 ms
88 ms
79 ms
Our browser made a total of 198 requests to load all elements on the main page. We found that 27% of them (53 requests) were addressed to the original Lovedl.co.kr, 40% (79 requests) were made to Vendor-cdn.imweb.me and 17% (33 requests) were made to Cdn.imweb.me. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Cdn.imweb.me.
Page size can be reduced by 1.3 MB (50%)
2.6 MB
1.3 MB
In fact, the total size of Lovedl.co.kr main page is 2.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. Only a small number of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.
Potential reduce by 1.0 MB
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 1.0 MB or 88% of the original size.
Potential reduce by 2.3 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, Lovedl needs image optimization as it can save up to 2.3 kB or 61% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 226.2 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 226.2 kB or 20% of the original size.
Potential reduce by 37.6 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. Lovedl.co.kr needs all CSS files to be minified and compressed as it can save up to 37.6 kB or 14% of the original size.
Number of requests can be reduced by 140 (80%)
175
35
The browser has sent 175 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lovedl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 107 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
lovedl.co.kr
1550 ms
gtp6.acecounter.com
1435 ms
AceCounter_AW.js
1613 ms
vendor_blue_10.css
88 ms
vendor_red_10.css
79 ms
im_component.css
87 ms
alarm_menu.css
101 ms
function.css
101 ms
site.css
105 ms
site2.css
119 ms
iefix2.css
116 ms
animate.css
102 ms
chosen.css
117 ms
chosenImage.css
117 ms
style.css
132 ms
ii.css
132 ms
pretendardvariable.css
140 ms
pretendard.css
132 ms
style.css
133 ms
custom.cm
227 ms
tailwind.css
133 ms
emoji.css
138 ms
font-awesome5.min.css
141 ms
style.css
192 ms
spocahansans.css
6 ms
lato.css
6 ms
nanumgothic.css
28 ms
vegur.css
25 ms
jquery.js
10 ms
jquery-ui.design.js
23 ms
lodash.min.js
10 ms
vue.global.prod.js
67 ms
axios.min.js
10 ms
css2
45 ms
css2
47 ms
css2
47 ms
postcode.v2.js
168 ms
player.js
70 ms
js
104 ms
js
165 ms
vue.global.prod.js
25 ms
gtm.js
479 ms
bootstrap.min.js
13 ms
jquery.fileupload.js
16 ms
jquery.lazyload.min.js
16 ms
KR_KRW_currency.js
625 ms
common.js
14 ms
im_component.js
14 ms
site_common.js
12 ms
imagesloaded.pkgd.min.js
14 ms
jquery.smooth-scroll.min.js
15 ms
gambit-smoothscroll-min.js
15 ms
ThreeCanvas.js
18 ms
snow.js
17 ms
preloader.js
18 ms
masonry.pkgd.min.js
17 ms
lightgallery-all.min.js
16 ms
bootstrap.slide-menu.js
18 ms
bootstrap.slide-menu-alarm.js
22 ms
bootstrap-hover-dropdown.min.js
22 ms
jquery-scrolltofixed.js
22 ms
jquery.trackpad-scroll-emulator.js
21 ms
modernizr.custom.js
21 ms
classie.js
30 ms
jquery.exif.js
128 ms
jquery.canvasResize.js
33 ms
autosize.js
128 ms
owl.carousel2.js
128 ms
slick.min.js
128 ms
preview_mode.js
474 ms
site.js
474 ms
site_member.js
475 ms
mobile_menu.js
475 ms
sns_share.js
474 ms
android_image_upload.js
823 ms
alarm_menu.js
881 ms
alarm_badge.js
826 ms
one_page.js
879 ms
site_coupon.js
881 ms
secret_article.js
948 ms
article_reaction.js
964 ms
site_shop.js
1138 ms
board_common.js
1008 ms
site_shop_mypage.js
1028 ms
site_search.js
1033 ms
zipcode_daum.js
1126 ms
site_booking.js
1143 ms
site_section.js
1359 ms
jquery.number.min.js
438 ms
nprogress.js
438 ms
tinycolor-min.js
437 ms
app.js
1377 ms
header_fixed_menu.js
1211 ms
header_more_menu.js
1492 ms
header_center_colgroup.js
1493 ms
mobile_carousel_menu.js
1318 ms
header_mega_dropdown.js
1559 ms
header_overlay.js
1667 ms
site_log.js
1712 ms
advanced_trace.js
1726 ms
site_animation.js
1650 ms
site_event_check.js
1665 ms
site_widget.js
1742 ms
moment.min.js
436 ms
moment-with-locales.js
436 ms
bootstrap-datepicker.js
435 ms
jquery.timepicker.min.js
461 ms
ie-checker-min.js
461 ms
channel_plugin.js
2004 ms
jquery.chosen.js
462 ms
device_uuid.js
1843 ms
wcslog.js
484 ms
oms-shop-bridge.iife.js
461 ms
front-office.js
1842 ms
naver_web_player_ugc_min.js
621 ms
kp.js
434 ms
keepgrow-service_4f4fb558-c992-4975-8c22-32e6b08bedee.js
529 ms
main.min.js
490 ms
fb_pixel.js
1883 ms
froogaloop2.min.js
458 ms
fbevents.js
499 ms
e587b72597310.png
572 ms
ab15d0dddc8f9.png
1184 ms
daba1dac8f569.png
1185 ms
f29448bee1f02.png
2921 ms
e4655d7962d34.png
490 ms
e80eac4fb2173.png
489 ms
783638984461a.png
493 ms
7c9f458a41d45.png
496 ms
486ab25d38553.png
493 ms
b9a220c128332.png
495 ms
040957ee41e43.jpg
1384 ms
5c0de3ef84b2b.png
502 ms
7a57693f710a0.png
503 ms
75fbdb6ed54e4.png
504 ms
5a22345ecde49.png
505 ms
2375c16495823.png
505 ms
aa0c803297c9e.png
1386 ms
6be81c2bd1b7d.png
1393 ms
b86502b6f32ef.png
2955 ms
4affdc4a9b2bd.jpg
2086 ms
0d195451c14a7.png
2928 ms
a88d5af2e1aa4.png
2927 ms
bbf367788c1f3.png
2922 ms
02a8f8d29a5ed.png
2934 ms
5918bd5451a35.png
3235 ms
26f84fb526025.png
3379 ms
42363bc8f153d.png
3842 ms
c9e9a6427b535.png
3703 ms
8b5700fbde9f1.png
3646 ms
f980e2cb7c1b2.png
3863 ms
d4ab2bdf85225.png
3951 ms
8edc94c68d792.png
4299 ms
18918b9a1cf87.png
3654 ms
im-icon.ttf
51 ms
Lato-Regular.woff
943 ms
Lato-Light.woff
982 ms
Lato-Bold.woff
981 ms
SpoqaHanSansRegular.woff
170 ms
SpoqaHanSansLight.woff
165 ms
SpoqaHanSansThin.woff
126 ms
SpoqaHanSansBold.woff
167 ms
font
376 ms
BlackTie-Medium-webfont.woff
168 ms
BlackTie-Light-webfont.woff
171 ms
BlackTie-Bold-webfont.woff
170 ms
BlackTie-Solid-webfont.woff
178 ms
Vegur-R%200.602.woff
172 ms
fontawesome-webfont.woff
179 ms
Material-Design-Iconic-Font.woff
180 ms
Simple-Line-Icons.ttf
181 ms
google_analytics.js
1432 ms
mobon.js
1624 ms
ace_counter_partner.js
1726 ms
kakao_pixel.js
1550 ms
naver_log.js
1592 ms
google_adwords_trace.js
1457 ms
post.js
1545 ms
post_comment.js
1331 ms
library_image.js
1558 ms
gallery.js
1399 ms
image.js
1432 ms
newest_post.js
1601 ms
default_profile.png
2035 ms
%EB%B2%84%ED%8A%BC%EC%9D%B4%EB%AF%B8%EC%A7%80%EC%A3%BC%EC%86%8C
2026 ms
gtp6.acecounter.com
949 ms
sendid
864 ms
gtp6.acecounter.com
1329 ms
gtp6.acecounter.com
1228 ms
gtp6.acecounter.com
865 ms
805c4dd67f
828 ms
b220613e152644u854
835 ms
enp_tracker_self_hosted.min.js
1884 ms
enp_tracker_imweb.min.js
1911 ms
iframe_api
64 ms
www-widgetapi.js
5 ms
805c4dd67f
187 ms
bstrk.1.js
1132 ms
lovedl.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
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.
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
lovedl.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lovedl.co.kr 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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lovedl.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 Lovedl.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.
lovedl.co.kr
Open Graph data is detected on the main page of Lovedl. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: