9.5 sec in total
1 sec
6.7 sec
1.8 sec
Welcome to limelikeme.com homepage info - get ready to check Limelikeme best content for South Korea right away, or after learning these important things about limelikeme.com
라임라이크미 온라인에서 만나는 스타일리쉬한 브랜드 퀄리티 제품들!
Visit limelikeme.comWe analyzed Limelikeme.com page load time and found that the first response time was 1 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
limelikeme.com performance score
1006 ms
784 ms
4 ms
1179 ms
808 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 92% of them (139 requests) were addressed to the original Limelikeme.com, 2% (3 requests) were made to Web4.logcounter.com and 1% (2 requests) were made to Serial4.logcounter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Limelikeme.com.
Page size can be reduced by 443.1 kB (7%)
6.0 MB
5.5 MB
In fact, the total size of Limelikeme.com main page is 6.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. 80% 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 5.5 MB which makes up the majority of the site volume.
Potential reduce by 152.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 84.7 kB, which is 52% 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 152.0 kB or 93% of the original size.
Potential reduce by 98.6 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. Limelikeme images are well optimized though.
Potential reduce by 169.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 169.2 kB or 67% of the original size.
Potential reduce by 23.3 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. Limelikeme.com needs all CSS files to be minified and compressed as it can save up to 23.3 kB or 81% of the original size.
Number of requests can be reduced by 17 (11%)
149
132
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Limelikeme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
limelikeme.com
1006 ms
common.css
784 ms
wcslog.js
4 ms
jquery-1.7.2.min.js
1179 ms
flash.js
808 ms
rightbanner.js
589 ms
bookmark.js
395 ms
main.css
582 ms
shopRbanner.html
608 ms
header.1.css
777 ms
header.1.js
618 ms
footer.1.css
423 ms
detailpage.js
588 ms
Log_script_logsid.html
594 ms
cookie.js
598 ms
ld.js
25 ms
search_img.gif
795 ms
bottom.jpg
1384 ms
top_bg.jpg
204 ms
top_before.jpg
371 ms
logo.jpg
378 ms
1.jpg
1166 ms
call_center.jpg
405 ms
ca_before(1).jpg
404 ms
ca_before(2).jpg
566 ms
ca_before(3).jpg
572 ms
ca_before(4).jpg
572 ms
ca_before(5).jpg
577 ms
ca_before(6).jpg
596 ms
ca_before(7).jpg
763 ms
ca_before(8).jpg
768 ms
ca_before(9).jpg
769 ms
ca_before(10).jpg
774 ms
item_week.jpg
792 ms
week_img(1).jpg
958 ms
week_img(2).jpg
964 ms
week_img(3).jpg
966 ms
week_img(4).jpg
971 ms
week_img(5).jpg
990 ms
week_img(6).jpg
1154 ms
week_img(7).jpg
1158 ms
week_img(8).jpg
1162 ms
week_img(9).jpg
1167 ms
week_img(10).jpg
1185 ms
item_new.jpg
1349 ms
0050000016343.jpg
1551 ms
7
1359 ms
119
1356 ms
0080000007553.jpg
1558 ms
0050000016393.jpg
1608 ms
0050000016403.jpg
1763 ms
0070000014733.jpg
1573 ms
0080000007563.jpg
1375 ms
0090000008363.jpg
1744 ms
0050000016383.jpg
1386 ms
0050000016373.jpg
1632 ms
scroll.css
1552 ms
0080000007503.jpg
1624 ms
0080000007493.jpg
1769 ms
0110000010623.jpg
1572 ms
0080000007533.jpg
1571 ms
0080000007513.jpg
1582 ms
0080000007543.jpg
1574 ms
0070000014723.jpg
1561 ms
0050000016353.jpg
1570 ms
0090000008353.jpg
1573 ms
0050000016283.jpg
1578 ms
0050000016363.jpg
1576 ms
0060000009863.jpg
1560 ms
0060000009813.jpg
1411 ms
0070000014713.jpg
1761 ms
0080000007523.jpg
1572 ms
0050000016313.jpg
1572 ms
0110000010603.jpg
1557 ms
0050000016303.jpg
1396 ms
0050000016293.jpg
1407 ms
0050000016323.jpg
1571 ms
0060000009873.jpg
1576 ms
0050000016333.jpg
1576 ms
0070000014703.jpg
1562 ms
0090000008343.jpg
1414 ms
0080000007483.jpg
1560 ms
0080000007463.jpg
1569 ms
0080000007403.jpg
1384 ms
0110000010593.jpg
1384 ms
0080000007443.jpg
1385 ms
0080000007433.jpg
1209 ms
0080000007453.jpg
1364 ms
0080000007393.jpg
1350 ms
0050000016223.jpg
1195 ms
0050000016253.jpg
1195 ms
m
458 ms
0060000009913.jpg
1119 ms
0060000009853.jpg
1130 ms
[sr].gif
623 ms
0060000009903.jpg
1283 ms
mslog.js
1032 ms
event
22 ms
event
356 ms
0110000010563.jpg
1197 ms
0060000009893.jpg
1191 ms
0060000009883.jpg
1185 ms
0080000007473.jpg
1190 ms
0050000016233.jpg
1201 ms
0090000008323.jpg
1341 ms
0060000009923.jpg
1197 ms
0070000014673.jpg
1191 ms
0050000016213.jpg
1187 ms
0090000008313.jpg
1191 ms
0050000016143.jpg
1202 ms
0090000008303.jpg
1340 ms
0050000016103.jpg
1189 ms
0110000010543.jpg
1185 ms
0090000008283.jpg
1184 ms
0060000009783.jpg
1188 ms
0090000008293.jpg
1186 ms
Conf_fakeblue.js
775 ms
0110000010503.jpg
1183 ms
0110000010613.jpg
1190 ms
0050000016243.jpg
1193 ms
0050000016273.jpg
1189 ms
0110000010573.jpg
1189 ms
0070000014683.jpg
1186 ms
0060000009833.jpg
1182 ms
0110000010463.jpg
1188 ms
0060000009843.jpg
1193 ms
0110000010523.jpg
1188 ms
0110000010533.jpg
1190 ms
117
1187 ms
ms.log
407 ms
0090000008273.jpg
1182 ms
0110000010553.jpg
1188 ms
0060000009763.jpg
1192 ms
0110000010483.jpg
1185 ms
item_codi.jpg
1191 ms
0050000008483.jpg
1186 ms
121
1182 ms
0140000003493.jpg
1181 ms
0140000003483.jpg
1190 ms
0140000003473.jpg
1189 ms
0140000003443.jpg
1190 ms
0140000003083.jpg
1187 ms
[sr].gif
632 ms
emd_pt.js
825 ms
0140000003453.jpg
1180 ms
0140000003333.jpg
1180 ms
0140000001863.jpg
1192 ms
0140000003223.jpg
1188 ms
0140000003313.jpg
1386 ms
0140000003463.jpg
1187 ms
HTTP_s.js
1195 ms
limelikeme.com SEO score
N/A
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Limelikeme.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Limelikeme.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
limelikeme.com
Open Graph data is detected on the main page of Limelikeme. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: