Tools & Wizards About Us
lesud.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lesud.jp

先天性耳瘻孔との付き合い方

Page Load Speed

7.8 sec in total

First Response

488 ms

Resources Loaded

7.2 sec

Page Rendered

135 ms

lesud.jp screenshot

About Website

Visit lesud.jp now to see the best up-to-date Lesud content and also check out these interesting facts you probably never knew about lesud.jp

耳の付け根にちょっと不思議な穴が開いている先天性耳瘻孔(せんてんせいじろうこう）。劣性遺伝と言われています。穴がある人でも耳瘻孔という名前に気づかずに過ごしている人も多くいます。穴から複雑に迷路のようになって皮下とか結合組織に入り込んで長くなってる場合もあります。そして、できる位置や、長さも人によって違っています。両耳に先天性耳漏孔をもつ当サイト管理人が約３０年間も耳漏孔という言葉を知らずに日々疑...

Visit lesud.jp

Key Findings

We analyzed Lesud.jp page load time and found that the first response time was 488 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

lesud.jp performance score

0

Network Requests Diagram

lesud.jp

488 ms

www.lesud.jp

519 ms

styles.css

317 ms

l.j

295 ms

7-1.jpg

461 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 26% of them (6 requests) were addressed to the original Lesud.jp, 57% (13 requests) were made to Mo1.s79.coreserver.jp and 13% (3 requests) were made to J1.ax.xrea.com. The less responsive or slowest element that took the longest time to load (5.4 sec) relates to the external source Wj.ax.xrea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.7 kB (24%)

Content Size

120.3 kB

After Optimization

91.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lesud.jp main page is 120.3 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. Only 10% of websites need less resources to load. Images take 83.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 11.1 kB

  • Original 14.9 kB
  • After minification 13.0 kB
  • After compression 3.9 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 1.9 kB, which is 13% 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 11.1 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 801 B

  • Original 83.2 kB
  • After minification 82.3 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. Lesud images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 3.9 kB

  • Original 6.5 kB
  • After minification 6.3 kB
  • After compression 2.6 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 3.9 kB or 60% of the original size.

CSS Optimization

-82%

Potential reduce by 13.0 kB

  • Original 15.7 kB
  • After minification 10.1 kB
  • After compression 2.8 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. Lesud.jp needs all CSS files to be minified and compressed as it can save up to 13.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (24%)

Requests Now

21

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lesud.jp

lesud.jp

488 ms

www.lesud.jp

www.lesud.jp

519 ms

styles.css

styles.css

317 ms

l.j

l.j

295 ms

7-1.jpg

7-1.jpg

461 ms

8-1.jpg

8-1.jpg

494 ms

http_3a_2f_2fwww_2elesud_2ejp_2fm_2f.gif

http_3a_2f_2fwww_2elesud_2ejp_2fm_2f.gif

334 ms

Kids.css

Kids.css

478 ms

content-bk.jpg

content-bk.jpg

310 ms

banner.jpg

banner.jpg

966 ms

up_bar.gif

up_bar.gif

331 ms

middle_bar.gif

middle_bar.gif

337 ms

bttm_bar.gif

bttm_bar.gif

352 ms

h2-upper.gif

h2-upper.gif

353 ms

h2-lower.gif

h2-lower.gif

635 ms

side-dt.gif

side-dt.gif

638 ms

side-dd.gif

side-dd.gif

645 ms

atom.gif

atom.gif

656 ms

rss.gif

rss.gif

682 ms

3career.gif

3career.gif

938 ms

x.gif

x.gif

147 ms

l44.f

l44.f

5373 ms

ts.gif

ts.gif

293 ms

SEO Factors

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

lesud.jp

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