16.6 sec in total
6.9 sec
9.5 sec
208 ms
Welcome to lekue.jp homepage info - get ready to check Lekue best content for Japan right away, or after learning these important things about lekue.jp
lekue.jp is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, lekue.jp has it all. We hope you find what you ...
Visit lekue.jpWe analyzed Lekue.jp page load time and found that the first response time was 6.9 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lekue.jp performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value0.9 s
100/100
25%
Value2.0 s
99/100
10%
Value270 ms
82/100
30%
Value0.136
80/100
15%
Value3.1 s
95/100
10%
6877 ms
306 ms
999 ms
553 ms
1573 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 56% of them (62 requests) were addressed to the original Lekue.jp, 22% (24 requests) were made to Static.xx.fbcdn.net and 5% (6 requests) were made to Coram.co.jp. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Lekue.jp.
Page size can be reduced by 331.1 kB (16%)
2.0 MB
1.7 MB
In fact, the total size of Lekue.jp main page is 2.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. 70% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 35.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. 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 35.0 kB or 78% of the original size.
Potential reduce by 156.8 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. Lekue images are well optimized though.
Potential reduce by 92.5 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 92.5 kB or 59% of the original size.
Potential reduce by 46.7 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. Lekue.jp needs all CSS files to be minified and compressed as it can save up to 46.7 kB or 82% of the original size.
Number of requests can be reduced by 45 (42%)
106
61
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lekue. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.lekue.jp
6877 ms
postratings-css.css
306 ms
jquery.js
999 ms
tsa_params.min.js
553 ms
hoverIntent.js
1573 ms
superfish.js
1574 ms
default.css
606 ms
3c-fixed.css
710 ms
user.css
910 ms
toggle-switcher.js
868 ms
base.css
154 ms
ga.js
46 ms
bana_shop.jpg
542 ms
spring1.jpg
762 ms
201409-01.jpg
765 ms
201410-01.jpg
636 ms
201409-02.jpg
893 ms
201404-04B.jpg
897 ms
rs2013.gif
1429 ms
review1.gif
915 ms
manga.png
915 ms
photo1_20141129_231111-132x132.jpg
1071 ms
photo1_20141128_191100-132x132.jpg
1073 ms
photo1_20141128_191106-132x132.jpg
1067 ms
photo1_20141126_211101-132x132.jpg
1068 ms
photo1_20141126_211116-132x132.jpg
1218 ms
photo1_20141126_221131-132x132.jpg
1219 ms
photo1_20141124_131117-132x132.jpg
1247 ms
photo1_20141124_131123-132x132.jpg
1250 ms
photo1_20141123_171124-132x132.jpg
1369 ms
photo1_20141123_171111-132x132.jpg
1370 ms
photo1_20141120_231139-132x132.jpg
1424 ms
photo1_20141118_221150-132x132.jpg
1427 ms
LekueRecipe-11.jpg
1515 ms
prev.png
1515 ms
next.png
1594 ms
mizutama.png
1576 ms
tool-title_sr.png
1597 ms
tool-title.png
1666 ms
__utm.gif
11 ms
bana_shop.jpg
540 ms
jquery.ui.core.min.js
154 ms
jquery.ui.widget.min.js
154 ms
jquery.ui.tabs.min.js
160 ms
jquery.cycle.min.js
356 ms
postratings-js.js
179 ms
oyako.jpg
507 ms
lekue-curry.jpg
910 ms
party.jpg
760 ms
obento125.jpg
671 ms
pro.jpg
712 ms
mens.jpg
887 ms
bijin.jpg
828 ms
ebara.jpg
995 ms
recipeblog.jpg
1177 ms
pan-recipe.gif
910 ms
sample.jpg
1182 ms
plaza-vegefood.gif
1175 ms
yonekyu.jpg
1218 ms
yellowtail.jpg
1219 ms
sdk.js
11 ms
widgets.js
83 ms
footer-bg.jpg
528 ms
coram.png
537 ms
searchsubmit.gif
1163 ms
121 ms
xd_arbiter.php
38 ms
xd_arbiter.php
43 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
125 ms
thumb-bg2.jpg
345 ms
rating_over.gif
836 ms
comments.gif
838 ms
feed-title-white.jpg
935 ms
page.php
517 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
43 ms
404.html
363 ms
404.html
333 ms
jot
89 ms
404.html
431 ms
-bSdoXNF-FL.css
26 ms
qBBLx_j_YWO.css
30 ms
gPLjjXw4kx2.css
30 ms
MrIRm6wo5X6.css
34 ms
wNJXghTCtIz.css
31 ms
FAHeNGXgPup.js
33 ms
k19Xse48j5I.js
50 ms
ihptErjAmMX.js
59 ms
3So47A9WcrL.js
58 ms
cUsKAwzqrQw.js
65 ms
XWkrVsE9d-K.js
74 ms
juKryPYAUFc.js
73 ms
FzGTmhgBEqv.js
84 ms
lRyN50VcaFW.js
86 ms
545112_427002443980719_658943040_n.jpg
112 ms
b8XhdWI9eAN.js
28 ms
1010711_1250384328309189_2339294098607803206_n.jpg
19 ms
941065_1250384071642548_8730825304015519824_n.jpg
29 ms
700_1250383958309226_5740920682579764399_n.jpg
21 ms
12365596_1669925263276159_1228775954_n.jpg
23 ms
994747_1246676202013335_8049394585284144771_n.jpg
20 ms
ZS8q378OQsF.png
15 ms
wL6VQj7Ab77.png
15 ms
s7jcwEQH7Sx.png
15 ms
GtIpNnEyqq_.png
15 ms
e3Spc1mcUJw.png
17 ms
R9a_DtVRZgv.js
5 ms
cUDgRFxaoIk.js
3 ms
0JBr1QHp8Gi.js
5 ms
kDOzhTr2W91.js
2 ms
mylink-toggle-open.css
162 ms
mylink-toggle-close.css
163 ms
lekue.jp 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
<frame> or <iframe> elements do not have a title
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.
lekue.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
lekue.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lekue.jp 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 Japanese language. Our system also found out that Lekue.jp 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.
lekue.jp
Open Graph description is not detected on the main page of Lekue. 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: