11.8 sec in total
421 ms
8.4 sec
3.1 sec
Visit lglifecare.com now to see the best up-to-date Lglifecare content for South Korea and also check out these interesting facts you probably never knew about lglifecare.com
Digital Benefit으로 완성되는 국내 최고 IT기업의 1등 임직원 복지 서비스
Visit lglifecare.comWe analyzed Lglifecare.com page load time and found that the first response time was 421 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lglifecare.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value61.3 s
0/100
25%
Value20.0 s
0/100
10%
Value920 ms
31/100
30%
Value0.005
100/100
15%
Value56.3 s
0/100
10%
421 ms
801 ms
70 ms
27 ms
559 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 94% of them (136 requests) were addressed to the original Lglifecare.com, 2% (3 requests) were made to Fonts.googleapis.com and 2% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Lglifecare.com.
Page size can be reduced by 1.6 MB (29%)
5.7 MB
4.1 MB
In fact, the total size of Lglifecare.com main page is 5.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. Only a small number of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.
Potential reduce by 669.2 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. 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 669.2 kB or 87% of the original size.
Potential reduce by 975.4 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, Lglifecare needs image optimization as it can save up to 975.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Number of requests can be reduced by 39 (30%)
128
89
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lglifecare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lglifecare.com
421 ms
gate
801 ms
css
70 ms
materialdesignicons.min.css
27 ms
swiper.min.js
559 ms
jquery-3.5.1.min.js
737 ms
main.js
729 ms
d6fd31c.js
381 ms
83a8ad9.js
471 ms
12974a6.js
1037 ms
326b8fa.js
1723 ms
245d0b7.js
1170 ms
css2
63 ms
css2
78 ms
bahnschrift
101 ms
img_profile.png
315 ms
partner01.png
317 ms
partner02.png
316 ms
partner03.png
421 ms
partner04.png
419 ms
partner05.png
483 ms
partner06.png
658 ms
partner07.png
610 ms
partner08.png
610 ms
partner09.png
676 ms
partner10.png
796 ms
partner11.png
796 ms
partner12.png
826 ms
partner13.png
861 ms
partner14.png
887 ms
partner15.png
983 ms
partner16.png
985 ms
partner17.png
1015 ms
partner18.png
1043 ms
partner19.png
1071 ms
partner20.png
1167 ms
partner21.png
1170 ms
partner22.png
1199 ms
partner23.png
1230 ms
partner24.png
1252 ms
btn_appstore.png
1357 ms
btn_googleplay.png
1352 ms
logo_lgcns.png
1383 ms
logo_lifecare.png
1308 ms
ico_blank2.png
1330 ms
ico_search.png
1331 ms
bg_sec1.png
2778 ms
btn_cancel.png
1433 ms
ico_search2.png
1265 ms
diagram_obj1.png
1292 ms
Pretendard-Medium.woff
1887 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgyeLQ.ttf
73 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoyeLQ.ttf
170 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01eLQ.ttf
269 ms
Pretendard-Regular.woff
2125 ms
Pretendard-Light.woff
2221 ms
Pretendard-ExtraLight.woff
2577 ms
Pretendard-Thin.woff
4644 ms
Pretendard-SemiBold.woff
1807 ms
Pretendard-Bold.woff
2045 ms
Pretendard-ExtraBold.woff
2405 ms
Pretendard-Black.woff
2217 ms
TheJamsil-Medium.woff
2189 ms
TheJamsil-Regular.woff
2268 ms
diagram_obj3.png
2266 ms
diagram_obj2.png
2239 ms
obj_sec3_li1_obj1.png
2370 ms
obj_sec3_li1_obj2.png
2344 ms
obj_sec3_li1_obj3.png
2249 ms
obj_sec3_li1_obj4.png
2248 ms
obj_sec3_li1_obj5.png
2221 ms
obj_sec3_li1_obj6.png
2246 ms
obj_sec3_li1_obj7.png
2324 ms
obj_sec3_li1_obj8.png
2231 ms
obj_sec3_li1_obj9.png
2229 ms
obj_sec3_li2_obj2.png
2213 ms
obj_sec3_li2_obj1.png
2240 ms
obj_sec3_li2_obj4.png
2330 ms
obj_sec3_li3_obj1.png
2279 ms
obj_sec3_li3_obj2.png
2229 ms
obj_sec3_li3_obj3.png
2245 ms
obj_sec3_li3_obj4.png
2272 ms
obj_sec3_li3_obj5.png
2354 ms
obj_sec4_li1_logo1.png
2336 ms
obj_sec4_li1_logo2.png
2328 ms
obj_sec4_li1_logo3.png
2258 ms
obj_sec4_li1_logo4.png
2265 ms
obj_sec4_li1_logo5.png
2348 ms
obj_sec4_li1_logo6.png
1677 ms
obj_sec4_li2_logo1.png
1486 ms
obj_sec4_li2_logo2.png
1394 ms
obj_sec4_li2_logo3.png
1325 ms
obj_sec4_li2_logo4.png
1360 ms
obj_sec4_li2_logo5.png
1254 ms
obj_sec4_li2_logo6.png
1243 ms
obj_sec4_li3_logo1.png
1213 ms
obj_sec4_li3_logo2.png
1149 ms
obj_sec4_li3_logo3.png
1257 ms
obj_sec4_li3_logo4.png
1268 ms
obj_sec4_li3_logo5.png
1266 ms
obj_sec4_li3_logo6.png
1215 ms
obj_sec5_li1_1.png
1165 ms
obj_sec5_li1_2.png
1272 ms
obj_sec5_li1_3.png
1287 ms
obj_sec5_li2_1.png
1287 ms
obj_sec5_li2_2.png
1309 ms
obj_sec5_li2_3.png
1292 ms
obj_sec5_li3_1.png
1290 ms
obj_sec5_li3_2.png
1340 ms
obj_sec5_li3_3.png
1306 ms
obj_sec5_arrow.png
1327 ms
ico_star02.png
1305 ms
ico_star03.png
1292 ms
obj_sec6_li1_dd1.png
1309 ms
obj_sec6_li1_dd2.png
1337 ms
obj_sec6_li1_dd3.png
1321 ms
obj_sec6_li1_dd4.png
1314 ms
obj_sec6_li1_dd5.png
1293 ms
obj_sec6_li2_dd1.png
1307 ms
obj_sec6_li2_dd2.png
1336 ms
obj_sec6_li2_dd3.png
1309 ms
obj_sec6_li2_dd4.png
1311 ms
obj_sec6_li3_dd1.png
1319 ms
obj_sec6_li3_dd2.png
1319 ms
obj_sec6_li3_dd3.png
1379 ms
obj_sec6_li3_dd4.png
1350 ms
obj_sec6_li3_dd5.png
1315 ms
obj_review01_01.png
1275 ms
obj_review01_02.png
1286 ms
obj_review01_03.png
1308 ms
obj_review01_04.png
1318 ms
ico_star.png
1266 ms
obj_review03_01.png
1204 ms
obj_review03_02.png
1268 ms
obj_review04_01.png
1288 ms
obj_review04_02.png
1288 ms
obj_review04_03.png
1267 ms
obj_tooltip.png
1168 ms
obj_emogi02.png
1186 ms
obj_tooltip02.png
1266 ms
obj_emogi01.png
1258 ms
ico_expr.png
1247 ms
bg_tooltip.png
1164 ms
btn_top03.png
1149 ms
lglifecare.com 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
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
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.
lglifecare.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
lglifecare.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
Tap targets are not sized appropriately
KO
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lglifecare.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed English language. Our system also found out that Lglifecare.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.
lglifecare.com
Open Graph description is not detected on the main page of Lglifecare. 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: