7 sec in total
640 ms
4.8 sec
1.5 sec
Welcome to yogen.bz homepage info - get ready to check Yogen best content right away, or after learning these important things about yogen.bz
Visit yogen.bzWe analyzed Yogen.bz page load time and found that the first response time was 640 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
yogen.bz performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value9.0 s
1/100
25%
Value10.5 s
7/100
10%
Value40 ms
100/100
30%
Value0.43
22/100
15%
Value8.1 s
41/100
10%
640 ms
209 ms
375 ms
209 ms
352 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that all of those requests were addressed to Yogen.bz and no external sources were called. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Yogen.bz.
Page size can be reduced by 287.0 kB (7%)
4.2 MB
3.9 MB
In fact, the total size of Yogen.bz main page is 4.2 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. 25% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 6.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 6.1 kB or 74% of the original size.
Potential reduce by 259.2 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. Yogen images are well optimized though.
Potential reduce by 21.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. Yogen.bz needs all CSS files to be minified and compressed as it can save up to 21.7 kB or 80% of the original size.
Number of requests can be reduced by 6 (10%)
62
56
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yogen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for CSS and as a result speed up the page load time.
yogen.bz
640 ms
import.css
209 ms
import.js
375 ms
reset.css
209 ms
common.css
352 ms
top.css
367 ms
guide.css
381 ms
domain.css
402 ms
howto.css
404 ms
profile.css
414 ms
info.css
536 ms
back01.png
832 ms
back02.jpg
371 ms
back03.png
1002 ms
common_border.jpg
191 ms
common_deco-left.png
366 ms
common_deco-right.png
403 ms
common_page-back.png
380 ms
header.jpg
1654 ms
top_firsttext.png
740 ms
top_special-back.png
1704 ms
top_special-btn.gif
806 ms
top_nayami-deai.png
1485 ms
top_nayami-deai1.png
1211 ms
top_nayami-deai2.png
1243 ms
top_nayami-deai3.png
1204 ms
top_nayami-deai4.png
1407 ms
top_nayami-kataomoi.png
2018 ms
top_nayami-kataomoi1.png
1454 ms
top_nayami-kataomoi2.png
1613 ms
top_nayami-kataomoi3.png
1665 ms
top_nayami-kataomoi4.png
1672 ms
top_nayami-kosai.png
2214 ms
top_nayami-kosai1.png
1840 ms
top_nayami-kosai2.png
2081 ms
top_nayami-kosai3.png
1864 ms
top_nayami-kosai4.png
1896 ms
top_nayami-hukuen.png
2213 ms
top_nayami-hukuen1.png
2054 ms
top_nayami-hukuen2.png
2091 ms
top_nayami-hukuen3.png
2222 ms
top_nayami-hukuen4.png
2246 ms
top_nayami-kekkon.png
2706 ms
top_nayami-kekkon1.png
2287 ms
top_nayami-kekkon2.png
2418 ms
top_nayami-kekkon3.png
2401 ms
top_nayami-kekkon4.png
2393 ms
top_nayami-hurin.png
2446 ms
top_nayami-hurin1.png
2125 ms
top_nayami-hurin2.png
2229 ms
top_nayami-hurin3.png
2253 ms
top_nayami-hurin4.png
2242 ms
top_teller.png
2135 ms
top_story-top.jpg
1975 ms
top_story-bottom.jpg
2005 ms
top_story-center.jpg
1823 ms
top_categori-back.png
1640 ms
top_story-image.jpg
1709 ms
top_free-back.gif
1914 ms
top_free-shinri.gif
1600 ms
top_free-power.gif
1581 ms
top_free-meigen.gif
1563 ms
top_free-husui.gif
1451 ms
top_free-yume.gif
1480 ms
top_free-sex.gif
1530 ms
common_pointpresent.png
1770 ms
common_footer-back.jpg
1548 ms
yogen.bz 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.
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
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
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.
yogen.bz 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
yogen.bz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yogen.bz 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 Yogen.bz 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.
yogen.bz
Open Graph description is not detected on the main page of Yogen. 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: