11 sec in total
518 ms
9.6 sec
873 ms
Welcome to yoshinori-kobayashi.com homepage info - get ready to check Yoshinori Kobayashi best content for Japan right away, or after learning these important things about yoshinori-kobayashi.com
『ゴーマニズム宣言』『おぼっちゃまくん』『東大一直線』などでお馴染みの、漫画家・小林よしのりの公式webサイト。ブログ「あのな、教えたろか。」の配信や、キャリア40年に亘る全作品の紹介、最新情報などをお伝えしていきます。
Visit yoshinori-kobayashi.comWe analyzed Yoshinori-kobayashi.com page load time and found that the first response time was 518 ms and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yoshinori-kobayashi.com performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value13.1 s
0/100
25%
Value11.6 s
4/100
10%
Value230 ms
87/100
30%
Value0
100/100
15%
Value11.9 s
17/100
10%
518 ms
316 ms
73 ms
638 ms
329 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 91% of them (83 requests) were addressed to the original Yoshinori-kobayashi.com, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Yoshinori-kobayashi.com.
Page size can be reduced by 1.6 MB (22%)
7.3 MB
5.7 MB
In fact, the total size of Yoshinori-kobayashi.com main page is 7.3 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. 55% of websites need less resources to load. Images take 6.9 MB which makes up the majority of the site volume.
Potential reduce by 45.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 6.4 kB, which is 11% 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 45.9 kB or 82% of the original size.
Potential reduce by 1.3 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, Yoshinori Kobayashi needs image optimization as it can save up to 1.3 MB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 200.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 200.6 kB or 69% of the original size.
Potential reduce by 29.5 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. Yoshinori-kobayashi.com needs all CSS files to be minified and compressed as it can save up to 29.5 kB or 81% of the original size.
Number of requests can be reduced by 34 (39%)
88
54
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yoshinori Kobayashi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
yoshinori-kobayashi.com
518 ms
style.css
316 ms
jquery.min.js
73 ms
jquery.bxslider.js
638 ms
jquery.page-scroller-308.js
329 ms
chosen.jquery.js
505 ms
function.js
341 ms
styles.css
363 ms
colorbox.min.css
1028 ms
jquery.js
1121 ms
jquery-migrate.min.js
693 ms
external-tracking.min.js
657 ms
jquery.form.min.js
819 ms
scripts.js
957 ms
jquery.colorbox.1.5.9-min.js
968 ms
wp-embed.min.js
1037 ms
reset.css
875 ms
index.css
987 ms
page.css
1135 ms
jquery.bxslider.css
1014 ms
chosen.css
1021 ms
wp-emoji-release.min.js
350 ms
sdk.js
162 ms
ga.js
119 ms
bg.png
480 ms
topslide-bg.png
2754 ms
hg.png
471 ms
logo.png
470 ms
nav_4.png
470 ms
nav_6.png
696 ms
nav_5.png
774 ms
nav_1.png
785 ms
nav_2.png
811 ms
nav_3.png
826 ms
nav_7.png
1065 ms
header-top.png
2150 ms
topics_bg.png
1648 ms
235036c622b360fa9981af0e72f32f22.jpg
1356 ms
00c180325f18844c880271be98db9284.jpg
1611 ms
f417a1b94c5b0519cc2727cd4a328fca.jpg
1650 ms
blank_btn.png
1723 ms
blog_bg.png
2354 ms
0cc6f9879277b1abdb3580db189da907.jpg
2132 ms
1798ee10485aa190cc0344c51b18e9eb.jpg
2244 ms
a51769a9477f374c104590c77104dec6.jpg
2242 ms
28.jpg
2623 ms
works_bg.png
2938 ms
12d0c18ec18bf9e6b558dcdc1a0eedb8.jpg
3353 ms
7c1c5085b5726433e7926331a06b73a8.jpg
3425 ms
98d05b7c00f600b149e3b1d45f1acea9.jpg
3484 ms
b754ae7ed9020242ac558d98805ef5cf.jpg
3506 ms
c27a769b9ea6b6298ec3b922dca22813.jpg
3908 ms
f27ac8dc27b87f792db0108870e7f943.jpg
3518 ms
972ef49420a2a909d1d23a6e628de8e5.jpeg
3981 ms
5026c66ae1c1d4627ccdcbd797d89db7.jpg
5389 ms
6c54a250a800aad1ed75042f15bcf0ff.jpg
4361 ms
f27ac8dc27b87f792db0108870e7f9431.jpg
4277 ms
a79a0c720609dd66e3f88c3b5a29bc2c-e1380613623672.jpg
4264 ms
widgets.js
66 ms
68bc5c62918caf48963ded6801c90cdd-e1380179440574.jpg
4355 ms
__utm.gif
19 ms
279 ms
xd_arbiter.php
128 ms
xd_arbiter.php
394 ms
81a29b8ceb8ca1df39bc3fef3388d7f8-e1380279445621.jpg
4205 ms
cfa1250aa07c935820be0eeca3e3f3ac-e1380279243320.jpg
4425 ms
8c6ed4b35e895d2bf898ac1343d96159-e1380252339397.jpg
4501 ms
goods_bg.png
4685 ms
2f107754177c5a5df8a8fa2ecb78d2fb.jpg
4725 ms
854e0dad67ff776bdd3066835cdf3547.jpg
5085 ms
80c6fa06db7338d16584e43802d24f31.jpg
4758 ms
f506f3d9425d9178b871685c078d85ef.jpg
4824 ms
83fcac219c44e21cdc1c296fb0e810ff.jpg
5287 ms
9133d0a1a62cc4fe2025151e0fa69c0f.jpg
5285 ms
8583c95dbb34932a59bf8a1c5a1451db.jpg
5221 ms
PDS14072_01.jpg
4765 ms
PDS14071_02.jpg
4682 ms
PDS14073_02.jpg
4803 ms
19f4f8fc3a529433ee4de0d3af7c3848.jpg
5093 ms
a5f25c78b100d9a70e94d79082e38db4.jpg
5521 ms
fg.png
4352 ms
f-arrow.png
4452 ms
f-logo.png
4400 ms
pagetop.png
4573 ms
nav_1_on.png
4450 ms
nav_2_on.png
4338 ms
nav_3_on.png
4202 ms
nav_7_on.png
4191 ms
bx_loader.gif
4170 ms
big-arrow-left.png
3742 ms
big-arrow-right.png
3835 ms
yoshinori-kobayashi.com 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
Links do not have a discernible name
yoshinori-kobayashi.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
yoshinori-kobayashi.com 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 uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yoshinori-kobayashi.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 Yoshinori-kobayashi.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.
yoshinori-kobayashi.com
Open Graph description is not detected on the main page of Yoshinori Kobayashi. 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: