6.9 sec in total
579 ms
6 sec
406 ms
Welcome to lindsayshop.com homepage info - get ready to check LINDSAY Shop best content for United States right away, or after learning these important things about lindsayshop.com
모델링팩, 고무팩, 석고팩 : 마스크팩 필오프팩 1위, 자연주의 홈에스테틱 린제이 (LINDSAY)
Visit lindsayshop.comWe analyzed Lindsayshop.com page load time and found that the first response time was 579 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
lindsayshop.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value22.7 s
0/100
25%
Value17.6 s
0/100
10%
Value1,820 ms
9/100
30%
Value1.565
0/100
15%
Value23.3 s
1/100
10%
579 ms
1279 ms
17 ms
376 ms
78 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 43% of them (49 requests) were addressed to the original Lindsayshop.com, 22% (25 requests) were made to Cafe24img.poxo.com and 6% (7 requests) were made to File.cafe24cos.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Cafe24img.poxo.com.
Page size can be reduced by 184.4 kB (7%)
2.8 MB
2.6 MB
In fact, the total size of Lindsayshop.com main page is 2.8 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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 128.8 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 29.0 kB, which is 18% 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 128.8 kB or 80% of the original size.
Potential reduce by 14.7 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. LINDSAY Shop images are well optimized though.
Potential reduce by 40.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 224 B
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. Lindsayshop.com needs all CSS files to be minified and compressed as it can save up to 224 B or 16% of the original size.
Number of requests can be reduced by 36 (35%)
102
66
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LINDSAY Shop. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lindsayshop.com
579 ms
lindsayshop.com
1279 ms
jet.js
17 ms
common.js
376 ms
kp.js
78 ms
cid.generate.js
560 ms
wcslog.js
98 ms
optimizer.php
394 ms
optimizer_user.php
614 ms
jquery-1.11.1.min.js
23 ms
nanumgothic.css
25 ms
css
37 ms
slick.css
557 ms
slick-theme.css
557 ms
uif_modernizr.js
589 ms
jquery-1.11.3.min.js
588 ms
slick.min.js
602 ms
uif_classie.js
768 ms
uif_TooltipMenu.js
768 ms
ld.js
21 ms
wp_astg_2.0_mall.js
40 ms
kakao.min.js
165 ms
i18n.php
1353 ms
optimizer.php
1762 ms
optimizer_user.php
813 ms
conversion.js
82 ms
mbris.js
1131 ms
d4636203-23ed-4ce9-fd80-c2c94f6c05b5.jpeg
1453 ms
924397245d53ba8f0f5b961da3976d83.jpg
1431 ms
4d1a51dc-e9d7-4166-abe6-71ca17b70f45.jpeg
1454 ms
10649cbd-73ee-41c4-d3a1-04e036783876.jpeg
1467 ms
82836453-81bf-4eef-82d7-6a9c7a782676.jpeg
2070 ms
d3b2ae52-feb3-4d91-b6f2-b6d32f2499f9.jpeg
2095 ms
df993f70-dd6a-42d6-b68b-b68076eada40.jpeg
2140 ms
86f7c952-2f36-4472-f9c3-0d51a9f6fb36.jpeg
2004 ms
86f5c58872ab4e715b4b71b71ca3a50b_6_top.jpg
447 ms
top_smenu04.gif
572 ms
top_smenu03.gif
571 ms
top_smenu02.gif
629 ms
top_join.gif
635 ms
top_login.gif
757 ms
common_a_32_image_url_2.gif
757 ms
top_menu_01.gif
829 ms
top_menu_02.gif
830 ms
top_menu_04.gif
942 ms
top_menu_03.gif
943 ms
top_menu_05.gif
1028 ms
top_menu_001.gif
1026 ms
top_menu_002.gif
1126 ms
top_menu_003.gif
1128 ms
top_menu_005.gif
1162 ms
top_menu_006.gif
1216 ms
top_menu_007.gif
1230 ms
top_menu_008.gif
1315 ms
main_title_section01.jpg
1499 ms
main_title_section02.jpg
1350 ms
3f09fdd0fcd764602c81c88ba85d5376.jpg
225 ms
a7e9ce86903e3601c55680335815b21e.jpg
281 ms
176f3cffa3fcbc4a89cb970203a153a5.jpg
226 ms
9161e8424ec35d7fc1a97d790f66b420.jpg
1444 ms
e907f6b1bca1f7bf73899d8ef970b2b1.jpg
228 ms
546b4e353f6d7eb53dc21f09ebc771f6.jpg
280 ms
375ef1d7a71e7d190039387f65cb1f79.jpg
281 ms
3b2c26a06d49d9eb61538adfc82403df.jpg
1462 ms
7ecb369e879645977e9fe7ed7584bfa6.jpg
1452 ms
0678c8ebe6f0a950761707f5ec6e0ddd.jpg
1502 ms
2e7c1dbc90d7f2e5c4f228b3ffb0669a.jpg
281 ms
7f62cf2d3fac6becd12375c2beeeda91.jpg
1466 ms
f092711fbacec678a21270ffa431d90b.jpg
2681 ms
b3faabacc9ec9a10201ebc0e9aff6abd.jpg
2718 ms
c0df1cb2a40f4b6b239b48085b6316b6.jpg
1458 ms
31fe8ebb9e8d8a54ef3928e29aac6f75.jpg
1471 ms
80e35b5068f6649ad4c60fa6bb9ae2b5.jpg
1468 ms
b2bebe5a5d85d4fc139ff336b312d3c0.jpg
1479 ms
61b03af26828c0eda635b6d465b2663b.jpg
2690 ms
9210bebbf5b4d3f6d651be9483c82af2.jpg
2475 ms
6fac2dc19b82a263e099b08288eca3de.jpg
2699 ms
8a5359c3653759023cf4ea1652347b78.jpg
2682 ms
e818f89b3af01a3fcb8a6949108056ea.jpg
3708 ms
e5cac7174c2abf245ccee75acefc5dd7.jpg
2685 ms
blank
24 ms
txt_progress.gif
24 ms
img_loading.gif
25 ms
body_bg.jpg
1154 ms
mdchoice_menu01.gif
1170 ms
mdchoice_menu02.gif
1239 ms
mdchoice_menu03.gif
1279 ms
mdchoice_menu04.gif
1310 ms
mdchoice_menu05.gif
1344 ms
mainContentSB_Map01.jpg
1970 ms
footer_body.jpg
1981 ms
footer_banner.gif
1797 ms
PN_3Rfi-oW3hYwmKDpxS7F_D-djb.ttf
8 ms
PN_oRfi-oW3hYwmKDpxS7F_LQv3LyVsj.ttf
98 ms
PN_oRfi-oW3hYwmKDpxS7F_LXv7LyVsj.ttf
102 ms
lW-8wjkKLXjg5y2o2uUYV-t3.ttf
110 ms
fontawesome-webfont.woff
1445 ms
syncframe
16 ms
mdchoice_menu01_roll.gif
357 ms
banner_bg.gif
396 ms
35 ms
enp_tracker_cafe24_smart.min.js
1100 ms
storage
703 ms
wpc.php
707 ms
27 ms
29 ms
pixel
29 ms
usersync
678 ms
WIDER
57 ms
storage
176 ms
wpg.php
180 ms
wpp.php
175 ms
wpg_a.php
177 ms
lindsayshop.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
lindsayshop.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
lindsayshop.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
![]()
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lindsayshop.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 Lindsayshop.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.
lindsayshop.com
Open Graph data is detected on the main page of LINDSAY Shop. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: