3.8 sec in total
40 ms
2.3 sec
1.5 sec
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.jpWe analyzed Lezhin.jp page load time and found that the first response time was 40 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lezhin.jp performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value19.5 s
0/100
25%
Value11.0 s
6/100
10%
Value2,990 ms
3/100
30%
Value0.015
100/100
15%
Value19.2 s
2/100
10%
40 ms
370 ms
19 ms
28 ms
29 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lezhin.jp, 74% (67 requests) were made to Ncdn.lezhin.com and 13% (12 requests) were made to Lezhin.com. The less responsive or slowest element that took the longest time to load (919 ms) relates to the external source Ncdn.lezhin.com.
Page size can be reduced by 1.0 MB (26%)
4.0 MB
3.0 MB
In fact, the total size of Lezhin.jp main page is 4.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 347.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. 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 347.9 kB or 87% of the original size.
Potential reduce by 353.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. Obviously, Lezhin needs image optimization as it can save up to 353.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 196.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 196.6 kB or 61% of the original size.
Potential reduce by 126.6 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. Lezhin.jp needs all CSS files to be minified and compressed as it can save up to 126.6 kB or 83% of the original size.
Number of requests can be reduced by 12 (14%)
87
75
The browser has sent 87 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 13 to 1 for JavaScripts and as a result speed up the page load time.
lezhin.jp
40 ms
;jsessionid=Y7vNqbOxjMcj2rhd01jXSQ
370 ms
global-v3-prod-16186499abf1d2d244788cde60ee0189.css
19 ms
home-v3-prod-501b221e30391149da595c6c13ed1d02.css
28 ms
jquery-1409211049125.js
29 ms
lodash-1434726502566.js
14 ms
typeahead.bundle-1431497428787.js
48 ms
s2-global-616eafd914d1ca52ad8ffc1b4b2e48f0.js
52 ms
s2-common-d65f0def5ad44e02ddc604f6bd4e9ba6.js
76 ms
conversion.js
50 ms
jquery.tada-1437280031543.js
82 ms
s2-comic-home-47df33e3710b1cc41bc366bf6cb68fa0.js
83 ms
logo-68.png
493 ms
ico-newmenu-red.png
576 ms
analytics.js
523 ms
fbevents.js
357 ms
519 ms
gtm.js
518 ms
lzcon_10737e7df91927c64461e961637f6e83.svg
515 ms
lzcon_10737e7df91927c64461e961637f6e83.woff
515 ms
load
708 ms
img-curation-layer.png
178 ms
wide
358 ms
square
357 ms
promotionBanner
180 ms
promotionBanner
487 ms
square
177 ms
square
178 ms
wide
354 ms
wide
355 ms
promotionBanner
488 ms
promotionBanner
489 ms
promotionBanner
491 ms
promotionBanner
492 ms
promotionBanner
493 ms
wide
495 ms
thumbnail
498 ms
thumbnail
495 ms
thumbnail
521 ms
thumbnail
499 ms
wide
502 ms
thumbnail
504 ms
thumbnail
503 ms
thumbnail
505 ms
thumbnail
498 ms
wide
505 ms
thumbnail
507 ms
thumbnail
510 ms
thumbnail
517 ms
thumbnail
509 ms
wide
510 ms
wide
506 ms
wide
844 ms
wide
511 ms
wide
512 ms
ico-new.png
428 ms
389 ms
wide
652 ms
325 ms
thumbnail
919 ms
thumbnail
342 ms
thumbnail
341 ms
linkid.js
159 ms
thumbnail
167 ms
thumbnail
170 ms
thumbnail
169 ms
thumbnail
170 ms
thumbnail
233 ms
square
226 ms
square
351 ms
square
224 ms
square
224 ms
square
222 ms
square
223 ms
square
222 ms
square
223 ms
square
220 ms
square
218 ms
square
218 ms
square
217 ms
square
216 ms
square
216 ms
square
215 ms
square
214 ms
topBanner
214 ms
topBannerMobile
213 ms
btn-close-topbanner.png
213 ms
common.png
212 ms
collect
10 ms
collect
53 ms
notice-hdpi.png
15 ms
lezhin.jp accessibility score
lezhin.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lezhin.jp SEO score
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 uses legible font sizes
JA
JA
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.
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: