5.2 sec in total
612 ms
4.5 sec
158 ms
Click here to check amazing Lazystore content. Otherwise, check out these important facts you probably never knew about lazystore.net
株式会社レイジーストアは、ワッペン(パッチ)・アップリケ・バッジ・ブローチ・アメリカ雑貨・インテリア等の小売業・卸売販売を通し、笑顔のあるライフスタイルの提案を皆様にお届け致します。
Visit lazystore.netWe analyzed Lazystore.net page load time and found that the first response time was 612 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lazystore.net performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value3.7 s
58/100
25%
Value6.2 s
44/100
10%
Value20 ms
100/100
30%
Value0.009
100/100
15%
Value3.7 s
90/100
10%
612 ms
337 ms
353 ms
346 ms
349 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 96% of them (44 requests) were addressed to the original Lazystore.net, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Lazystore.net.
Page size can be reduced by 524.5 kB (43%)
1.2 MB
707.6 kB
In fact, the total size of Lazystore.net main page is 1.2 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. 30% of websites need less resources to load. Images take 561.2 kB which makes up the majority of the site volume.
Potential reduce by 20.6 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 4.5 kB, which is 17% 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 20.6 kB or 77% of the original size.
Potential reduce by 2.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. Lazystore 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 76% of the original size.
Potential reduce by 82.6 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. Lazystore.net needs all CSS files to be minified and compressed as it can save up to 82.6 kB or 89% of the original size.
Number of requests can be reduced by 23 (52%)
44
21
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lazystore. 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.lazystore.net
612 ms
ocnk.js
337 ms
common.css
353 ms
column2.css
346 ms
201305132047042b9088.css
349 ms
jquery.js
559 ms
underscore.js
376 ms
prototype.js
1057 ms
flipsnap.js
681 ms
jquerypp.custom.js
688 ms
jquery.swipeList-min.js
702 ms
jquery.collapser-min.js
715 ms
shared-tool-min.js
925 ms
common.js
1029 ms
form-check.js
1105 ms
bg.gif
180 ms
header_bg.gif
179 ms
20111006_80c305.jpg
333 ms
sub_navi_bg.gif
355 ms
icon01.gif
363 ms
icon02.gif
376 ms
bot_bg.gif
518 ms
menu_bg01.gif
522 ms
side_bg.gif
707 ms
icon_member.gif
716 ms
icon03.gif
708 ms
icon04.gif
737 ms
menu_bg02.gif
859 ms
ssl.gif
881 ms
screen1.jpg
1882 ms
screen2.jpg
1564 ms
screen3.jpg
1291 ms
screen4.jpg
1442 ms
screen5.jpg
1625 ms
whole.jpg
1409 ms
info.jpg
1856 ms
online.jpg
1777 ms
lazy1.jpg
1814 ms
wappen1.jpg
1925 ms
time1.jpg
1955 ms
rakuten1.jpg
2149 ms
yahoo1.jpg
2167 ms
rss10.gif
2215 ms
what_top_bg.gif
2205 ms
ga.js
8 ms
__utm.gif
13 ms
lazystore.net 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.
lazystore.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
Page has valid source maps
lazystore.net 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 uses 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 Lazystore.net 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 Lazystore.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.
lazystore.net
Open Graph description is not detected on the main page of Lazystore. 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: