Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lekue.jp

lekue.jp - ルクエ スチームケース スチームロースター キッチン キヌア Resources and Information.

Page Load Speed

16.6 sec in total

First Response

6.9 sec

Resources Loaded

9.5 sec

Page Rendered

208 ms

lekue.jp screenshot

About Website

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.jp

Key Findings

We 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.

Performance Metrics

lekue.jp performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.136

80/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

www.lekue.jp

6877 ms

postratings-css.css

306 ms

jquery.js

999 ms

tsa_params.min.js

553 ms

hoverIntent.js

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 Optimization Overview & Recommendations

Page size can be reduced by 331.1 kB (16%)

Content Size

2.0 MB

After Optimization

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.

HTML Optimization

-78%

Potential reduce by 35.0 kB

  • Original 45.0 kB
  • After minification 40.8 kB
  • After compression 10.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.

Image Optimization

-9%

Potential reduce by 156.8 kB

  • Original 1.8 MB
  • After minification 1.6 MB

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.

JavaScript Optimization

-59%

Potential reduce by 92.5 kB

  • Original 157.8 kB
  • After minification 154.2 kB
  • After compression 65.3 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.

CSS Optimization

-82%

Potential reduce by 46.7 kB

  • Original 57.1 kB
  • After minification 45.9 kB
  • After compression 10.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. 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.

Requests Breakdown

Number of requests can be reduced by 45 (42%)

Requests Now

106

After Optimization

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.

Accessibility Review

lekue.jp accessibility score

63

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lekue.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lekue.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: