3.6 sec in total
968 ms
2.2 sec
428 ms
Welcome to fu-chi-ku-chi.jp homepage info - get ready to check Fu Chi Ku best content right away, or after learning these important things about fu-chi-ku-chi.jp
[eo_events event_start_after="2020-6-20 15:00" event_st
Visit fu-chi-ku-chi.jpWe analyzed Fu-chi-ku-chi.jp page load time and found that the first response time was 968 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fu-chi-ku-chi.jp performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value10.6 s
0/100
25%
Value9.0 s
14/100
10%
Value940 ms
29/100
30%
Value0.105
88/100
15%
Value12.0 s
16/100
10%
968 ms
74 ms
138 ms
143 ms
142 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 86% of them (75 requests) were addressed to the original Fu-chi-ku-chi.jp, 5% (4 requests) were made to Platform.twitter.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (968 ms) belongs to the original domain Fu-chi-ku-chi.jp.
Page size can be reduced by 273.0 kB (27%)
998.5 kB
725.6 kB
In fact, the total size of Fu-chi-ku-chi.jp main page is 998.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 725.9 kB which makes up the majority of the site volume.
Potential reduce by 24.4 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 24.4 kB or 80% of the original size.
Potential reduce by 78.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. Obviously, Fu Chi Ku needs image optimization as it can save up to 78.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 118.1 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 118.1 kB or 66% of the original size.
Potential reduce by 52.3 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. Fu-chi-ku-chi.jp needs all CSS files to be minified and compressed as it can save up to 52.3 kB or 82% of the original size.
Number of requests can be reduced by 23 (27%)
86
63
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fu Chi Ku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
fu-chi-ku-chi.jp
968 ms
base.css
74 ms
style.css
138 ms
okb.css
143 ms
home.css
142 ms
fullcalendar.css
144 ms
fullcalendar.print.css
149 ms
libs.min.js
391 ms
okb.min.js
202 ms
ga.js
205 ms
jquery-ui.custom.min.js
209 ms
fullcalendar.min.js
283 ms
gcal.js
218 ms
common.js
269 ms
home.js
270 ms
loading.gif
277 ms
slide-next.png
291 ms
slide-back.png
335 ms
logo.png
338 ms
catch.png
345 ms
h-news.png
350 ms
bt-list.png
364 ms
h-schedule.png
400 ms
sche-midashi.png
405 ms
h-twitter.png
413 ms
twitter-txt.png
420 ms
twitter-pic.png
510 ms
okb.css
335 ms
okb.ui.css
338 ms
okb.form.css
343 ms
okb.ui.css
73 ms
okb.form.css
72 ms
widgets.js
95 ms
bg.jpg
434 ms
slide-paging.png
88 ms
gnav-ac.png
87 ms
gnav-top.png
90 ms
gnav-menu.png
90 ms
gnav-schedule.png
86 ms
gnav-access.png
185 ms
gnav-news.png
184 ms
gnav-faq.png
185 ms
gnav-party_off.png
186 ms
catch-bg.png
186 ms
bg-content.png
204 ms
white2-t.png
206 ms
white2-c.png
279 ms
arw.png
222 ms
white2-b.png
229 ms
white1-t.png
269 ms
white1-c.png
344 ms
twitter-icon.png
297 ms
white1-b.png
319 ms
h-menu.png
342 ms
menu-txt.png
348 ms
menu-pic.png
444 ms
bt-menu.png
382 ms
h-access.png
409 ms
access-address.png
411 ms
access-time.png
418 ms
bt-map.png
459 ms
h-party.png
477 ms
party-txt.png
479 ms
party-pic.png
488 ms
bt-party.png
497 ms
faq-txt.png
518 ms
bt-faq.png
534 ms
footer-home.png
552 ms
footer-copyright.png
505 ms
footer-pagetop.png
477 ms
ga.js
12 ms
__utm.gif
62 ms
__utm.gif
53 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
120 ms
slide-next_ov.png
466 ms
slide-back_ov.png
465 ms
bt-list_ov.png
465 ms
bt-menu_ov.png
464 ms
bt-map_ov.png
537 ms
bt-faq_ov.png
536 ms
syndication
81 ms
374081060163706881
221 ms
1f343.png
36 ms
1f302.png
30 ms
1f423.png
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
32 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
88 ms
fu-chi-ku-chi.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
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
fu-chi-ku-chi.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
Page has valid source maps
fu-chi-ku-chi.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 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 Fu-chi-ku-chi.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 Fu-chi-ku-chi.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.
fu-chi-ku-chi.jp
Open Graph description is not detected on the main page of Fu Chi Ku. 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: