9.3 sec in total
1.7 sec
7.4 sec
205 ms
Click here to check amazing Fasting content for Japan. Otherwise, check out these important facts you probably never knew about fasting.bz
健康と美容と食育のスペシャリストになろう!ファスティングのプロに学ぶ本物のファスティングメソッド
Visit fasting.bzWe analyzed Fasting.bz page load time and found that the first response time was 1.7 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fasting.bz performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value10.0 s
0/100
25%
Value11.8 s
4/100
10%
Value710 ms
42/100
30%
Value0.457
19/100
15%
Value11.4 s
19/100
10%
1660 ms
329 ms
891 ms
348 ms
360 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 95% of them (83 requests) were addressed to the original Fasting.bz, 2% (2 requests) were made to Staticxx.facebook.com and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Fasting.bz.
Page size can be reduced by 521.6 kB (19%)
2.7 MB
2.2 MB
In fact, the total size of Fasting.bz main page is 2.7 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 26.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 26.1 kB or 75% of the original size.
Potential reduce by 15.8 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. Fasting images are well optimized though.
Potential reduce by 371.2 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 371.2 kB or 68% of the original size.
Potential reduce by 108.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. Fasting.bz needs all CSS files to be minified and compressed as it can save up to 108.5 kB or 81% of the original size.
Number of requests can be reduced by 38 (44%)
86
48
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fasting. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.fasting.bz
1660 ms
style.css
329 ms
jquery-1.4.4.min.js
891 ms
slides.min.jquery.js
348 ms
script.js
360 ms
events_manager.css
390 ms
events-manager-pro.css
590 ms
pagenavi-css.css
497 ms
main.css
701 ms
jquery-ui.min.css
867 ms
theme.css
571 ms
jquery.js
1144 ms
jquery-migrate.min.js
758 ms
core.min.js
771 ms
widget.min.js
878 ms
position.min.js
938 ms
mouse.min.js
955 ms
sortable.min.js
1206 ms
datepicker.min.js
1216 ms
menu.min.js
1051 ms
autocomplete.min.js
1118 ms
resizable.min.js
1317 ms
draggable.min.js
1220 ms
button.min.js
1321 ms
dialog.min.js
1300 ms
events-manager.js
1405 ms
events-manager-pro.js
1406 ms
selectmenu.min.js
1234 ms
main.js
1470 ms
common.css
1195 ms
style.css
1185 ms
wp-emoji-release.min.js
205 ms
body_bg.jpg
187 ms
logo.gif
166 ms
tel.gif
182 ms
form00_on.jpg
185 ms
form00_off.jpg
377 ms
form01_on.gif
284 ms
form01_off.gif
324 ms
form02_on.gif
367 ms
form02_off.gif
368 ms
form03_on.gif
358 ms
form03_off.gif
471 ms
nav01_on.jpg
494 ms
nav01_off.jpg
528 ms
nav02_on.jpg
697 ms
nav02_off.jpg
701 ms
nav03_on.jpg
741 ms
nav03_off.jpg
826 ms
nav04_on.jpg
657 ms
nav04_off.jpg
700 ms
nav05_on.jpg
817 ms
nav05_off.jpg
883 ms
main_bg.jpg
2382 ms
main01.jpg
1706 ms
main02.jpg
2204 ms
main03.jpg
1459 ms
main04.jpg
2071 ms
main_cap.png
1049 ms
wrap_bg.jpg
1217 ms
news.png
1391 ms
bana00_on.png
1735 ms
image.jpeg
1777 ms
bana00_off.png
1880 ms
kenko.jpg
1910 ms
topImg.jpg
2111 ms
sdk.js
27 ms
topBana02_on.jpg
2013 ms
97 ms
xd_arbiter.php
46 ms
xd_arbiter.php
51 ms
topBana02_off.jpg
2132 ms
topBana03_on.jpg
2057 ms
topBana03_off.jpg
2094 ms
topBana06_on.jpg
2093 ms
topBana06_off.jpg
2216 ms
topBana05_on.jpg
2118 ms
topBana05_off.jpg
2258 ms
topBana01_on.jpg
2104 ms
topBana01_off.jpg
2076 ms
topBana04_on.jpg
2204 ms
topBana04_off.jpg
2194 ms
foot_txt.jpg
2123 ms
foot_logo.png
2110 ms
foot_ico.gif
2115 ms
foot_ico02.gif
2099 ms
page_top.png
2045 ms
fasting.bz accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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.
fasting.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
Browser errors were logged to the console
fasting.bz 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fasting.bz 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 Fasting.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.
fasting.bz
Open Graph description is not detected on the main page of Fasting. 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: