9.2 sec in total
1.7 sec
7.1 sec
356 ms
Click here to check amazing Contendo content for Japan. Otherwise, check out these important facts you probably never knew about contendo.jp
電子書籍・コミックなどの総合電子書籍ストア『ConTenDo|コンテン堂』。まずは立ち読みから。音声・動画付きコンテンツあり。文字モノが読みやすい『ConTenDoビューア』。スマホ・タブレット・パソコンで読める!
Visit contendo.jpWe analyzed Contendo.jp page load time and found that the first response time was 1.7 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
contendo.jp performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value12.4 s
0/100
25%
Value8.0 s
22/100
10%
Value100 ms
98/100
30%
Value1.079
2/100
15%
Value7.2 s
51/100
10%
1727 ms
394 ms
393 ms
410 ms
403 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 69% of them (106 requests) were addressed to the original Contendo.jp, 18% (27 requests) were made to Pbs.twimg.com and 5% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Contendo.jp.
Page size can be reduced by 532.5 kB (13%)
4.1 MB
3.6 MB
In fact, the total size of Contendo.jp main page is 4.1 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. 65% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 53.6 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 53.6 kB or 80% of the original size.
Potential reduce by 303.9 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. Contendo images are well optimized though.
Potential reduce by 75.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 75.3 kB or 58% of the original size.
Potential reduce by 99.7 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. Contendo.jp needs all CSS files to be minified and compressed as it can save up to 99.7 kB or 84% of the original size.
Number of requests can be reduced by 40 (26%)
152
112
The browser has sent 152 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Contendo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
contendo.jp
1727 ms
type.css
394 ms
home.css
393 ms
genres.css
410 ms
names.css
403 ms
common.js
610 ms
jquery-1.4.4.min.js
1354 ms
brand
14 ms
widgets.js
89 ms
word-surfing.css
413 ms
jquery.fs.boxer.min.css
626 ms
jquery.min.js
33 ms
infiniteslide.js
423 ms
jquery.pause.min.js
604 ms
jquery.fs.boxer.min.js
808 ms
brand
56 ms
slides.css
441 ms
slides.min.jquery.js
575 ms
reset.css
585 ms
base.css
625 ms
common.css
824 ms
navi.css
785 ms
contents.css
1381 ms
palette.css
855 ms
NewSelect.css
509 ms
NewSelect.js
624 ms
gs_image_110-55_en.js
14 ms
gs_noscript_110-55_en.gif
15 ms
body_back.gif
251 ms
btn_kaiin.gif
250 ms
btn_hajimete.gif
251 ms
bg_header.jpg
463 ms
header_logo.jpg
880 ms
bg_header2.gif
324 ms
btn_search.gif
767 ms
pdtl0000043179_00001.jpg
576 ms
pdtl0000018341_00001.jpg
902 ms
pdtl0000044251_00001.jpg
810 ms
pdtl0000040806_00001.jpg
971 ms
pdtl0000042763_00001.jpg
841 ms
pdtl0000039870_00001.jpg
1348 ms
pdtl0000032966_00001.jpg
1028 ms
pdtl0000043482_00001.jpg
1055 ms
pdtl0000043538_00001.jpg
1280 ms
pdtl0000043026_00001.jpg
1110 ms
pdtl0000042863_00001.jpg
1223 ms
pdtl0000025676_00001.jpg
1257 ms
pdtl0000040211_00001.jpg
1274 ms
pdtl0000043222_00001.jpg
1329 ms
pdtl0000044258_00001.jpg
2216 ms
pdtl0000042988_00001.jpg
1458 ms
pdtl0000042574_00001.jpg
1484 ms
pdtl0000044254_00001.jpg
2217 ms
wave.png
1528 ms
logo.png
1559 ms
search-icon.png
2215 ms
hatena.png
2217 ms
ft0000000182.png
2218 ms
ft0000000180.png
2218 ms
ft0000000178.png
2219 ms
ft0000000172.jpg
2220 ms
ft0000000164.jpg
2225 ms
ft0000000163.jpg
2220 ms
ft0000000159.png
2216 ms
like.php
67 ms
ga.js
32 ms
siteSeal.do
616 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
128 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
153 ms
__utm.gif
24 ms
TY3MhkXpWJ-.js
563 ms
LVx-xkvaJ0b.png
564 ms
ft0000000155.png
1980 ms
ft0000000149.png
1982 ms
ft0000000148.png
2921 ms
syndication
79 ms
344644237398249472
316 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
45 ms
ft0000000139.png
3060 ms
ft0000000114.png
1772 ms
ft0000000119.jpg
1879 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
124 ms
49592b634e28dbd7fe91f82089325ebd_normal.png
179 ms
Cd1st-OXIAAZ1Aw.jpg:small
435 ms
Cd1fBqhW0AAWHOf.jpg:small
322 ms
Cd1KHCAW8AAwJmZ.jpg:small
418 ms
Cd0uhipWAAEEgkc.jpg:small
347 ms
Cd0gysnUMAA5jUI.jpg:small
396 ms
Cd0TCt7UAAA9U7_.jpg:small
419 ms
CdzwwtFWIAAHVfQ.jpg:small
420 ms
CdzHmOIXIAAWln7.jpg:small
564 ms
CdysO7CUIAASUbL.jpg:small
514 ms
CdyQxniW8AAR5qr.jpg:small
592 ms
CdwjK-uWEAA2YK6.jpg:small
595 ms
CdwVbxaWEAE6O-O.jpg:small
552 ms
CdwAgtbXEAAA8v7.jpg:small
514 ms
Cdvk8CAWwAA7dA4.jpg:small
566 ms
CdvILMiUYAAdVoV.jpg:small
664 ms
CdunJZpWoAAnH8s.jpg:small
873 ms
CduYJIlUUAA9t5p.jpg:small
745 ms
CduSY1_UUAE8no6.jpg:small
632 ms
Cd16YzfWAAAEanr.jpg:small
721 ms
Cd16YsKWIAAD-77.jpg:small
846 ms
Cd16YsVW0AABC9g.jpg:small
716 ms
Cd16Ys3W0AELOcb.jpg:small
800 ms
Cd08RH5UMAELx2P.jpg:small
848 ms
Cd08Q3yWoAAlzjz.jpg:small
850 ms
Cd08Q44W0AAeC-_.jpg:small
875 ms
Cd08Q9SW8AA-LTV.jpg:small
921 ms
siteSealImage.do
195 ms
ft0000000115.png
1507 ms
ft0000000150.jpg
1504 ms
ft0000000060.jpg
1532 ms
ft0000000057.jpg
1637 ms
ft0000000092.jpg
1627 ms
pdtl0000043590_00002.jpg
1616 ms
pdtl0000039501_00001.jpg
1657 ms
jot.html
27 ms
pdtl0000040011_00001.jpg
1681 ms
btn_tachiyomi_s.png
1629 ms
pdtl0000008776_00006.jpg
1587 ms
pdtl0000031029_00001.jpg
1641 ms
pdtl0000026420_00001.jpg
1679 ms
pdtl0000033165_00001.jpg
1677 ms
pdtl0000039432_00001.jpg
1689 ms
pdtl0000046995_00001.jpg
1778 ms
pdtl0000030504_00001.jpg
1709 ms
pdtl0000026412_00002.jpg
1695 ms
pdtl0000039480_00001.jpg
1694 ms
pdtl0000025857_00001.jpg
1785 ms
pdtl0000031107_00001.jpg
1164 ms
pdtl0000046629_00001.jpg
1543 ms
pdtl0000036018_00001.jpg
1194 ms
pdtl0000034242_00001.jpg
1223 ms
pdtl0000026807_00001.jpg
1343 ms
pdtl0000028106_00001.jpg
1578 ms
pdtl0000043610_00001.jpg
1374 ms
pdtl0000028251_00001.jpg
1415 ms
app_contendo.png
1440 ms
store_banner_small.png
1780 ms
store_banner_small.png
1600 ms
store_banner_small.png
1626 ms
store_banner_small.png
1630 ms
store_banner_small.png
1735 ms
store_banner_small.png
1709 ms
store_banner_small.png
1725 ms
facebook-banner.png
1695 ms
bg_navi2.jpg
1600 ms
bg_navi.jpg
1656 ms
bg_container.gif
1695 ms
icon_genre.png
1679 ms
pagination.png
1588 ms
ace_arrow_gray.png
1564 ms
contendo.jp accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
contendo.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
General
Impact
Issue
Detected JavaScript libraries
contendo.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contendo.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Contendo.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.
contendo.jp
Open Graph description is not detected on the main page of Contendo. 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: