Tools & Wizards About Us
lear-japan.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lear-japan.com

カスタム IEM イヤホン LEAR Japan

Page Load Speed

4.9 sec in total

First Response

758 ms

Resources Loaded

3.9 sec

Page Rendered

210 ms

lear-japan.com screenshot

About Website

Welcome to lear-japan.com homepage info - get ready to check LEAR Japan best content right away, or after learning these important things about lear-japan.com

カスタムIEM イヤホンのLEAR Japan　公式通販サイトになります。

Visit lear-japan.com

Key Findings

We analyzed Lear-japan.com page load time and found that the first response time was 758 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

lear-japan.com performance score

0

Network Requests Diagram

lear-japan.com

758 ms

import.css

167 ms

css.js

317 ms

navi.js

320 ms

win_op.js

330 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 95% of them (61 requests) were addressed to the original Lear-japan.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Lear-japan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 346.0 kB (23%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lear-japan.com main page is 1.5 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. 25% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.2 kB

  • Original 18.4 kB
  • After minification 16.7 kB
  • After compression 4.2 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 14.2 kB or 77% of the original size.

Image Optimization

-17%

Potential reduce by 232.3 kB

  • Original 1.3 MB
  • After minification 1.1 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. Obviously, LEAR Japan needs image optimization as it can save up to 232.3 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 64.7 kB

  • Original 110.0 kB
  • After minification 101.3 kB
  • After compression 45.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 64.7 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 34.7 kB

  • Original 41.8 kB
  • After minification 27.8 kB
  • After compression 7.1 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. Lear-japan.com needs all CSS files to be minified and compressed as it can save up to 34.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (40%)

Requests Now

63

After Optimization

38

  • Images
  • JavaScript
  • CSS

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LEAR Japan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lear-japan.com

lear-japan.com

758 ms

import.css

import.css

167 ms

css.js

css.js

317 ms

navi.js

navi.js

320 ms

win_op.js

win_op.js

330 ms

site.js

site.js

332 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

497 ms

main_top_branding.js

main_top_branding.js

335 ms

reset.css

reset.css

308 ms

common.css

common.css

317 ms

contents.css

contents.css

334 ms

table.css

table.css

332 ms

bloc.css

bloc.css

340 ms

print.css

print.css

465 ms

css

css

26 ms

ga.js

ga.js

53 ms

h1_logo.png

h1_logo.png

343 ms

btn_header_cart.png

btn_header_cart.png

171 ms

bg_cart_info_td.gif

bg_cart_info_td.gif

167 ms

bg_header_navi.png

bg_header_navi.png

162 ms

bg_header_navi_li.gif

bg_header_navi_li.gif

159 ms

bg_container.gif

bg_container.gif

167 ms

h2_product_category.png

h2_product_category.png

318 ms

btn_category_earphone.png

btn_category_earphone.png

323 ms

lcm_2f_main.jpg

lcm_2f_main.jpg

1312 ms

lcm_1f_title.png

lcm_1f_title.png

331 ms

lcm_series.png

lcm_series.png

338 ms

lcm_2f_spec.png

lcm_2f_spec.png

786 ms

lcm_1f_price.png

lcm_1f_price.png

797 ms

btn_buynow.png

btn_buynow.png

497 ms

lcm_2b_main.jpg

lcm_2b_main.jpg

1339 ms

lcm_3b_title.png

lcm_3b_title.png

507 ms

lcm_3c_price.png

lcm_3c_price.png

987 ms

lcm_1b_main.jpg

lcm_1b_main.jpg

1171 ms

lcm_3c_title.png

lcm_3c_title.png

944 ms

lcm_3b_main.jpg

lcm_3b_main.jpg

1586 ms

lcm_2f_title.png

lcm_2f_title.png

1103 ms

lcm_2f_price.png

lcm_2f_price.png

1320 ms

h2_about.png

h2_about.png

1262 ms

img_top_about.jpg

img_top_about.jpg

1387 ms

bana_kasidasi.png

bana_kasidasi.png

1898 ms

h2_recommend.png

h2_recommend.png

1477 ms

resize_image.php

resize_image.php

1675 ms

img_review_stars_4.png

img_review_stars_4.png

1505 ms

resize_image.php

resize_image.php

1741 ms

img_review_stars_0.png

img_review_stars_0.png

1642 ms

resize_image.php

resize_image.php

1858 ms

resize_image.php

resize_image.php

1921 ms

resize_image.php

resize_image.php

1991 ms

resize_image.php

resize_image.php

2016 ms

h2_guide_flow.png

h2_guide_flow.png

1908 ms

h3_guide_flow_step_1.png

h3_guide_flow_step_1.png

1986 ms

__utm.gif

__utm.gif

19 ms

h3_guide_flow_step_2.png

h3_guide_flow_step_2.png

1903 ms

h3_guide_flow_step_3.png

h3_guide_flow_step_3.png

1920 ms

h3_guide_flow_step_4.png

h3_guide_flow_step_4.png

1922 ms

h2_guide_info_delivery.png

h2_guide_info_delivery.png

1997 ms

h2_guide_info_payment.png

h2_guide_info_payment.png

2020 ms

img_guide_info_payment.png

img_guide_info_payment.png

1891 ms

btn_branding_navi_off.png

btn_branding_navi_off.png

1895 ms

bg_top_about.png

bg_top_about.png

1918 ms

bg_guide_flow_r.png

bg_guide_flow_r.png

1910 ms

bg_guide_info_r.gif

bg_guide_info_r.gif

1988 ms

btn_branding_navi_on.png

btn_branding_navi_on.png

169 ms

SEO Factors

lear-japan.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lear-japan.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 Lear-japan.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.

Social Sharing Optimization

lear-japan.com

Open Graph description is not detected on the main page of LEAR Japan. 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: