9.8 sec in total
742 ms
7.9 sec
1.1 sec
Welcome to pinklavender.co.kr homepage info - get ready to check Pinklavender best content right away, or after learning these important things about pinklavender.co.kr
러블리한 악세사리쇼핑몰 핑크라벤더 입니다
Visit pinklavender.co.krWe analyzed Pinklavender.co.kr page load time and found that the first response time was 742 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pinklavender.co.kr performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value24.5 s
0/100
25%
Value10.3 s
8/100
10%
Value360 ms
72/100
30%
Value0.687
7/100
15%
Value16.5 s
5/100
10%
742 ms
1657 ms
223 ms
375 ms
21 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 88% of them (139 requests) were addressed to the original Pinklavender.co.kr, 4% (6 requests) were made to Fonts.googleapis.com and 3% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Pinklavender.co.kr.
Page size can be reduced by 225.2 kB (7%)
3.0 MB
2.8 MB
In fact, the total size of Pinklavender.co.kr main page is 3.0 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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 182.0 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 27.2 kB, which is 13% 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 182.0 kB or 86% of the original size.
Potential reduce by 42.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. Pinklavender images are well optimized though.
Potential reduce by 1.1 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.
Number of requests can be reduced by 41 (27%)
151
110
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pinklavender. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
pinklavender.co.kr
742 ms
pinklavender.co.kr
1657 ms
jet.js
223 ms
common.js
375 ms
css
21 ms
css
37 ms
css
39 ms
css
39 ms
css
38 ms
cid.generate.js
809 ms
wcslog.js
33 ms
optimizer.php
648 ms
optimizer_user.php
460 ms
i18n.php
1570 ms
optimizer.php
1426 ms
optimizer_user.php
878 ms
nanumgothic.css
18 ms
d5602d4e-80eb-49a6-8ea2-44e02a076b50.jpeg
2443 ms
btn_list_cart.gif
31 ms
blank
22 ms
txt_prog_001.gif
575 ms
btn_list_option.gif
119 ms
btn_search.gif
23 ms
logo.jpg
188 ms
m_item.jpg
193 ms
74a99ccc70c1f9eae4f6632537735e1f.jpg
210 ms
675df1b40432f08761351771e6ad8635.jpg
377 ms
d7238d80ce2c7b2c25338350b835005c.jpg
385 ms
2fe20bef4a590bc1cba1e923e9c5a6ba.jpg
419 ms
b49414bc462dc26b8315fb32c43f66aa.jpg
425 ms
b65209d5f402fcf0eaf8c0db2cc8be90.jpg
565 ms
shop1_52_menu_851520.jpg
576 ms
shop1_32_menu_778394.jpg
627 ms
shop1_47_menu_645351.jpg
620 ms
shop1_61_menu_591026.jpg
753 ms
m_silver.jpg
769 ms
m_1.jpg
817 ms
m_3.jpg
839 ms
m_4.jpg
992 ms
m_5.jpg
992 ms
m_11.jpg
993 ms
m_12.jpg
1012 ms
m_13.jpg
1047 ms
m_14.jpg
1117 ms
m_commu.jpg
1130 ms
b_1.jpg
1154 ms
b_2.jpg
1163 ms
b_3.jpg
1208 ms
b_4.jpg
1256 ms
m_15.jpg
1305 ms
m_16.jpg
1317 ms
m_17.jpg
1345 ms
m_18.jpg
1352 ms
t_login.jpg
1404 ms
img_loading_bar.gif
991 ms
t_1.jpg
1464 ms
t_2.jpg
1475 ms
font
85 ms
font
90 ms
font
119 ms
font
147 ms
NanumGothicBold.woff
2448 ms
t_3.jpg
1347 ms
t_4.jpg
1307 ms
t_5.jpg
1367 ms
t_6.jpg
1300 ms
m_banner_top.jpg
1300 ms
cs.jpg
1315 ms
m_banner_1.jpg
1308 ms
m_banner_2.jpg
1234 ms
m_banner_3.jpg
1308 ms
m_banner_4.jpg
1252 ms
but_main_prev.png
1295 ms
but_main_next.png
1171 ms
e6e546d31981e49fcfee6be269597300.jpg
1421 ms
f9a5163f9a71b7fe6db8b2965eb29882.jpg
1277 ms
da9f43254d287a9aa9031fc8de1ba5c5.jpg
1277 ms
88898da7b14cd7150775fab7918fe902.jpg
1272 ms
d8c645830e0e5145e70ec63584e7d8b3.jpg
1127 ms
f61c2778f5cb0d33a552ce97c2048dfe.jpg
1259 ms
232297cb1e57f89b098d72c3b38fbcae.jpg
1312 ms
dde1df24eb3157ac20f1b9650bccbf9a.jpg
1306 ms
m_banner_5.jpg
1298 ms
015520d1539dbdacc440e829e2dca86f.jpg
1339 ms
5ba0bc2725ff7adeac664c581b1a4511.jpg
1324 ms
55268deb3e0e1efc12c5f59786e8cc91.jpg
1359 ms
10d26d168e5849f683be096a013a12fc.jpg
1360 ms
2e150113ac063430ba102fa236387cd7.jpg
1341 ms
c7878e8c0f98134c1e3f6cc3a133f9df.jpg
1374 ms
6f68e1a8a28735669eb802d80dfbd7b2.jpg
1374 ms
100d9b7c017ec3ff3639d2890b61fc1f.jpg
1392 ms
c9aa447ce222681140f7e433555fee99.jpg
1380 ms
8831d3cc083e8d27e9e2f1228c44f8a8.jpg
1377 ms
b1b75bdd04368156582cf4ad6e545941.jpg
1428 ms
a894f0b79b9d6e8f1d96b34ee463b32a.jpg
1414 ms
e86fe987e9251429bd11f5bff631535a.jpg
1358 ms
1d4e2d88a9144d6fb645c8187aceac91.jpg
1376 ms
bcc0086cf2d32d715efcff868a128215.jpg
1353 ms
fa076c4796892d760ed43bad50b93a0b.jpg
1392 ms
922f8a5721d551ecdb6c5b0bffaa8588.jpg
1375 ms
custom_34.gif
1334 ms
03712e95032af8650511f318c04e85a3.jpg
1328 ms
9a82af46b48653b810e59b1a8ec0de6f.jpg
1327 ms
ff9db70e9d420bc71c9072cd7dbfc483.jpg
1352 ms
3808746e0c61fd59aeae50d1b9200e0e.jpg
1356 ms
3432bffee0d9b5ae098467a329ece8aa.jpg
1307 ms
a8c2a665477647f2c93b4a2b0281e4c6.jpg
1312 ms
45f1d2ffd531ade0afaf6b598de5c1b2.jpg
1280 ms
lavenderpink_344.jpg
1326 ms
lavenderpink_2517.jpg
1217 ms
custom_102.gif
1271 ms
7344d9971fb27664b4b1c451c6c02fdd.jpg
1264 ms
553a3e4abccb78abbd827c7b8b9471b4.jpg
1269 ms
1e11ae42fe5992d838ec2099f301c8dc.jpg
1199 ms
67335d01bcc0e48f35cd7b3d133d31e9.jpg
1188 ms
c81a4648d3a3ba3227db24d158495d47.jpg
1170 ms
81252b71d58f7881075257b4f00ce102.jpg
1270 ms
2ff9e30189a82d9597a0bc07440da1d9.jpg
1260 ms
24b31fc9f219ffcb61b01e2544f4ca9e.jpg
1187 ms
d9e0e154aa20e63f08f5a74fa34b9b1b.jpg
1135 ms
aaf4446bfb1e2627c401cce84b965426.jpg
1140 ms
789a882c75e3cf790cfde45e0c8df93b.jpg
1159 ms
0308971b4a88afc7aaffeb559a252652.jpg
1256 ms
ad123298d48e2b735f9b4bc663132650.jpg
1201 ms
0d75f4ba55b0b7e360326d91bea52b51.jpg
1133 ms
custom_69.gif
1127 ms
e1eaec61fa750a7f457b2d0461e1c91e.jpg
1122 ms
d2b3d1786b166d6a7974bb8c3e0c369f.jpg
1159 ms
5cae1ef0a63f7ae24ca288168c6a2e2d.jpg
1229 ms
6c164cb5e0d6e79997801cd90c779742.jpg
1174 ms
75e43b618b397b6ccd08f147b674e6b7.jpg
1145 ms
lavenderpink_3245.jpg
1378 ms
custom_101.gif
1140 ms
1710035258449afdf0306d6cc3901a0a.jpg
1159 ms
lavenderpink_3050.jpg
1209 ms
9dc0a12e6ed1ca6c74fc592514e60ff7.jpg
1166 ms
113dace829855e24557953f83cce5428.webp
1348 ms
2021cf58de9876980c18e720f69d302f.jpg
1187 ms
1e946eed07ab2f0044561f083c5e8f6e.jpg
1184 ms
lavenderpink_971.jpg
1247 ms
custom_73.gif
1177 ms
d78cb6eed0890fba06ad95d0c2a0a675.jpg
1209 ms
custom_68.gif
1213 ms
2e96e34469c9407e3c7be11f5235bcb3.jpg
1236 ms
lavenderpink_2650.jpg
1269 ms
custom_94.gif
1242 ms
d63a08f5d19fcd241c9c7fb5c094fafb.jpg
1190 ms
c38ce7f72639baca02966a5037142348.jpg
1204 ms
lavenderpink_2355.jpg
1234 ms
lavenderpink_2597.jpg
1240 ms
lavenderpink_2753.jpg
1268 ms
custom_99.gif
1238 ms
cb1c48293fe8bfd48dc435f2c0d98360.jpg
1179 ms
link_kcp.jpg
1195 ms
btn_todayprev.jpg
1254 ms
btn_todaynext.jpg
1246 ms
r_top.jpg
1266 ms
weekly_arrow.png
1232 ms
pinklavender.co.kr 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.
pinklavender.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
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
pinklavender.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
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 Pinklavender.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 Pinklavender.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.
pinklavender.co.kr
Open Graph description is not detected on the main page of Pinklavender. 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: