4.6 sec in total
603 ms
3.7 sec
269 ms
Visit lem-shop.com now to see the best up-to-date Lem Shop content for Japan and also check out these interesting facts you probably never knew about lem-shop.com
L.E.M.サプライは、ガン、ミリタリー、ロウエンフォスメントに興味を持つ皆様に魅力ある商品を提供していきます。
Visit lem-shop.comWe analyzed Lem-shop.com page load time and found that the first response time was 603 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
lem-shop.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value4.7 s
33/100
25%
Value6.7 s
37/100
10%
Value120 ms
97/100
30%
Value0.841
4/100
15%
Value3.9 s
89/100
10%
603 ms
183 ms
345 ms
341 ms
350 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 96% of them (64 requests) were addressed to the original Lem-shop.com, 3% (2 requests) were made to Lemsupplyco.ocnk.net and 1% (1 request) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Lem-shop.com.
Page size can be reduced by 579.6 kB (60%)
971.0 kB
391.5 kB
In fact, the total size of Lem-shop.com main page is 971.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 533.6 kB which makes up the majority of the site volume.
Potential reduce by 70.1 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 26.8 kB, which is 34% 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 70.1 kB or 88% of the original size.
Potential reduce by 15.9 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. Lem Shop images are well optimized though.
Potential reduce by 418.4 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 418.4 kB or 78% of the original size.
Potential reduce by 75.2 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. Lem-shop.com needs all CSS files to be minified and compressed as it can save up to 75.2 kB or 88% of the original size.
Number of requests can be reduced by 25 (38%)
65
40
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lem 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 12 to 1 for JavaScripts and as a result speed up the page load time.
www.lem-shop.com
603 ms
ocnk.js
183 ms
common_ie9.css
345 ms
column2.css
341 ms
20121013193556665ae0.css
350 ms
jquery.js
549 ms
underscore.js
369 ms
prototype.js
766 ms
flipsnap.js
508 ms
jquerypp.custom.js
510 ms
jquery.swipeList-min.js
519 ms
jquery.collapser-min.js
564 ms
shared-tool-min.js
678 ms
common.js
678 ms
form-check.js
691 ms
banner2.jpg
546 ms
bg.jpg
361 ms
20120703_b27dce.jpg
922 ms
sub_navi_bg.gif
175 ms
icon01.gif
172 ms
icon02.gif
191 ms
bot_bg.gif
171 ms
menu_bg01.gif
341 ms
icon04.gif
342 ms
menu_bg02.gif
347 ms
cart.gif
378 ms
icon_member.gif
508 ms
icon03.gif
509 ms
ssl.gif
519 ms
top_title_bg01.gif
541 ms
70726f647563742f726d70312e6a70670038300000660066.jpg
566 ms
new.gif
677 ms
70726f647563742f6461615f62656c74735f7765622e6a70670038300000660066.jpg
678 ms
70726f647563742f32303135303432305f6361663232352e4a50470038300000660066.jpg
691 ms
70726f647563742f3736322d312e6a70670038300000660066.jpg
720 ms
70726f647563742f32303132313032325f3235386431312e6a70670038300000660066.jpg
753 ms
70726f647563742f32303132313031365f6135356433662e6a70670038300000660066.jpg
845 ms
no1.gif
846 ms
70726f647563742f32303132313031375f3636383936362e6a70670038300000660066.jpg
863 ms
70726f647563742f32303132313031375f3232643531342e6a70670038300000660066.jpg
900 ms
70726f647563742f32303132313031385f6438396437312e6a70670038300000660066.jpg
941 ms
70726f647563742f32303132313031375f3939633764342e6a70670038300000660066.jpg
1014 ms
70726f647563742f32303132313031375f6435326162642e6a70670038300000660066.jpg
1016 ms
70726f647563742f32303132313032325f6339613732382e6a70670038300000660066.jpg
1036 ms
70726f647563742f32303132313032325f3363326264372e6a70670038300000660066.jpg
1080 ms
70726f647563742f32303132313031385f6666373863392e6a70670038300000660066.jpg
1103 ms
70726f647563742f32303132313032325f3338383134382e6a70670038300000660066.jpg
1129 ms
70726f647563742f32303136303331305f3333613331372e6a70670038300000660066.jpg
1183 ms
70726f647563742f32303136303330345f6234613838352e6a70670038300000660066.jpg
1184 ms
70726f647563742f32303136303232385f3233353831302e4a50470038300000660066.jpg
1208 ms
70726f647563742f32303136303232385f3566363738382e4a50470038300000660066.jpg
1260 ms
banner4.png
715 ms
widgets.js
9 ms
70726f647563742f32303136303232385f6536643465322e4a50470038300000660066.jpg
1232 ms
70726f647563742f32303135303230335f3765653438312e6a70670038300000660066.jpg
1149 ms
70726f647563742f32303132313031365f3461386138322e6a70670038300000660066.jpg
1184 ms
no3.gif
1184 ms
70726f647563742f32303132313031385f3065636366632e6a70670038300000660066.jpg
1195 ms
70726f647563742f32303132313032325f6532366462652e6a70670038300000660066.jpg
1104 ms
70726f647563742f32303132313031365f3236646365662e6a70670038300000660066.jpg
1130 ms
70726f647563742f32303132313031365f3762393561322e6a70670038300000660066.jpg
1161 ms
70726f647563742f32303132313031375f3563623330332e6a70670038300000660066.jpg
1166 ms
70726f647563742f32303132313032325f6636323332312e6a70670038300000660066.jpg
1149 ms
70726f647563742f32303132313031365f3365353130622e6a70670038300000660066.jpg
1048 ms
70726f647563742f32303132313031365f3034643935342e6a70670038300000660066.jpg
1115 ms
counter.php
1161 ms
rss10.gif
1155 ms
lem-shop.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
lem-shop.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lem-shop.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lem-shop.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Lem-shop.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.
lem-shop.com
Open Graph description is not detected on the main page of Lem Shop. 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: