8.2 sec in total
214 ms
7.3 sec
718 ms
Visit lookpine.net now to see the best up-to-date LOOKPINE content and also check out these interesting facts you probably never knew about lookpine.net
Welcome to korea men online shopping!
Visit lookpine.netWe analyzed Lookpine.net page load time and found that the first response time was 214 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lookpine.net performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value36.7 s
0/100
25%
Value10.5 s
7/100
10%
Value440 ms
63/100
30%
Value1.839
0/100
15%
Value17.9 s
3/100
10%
214 ms
606 ms
211 ms
376 ms
579 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 24% of them (28 requests) were addressed to the original Lookpine.net, 56% (64 requests) were made to Cafe24img.poxo.com and 5% (6 requests) were made to Img.echosting.cafe24.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Cafe24img.poxo.com.
Page size can be reduced by 627.2 kB (9%)
6.8 MB
6.2 MB
In fact, the total size of Lookpine.net main page is 6.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.1 MB which makes up the majority of the site volume.
Potential reduce by 224.4 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 224.4 kB or 87% of the original size.
Potential reduce by 401.1 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. LOOKPINE images are well optimized though.
Potential reduce by 1.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 62 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. Lookpine.net has all CSS files already compressed.
Number of requests can be reduced by 14 (13%)
109
95
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LOOKPINE. 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 from 4 to 1 for CSS and as a result speed up the page load time.
lookpine.net
214 ms
lookpine.net
606 ms
jet.js
211 ms
common.js
376 ms
jquery-1.11.0.min.js
579 ms
jquery-migrate-1.2.1.min.js
381 ms
slick.min.js
398 ms
swiper.min.js
400 ms
cid.generate.js
369 ms
optimizer.php
382 ms
optimizer_user.php
391 ms
jquery-1.12.4.js
20 ms
jquery-ui.js
25 ms
i18n.php
1312 ms
optimizer.php
1386 ms
optimizer_user.php
498 ms
logo.png
967 ms
ico_multishop1.png
242 ms
en_US_18x12.png
1136 ms
77492947e32e1f4a50e26f6820b0032a.webp
2276 ms
header_ico_search.png
958 ms
%EC%9D%B8%EC%8A%A4%ED%83%80%EA%B7%B8%EB%9E%A8.png
1019 ms
txt_progress.gif
236 ms
img_loading.gif
238 ms
btn_go.gif
242 ms
btn_close.gif
241 ms
ko_KR_32x24.png
1137 ms
en_US_32x24.png
1136 ms
zh_TW_32x24.png
1218 ms
ja_JP_32x24.png
1221 ms
zh_CN_32x24.png
1219 ms
78b5a771840a7b985db584a26ff1de3c.webp
2023 ms
0bc1679dfa70f49a171f5e78d8e45d56.webp
244 ms
9e15bf141ca843eaf7180e2fee242d1e.webp
245 ms
978436f0969213ca2055fd2ff4b781b3.webp
273 ms
a85ac998bacda980a3bb5e02e6ba3229.webp
246 ms
cfa3831851722c44a4eeecd436b761e0.webp
259 ms
4314f1d236b6e84375c579612d13afc3.webp
265 ms
32ca52353d3139881bb0eb66fab1da31.gif
260 ms
5a13a8400e87467bea51bae4dbe61ef7.webp
275 ms
69ec48e7695b5337f9e660ecf3a85d08.webp
276 ms
c577e26ec00f952224659946c82ad4c8.webp
280 ms
7bdc685e7c0ca338652e6d1663373fd9.gif
299 ms
0e310e81f703a17aa7e29c2393eb51b6.jpg
290 ms
295bac91f1739a71d37e551414647cdf.webp
2407 ms
abcbf40f1b5a319791c1e67e1124fce7.gif
2266 ms
76b4a2b7ff18a48560047e84d7fb5b1b.webp
2250 ms
0cbfbeec36304a202ca7d4af1f46a918.webp
345 ms
9cfbd0381c59e7bb8c84adf7f5df9356.webp
355 ms
a48d1d99f4febef9fffb1d3324f05d3c.webp
2121 ms
c888932a6d1e9c288b34daa16e21ad0e.webp
2043 ms
1431f639ad04255e15949ddee754ddff.webp
2060 ms
9010d8418cc1ffe790d3f2c917643469.webp
2069 ms
721763f9d539011ec32400432979b744.webp
2086 ms
ec9749a127f73320fea66c8aaaf87ef9.webp
2097 ms
b48b0245c0a2f295f622ed683707554b.webp
2113 ms
bfb64927d192ac42b5fc13ad7eb01572.webp
4091 ms
e94bb89086c747f20dff44389ae92b2a.webp
2135 ms
49d692992120691c9709ba8d1ffcaee9.webp
2148 ms
7456acc215d83b009c3c0b63666447ea.webp
2164 ms
78c88a0b97279028a62457d457132a5e.webp
2174 ms
137181cd635f0cf3e6d259e53caac1b7.webp
2191 ms
4da7b8136b70032d5eee25e5e270bf71.webp
2206 ms
90a2ee3ebd2e986186ac4a184247fe71.webp
2218 ms
0c3eee11ec01d7c9dd3707194f59ed23.webp
2227 ms
99ed741e9c5f24ff9c9310e3fc66809d.webp
2238 ms
lookmade_bg.jpg
1527 ms
NanumBarunGothic-Regular.woff
51 ms
NanumBarunGothic-Bold.woff
103 ms
766a48561e02ee8ef2251128f375abe7.js
198 ms
2389b006318ec128360a2cac0f1f9b9b.webp
3732 ms
a051d39810f46fa9d5ab26363512ff16.jpg
3797 ms
7b0f82067bc279ef6194d9e1444aa3f2.webp
2033 ms
20f59afc055b1805d3568b1fe276bc52.webp
2029 ms
ffaa65806fd80b9fd2a2b6cd1d6a9f0a.webp
2036 ms
ab6d130785ab3cd1724f0ff005e64a8e.webp
2035 ms
bb369516e176f86df2a58074703f8e32.webp
2034 ms
e114ad07b3f5595a3e674c1726c4ee6e.webp
2050 ms
8fc3dfdd5bd90a5bf5b31a4a8e423815.webp
4044 ms
0e5eeabf832d1d49e5459f94d4f47611.webp
2054 ms
c55b44d20215a2b4ac57aacc9d7b4f7c.webp
2056 ms
3441f90f894499d43cfea8af8441285a.webp
2057 ms
ed5d6f7b522232b2d1898d9d769d622a.jpg
1322 ms
92a718cf6d73bd83eb099393986976b3.jpg
1347 ms
3f67b64d38be0ac956acc55c41ad4396.jpg
1289 ms
4132dbd092d146add42a0b166fb92252.jpg
1472 ms
c2415767760488ebbd730b4f0df808d1.jpg
2320 ms
bc46a4af863ea7b003606e3555e0ee39.jpg
1645 ms
524f945f1338de08cda4e82ecf6532c7.jpg
2027 ms
9b03cdbc575aeb0699dfc6ccbde0373b.jpg
1515 ms
6e7337d1a044930a45a08a1ef5977744.jpg
1542 ms
2f7eeb72ec9c2f08c13344f274c545fe.jpg
2027 ms
slider_nav_prev.png
1519 ms
slider_nav_next.png
1523 ms
94cfefd93f2d7458de757cb551e70482.jpg
2019 ms
4d402382c50a4903d5b0bbc00a781cb3.webp
2036 ms
a5aaab3030.css
47 ms
font-awesome-css.min.css
10 ms
SubCategory
998 ms
bg_worldship.gif
13 ms
fontawesome-webfont.woff
14 ms
c372090ca235cca782e7202f12cb4927.webp
384 ms
829914db96c9eafa2ce1ad3faa39e3ff.webp
376 ms
23370f47ad7dbe45ae434328880cf699.webp
364 ms
0cab9b3a084a28e2c34102c53098c4b8.jpg
2375 ms
385318277a01055f30c4580d61b2757f.webp
2137 ms
a080bd5ef53142c7e7cef6130550a70d.jpg
3646 ms
8c2d92f79ee7bdcf871da9abed2d2066.jpg
3937 ms
7dd3e48639e3bf267c5961700c12fc6c.webp
3802 ms
e04a40d796b654b3761e7fd6f96d58d2.webp
2096 ms
faacc13784ae6f69d718799f515fa569.webp
2102 ms
13e59864c801746cb2b12d45f4943520.webp
2096 ms
86eaa5a0b6c34483edda82ff21cb0b00.webp
2103 ms
3907b60f8051e49d310488b39359c0bd.webp
2101 ms
0bc1679dfa70f49a171f5e78d8e45d56.webp
2089 ms
lookpine.net 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 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.
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.
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.
lookpine.net 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
Issues were logged in the Issues panel in Chrome Devtools
lookpine.net 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
![]()
EN
![]()
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lookpine.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Korean language. Our system also found out that Lookpine.net 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.
lookpine.net
Open Graph description is not detected on the main page of LOOKPINE. 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: