Tools & Wizards About Us
lezhin.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

lezhin.jp

レジンコミックス - オリジナル漫画が毎日更新

Page Load Speed

6.1 sec in total

First Response

351 ms

Resources Loaded

4.1 sec

Page Rendered

1.6 sec

lezhin.jp screenshot

About Website

Welcome to lezhin.jp homepage info - get ready to check Lezhin best content for Japan right away, or after learning these important things about lezhin.jp

ヨソでは読めないフルカラーオリジナル漫画が無料で読める!

Visit lezhin.jp

Key Findings

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

Performance Metrics

lezhin.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value28.1 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value3,130 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value22.3 s

1/100

10%

Network Requests Diagram

lezhin.jp

351 ms

lezhin.jp

713 ms

www.lezhin.jp

722 ms

ja

384 ms

8b7e5ee26c97b514.css

357 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 63% of them (39 requests) were addressed to the original Lezhin.jp, 37% (23 requests) were made to Ccdn.lezhin.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Lezhin.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 102.1 kB (55%)

Content Size

184.8 kB

After Optimization

82.7 kB

  • HTML
  • Images

In fact, the total size of Lezhin.jp main page is 184.8 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. 35% of websites need less resources to load. HTML takes 97.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 82.5 kB

  • Original 97.6 kB
  • After minification 97.6 kB
  • After compression 15.1 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 82.5 kB or 85% of the original size.

Image Optimization

-22%

Potential reduce by 19.6 kB

  • Original 87.1 kB
  • After minification 67.6 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. Obviously, Lezhin needs image optimization as it can save up to 19.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 41 (71%)

Requests Now

58

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lezhin.jp

lezhin.jp

351 ms

lezhin.jp

lezhin.jp

713 ms

www.lezhin.jp

www.lezhin.jp

722 ms

ja

ja

384 ms

8b7e5ee26c97b514.css

8b7e5ee26c97b514.css

357 ms

ea602308bfe9c9de.css

ea602308bfe9c9de.css

527 ms

8e98c150d1f8721a.css

8e98c150d1f8721a.css

532 ms

972a6d113fb5f5ad.css

972a6d113fb5f5ad.css

533 ms

276cb786096a1a2a.css

276cb786096a1a2a.css

535 ms

5caa29ec2bf0a99c.css

5caa29ec2bf0a99c.css

537 ms

c4d40b5d9eaafc07.css

c4d40b5d9eaafc07.css

547 ms

6de73394ace6daa0.css

6de73394ace6daa0.css

703 ms

443919cb-aeb4f98848ca4af8.js

443919cb-aeb4f98848ca4af8.js

1057 ms

3629-c15ed30b5f07f525.js

3629-c15ed30b5f07f525.js

888 ms

main-app-c7af23af24e617de.js

main-app-c7af23af24e617de.js

712 ms

0ed1bab3-dc6d5105ffceeba9.js

0ed1bab3-dc6d5105ffceeba9.js

1253 ms

4038-4e8bef71ee631ef1.js

4038-4e8bef71ee631ef1.js

1095 ms

2221-a3433e0189ffdcc4.js

2221-a3433e0189ffdcc4.js

879 ms

3680-570469e9499f608d.js

3680-570469e9499f608d.js

891 ms

2590-f7f37cf2f6cc6dea.js

2590-f7f37cf2f6cc6dea.js

1062 ms

5415-c9b8c7ce362fb802.js

5415-c9b8c7ce362fb802.js

1071 ms

4081-072a179b7ca8ab35.js

4081-072a179b7ca8ab35.js

1070 ms

4899-1e205ead1cbece05.js

4899-1e205ead1cbece05.js

1234 ms

8591-31995e0b509774cf.js

8591-31995e0b509774cf.js

1234 ms

2733-8e8d244ed9746585.js

2733-8e8d244ed9746585.js

1249 ms

6361-9f15570303fbfc24.js

6361-9f15570303fbfc24.js

1250 ms

page-cea5cf41661f1f46.js

page-cea5cf41661f1f46.js

1280 ms

9460-a390911c77a1d459.js

9460-a390911c77a1d459.js

1429 ms

global-error-05e7439ac2a5b58b.js

global-error-05e7439ac2a5b58b.js

1410 ms

error-13311fe077d7235c.js

error-13311fe077d7235c.js

1427 ms

5964-1e9eb9fd5c377a03.js

5964-1e9eb9fd5c377a03.js

1434 ms

9602-fc69abe5a69139f1.js

9602-fc69abe5a69139f1.js

1429 ms

2731-40ce576e4ff95921.js

2731-40ce576e4ff95921.js

1463 ms

layout-d2663b77cc23a4f4.js

layout-d2663b77cc23a4f4.js

1590 ms

error-b3e20fd4bf5142ea.js

error-b3e20fd4bf5142ea.js

1606 ms

roboto.css

roboto.css

1603 ms

noto-sans-jp.css

noto-sans-jp.css

1804 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

1614 ms

webpack-d7365f950b6527f7.js

webpack-d7365f950b6527f7.js

1643 ms

jaymee.svg

jaymee.svg

115 ms

btn-adult-off-ja-lt.png

btn-adult-off-ja-lt.png

103 ms

28-gift2.svg

28-gift2.svg

106 ms

28-search.svg

28-search.svg

103 ms

28-hamberger.svg

28-hamberger.svg

104 ms

icon-line.svg

icon-line.svg

112 ms

icon-google.svg

icon-google.svg

105 ms

icon-yahoo.svg

icon-yahoo.svg

110 ms

icon-facebook.svg

icon-facebook.svg

106 ms

sns-x-lt.svg

sns-x-lt.svg

107 ms

icon-apple.svg

icon-apple.svg

108 ms

icon-welcome-gift.png

icon-welcome-gift.png

112 ms

s-twitter2-lt.png

s-twitter2-lt.png

109 ms

s-insta-lt.png

s-insta-lt.png

110 ms

s-youtube-lt.png

s-youtube-lt.png

110 ms

s-blog-lt.png

s-blog-lt.png

219 ms

lt-btn-plus-jp-w.png

lt-btn-plus-jp-w.png

116 ms

lt-btn-google-w.png

lt-btn-google-w.png

113 ms

lt-btn-appstore-w.png

lt-btn-appstore-w.png

112 ms

lezhin.png

lezhin.png

111 ms

abj_lt.png

abj_lt.png

113 ms

24-arrow-up.png

24-arrow-up.png

112 ms

ico-adult-ja-lt.svg

ico-adult-ja-lt.svg

180 ms

Accessibility Review

lezhin.jp accessibility score

74

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s are not contained by their required parent element

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lezhin.jp SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 uses legible font sizes

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

lezhin.jp

Open Graph data is detected on the main page of Lezhin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: