6.3 sec in total
1.1 sec
4 sec
1.2 sec
Click here to check amazing Yohoho content for Japan. Otherwise, check out these important facts you probably never knew about yohoho.jp
なるべくお金を使わずにラクに生きるための、先住民技術、電気、ウェブ、政治、デザイン、読み物などを公開している架空の研究所。主催はヒッピーのテンダー。
Visit yohoho.jpWe analyzed Yohoho.jp page load time and found that the first response time was 1.1 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
yohoho.jp performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value9.4 s
0/100
25%
Value7.4 s
27/100
10%
Value660 ms
45/100
30%
Value0.155
74/100
15%
Value8.2 s
40/100
10%
1147 ms
185 ms
348 ms
25 ms
541 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 49% of them (35 requests) were addressed to the original Yohoho.jp, 20% (14 requests) were made to Pbs.twimg.com and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Yohoho.jp.
Page size can be reduced by 204.5 kB (5%)
3.9 MB
3.7 MB
In fact, the total size of Yohoho.jp main page is 3.9 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.7 MB which makes up the majority of the site volume.
Potential reduce by 48.3 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 7.7 kB, which is 12% 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 48.3 kB or 78% of the original size.
Potential reduce by 14.5 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. Yohoho images are well optimized though.
Potential reduce by 55.9 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 55.9 kB or 58% of the original size.
Potential reduce by 85.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. Yohoho.jp needs all CSS files to be minified and compressed as it can save up to 85.8 kB or 84% of the original size.
Number of requests can be reduced by 24 (36%)
66
42
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yohoho. 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 from 7 to 1 for CSS and as a result speed up the page load time.
yohoho.jp
1147 ms
wp-emoji-release.min.js
185 ms
styles.css,qver=4.4.pagespeed.ce.fIjaP8m3jJ.css
348 ms
css
25 ms
style.css,qver=4.4.2.pagespeed.ce.W5iHmFMaGp.css
541 ms
wpp.css,qver=3.3.3.pagespeed.ce.ZUwz9rjzGg.css
358 ms
jquery.min.js
31 ms
jquery.smoothScroll.js.pagespeed.jm.V6JOIYNKH5.js
365 ms
cssua.min.js
359 ms
yubinbango.js
32 ms
jquery.form.min.js
365 ms
scripts.js
518 ms
wp-embed.min.js
530 ms
sdk.js
125 ms
ga.js
127 ms
widgets.js
127 ms
feedly-follow-rectangle-flat-small_2x.png
93 ms
back-golf.jpg
202 ms
icon.png
203 ms
xbanner_wagaya_long_01.jpg.pagespeed.ic.qXmnhNzoPf.jpg
781 ms
640x360xkokyogesui_51.jpg.pagespeed.ic.6cu3YKgPrS.jpg
943 ms
180x101xminamatasolar_61.jpg.pagespeed.ic.FPqMXtVUC2.jpg
1301 ms
ribbon.png
201 ms
180x101xkokyo_gesui_41.jpg.pagespeed.ic.F-6EJqRNA3.jpg
1237 ms
180x120xwagaya_tsuika_14.jpg.pagespeed.ic.f4srPqIGDs.jpg
1269 ms
180x120xwagaya_tsuika_00-1.jpg.pagespeed.ic.6Z6hAcsv1s.jpg
1261 ms
180x255x4ce3491d392fc13acac2556fde558bd2.jpg.pagespeed.ic.EPiMQxiwGd.jpg
1973 ms
180x97xkamp_01.jpg.pagespeed.ic.hYjE6E3RQN.jpg
1430 ms
180x67xjorge_banner.jpg.pagespeed.ic.rPgtgZrQeL.jpg
1320 ms
180x282xnanten_kiji_00.jpg.pagespeed.ic.RdeVwCnWfQ.jpg
1999 ms
180x135xsuishitsu_12.jpg.pagespeed.ic.BSYBIQG7aV.jpg
1640 ms
180x135xIMG_0766.jpg.pagespeed.ic.FY0ZaLSEGz.jpg
1845 ms
60x43xsawyer_02-200x143.jpg.pagespeed.ic.gdFm61ygR5.jpg
1511 ms
60x40xhippie_00-200x133.jpg.pagespeed.ic.swbND985w3.jpg
1609 ms
60x45xflowlife05-200x150.jpg.pagespeed.ic.8qw1iQjjiV.jpg
1692 ms
category.jpg
1782 ms
search.png
1822 ms
banner-kagoden.png.pagespeed.ce.t9lqDzi2RL.png
1875 ms
banner-tee.png.pagespeed.ce.O1mk-1kM7m.png
1959 ms
xbanner-kagoshimaguide.png.pagespeed.ic.gVsa4aiaYQ.jpg
2019 ms
totop.png.pagespeed.ce.cdGm9WUVjs.png
2024 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
86 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
86 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
87 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
86 ms
__utm.gif
30 ms
408 ms
xd_arbiter.php
308 ms
xd_arbiter.php
313 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
143 ms
syndication
93 ms
392447181317079040
282 ms
2668.png
34 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
42 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
187 ms
VjxraVhr_normal.jpg
173 ms
pict01_normal.jpg
276 ms
CceQIJoUAAALPJB.jpg
263 ms
Ccd0-3YW0AAj45x.jpg
223 ms
CcbrOb1VAAE5rWi.jpg
223 ms
CcZGa9_UAAEZpu7.jpg
221 ms
CcYmsZTVIAAVj8-.jpg
176 ms
CcWhmPLUYAAHU7C.jpg
338 ms
CcT8xfyUYAAKsqo.jpg
286 ms
CcRX-kjUAAAEASf.jpg
313 ms
CcOzFhvUAAAA-OA.jpg
385 ms
CcMOP1DUAAA9JtJ.jpg
305 ms
CcJpcHfUMAE63YT.jpg:small
281 ms
CcHbx9xUYAA7J_O.jpg:small
284 ms
jot
30 ms
smartphone.css.pagespeed.ce.H9L0doDiIg.css
182 ms
yohoho.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
yohoho.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
yohoho.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Yohoho.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 Yohoho.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.
yohoho.jp
Open Graph description is not detected on the main page of Yohoho. 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: