7.8 sec in total
1.3 sec
6.1 sec
443 ms
Visit fuefuki-kanko.jp now to see the best up-to-date Fuefuki Kanko content for Japan and also check out these interesting facts you probably never knew about fuefuki-kanko.jp
「日本一桃源郷」笛吹市公式の観光ポータルサイトふえふき観光ナビ。笛吹市の観光・温泉・桃狩り・ぶどう狩り・ワイナリーの情報はここから!
Visit fuefuki-kanko.jpWe analyzed Fuefuki-kanko.jp page load time and found that the first response time was 1.3 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fuefuki-kanko.jp performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value22.2 s
0/100
25%
Value15.9 s
0/100
10%
Value930 ms
30/100
30%
Value0.684
7/100
15%
Value15.0 s
8/100
10%
1272 ms
327 ms
332 ms
510 ms
32 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 78% of them (75 requests) were addressed to the original Fuefuki-kanko.jp, 8% (8 requests) were made to Apis.google.com and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Fuefuki-kanko.jp.
Page size can be reduced by 335.5 kB (17%)
2.0 MB
1.7 MB
In fact, the total size of Fuefuki-kanko.jp main page is 2.0 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. 50% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 36.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 36.4 kB or 75% of the original size.
Potential reduce by 32.1 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. Fuefuki Kanko images are well optimized though.
Potential reduce by 38.0 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 38.0 kB or 60% of the original size.
Potential reduce by 229.1 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. Fuefuki-kanko.jp needs all CSS files to be minified and compressed as it can save up to 229.1 kB or 92% of the original size.
Number of requests can be reduced by 36 (39%)
93
57
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fuefuki Kanko. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
fuefuki-kanko.jp
1272 ms
index.css
327 ms
footer.css
332 ms
common.js
510 ms
jquery-1.10.2.js
32 ms
xdr.js
356 ms
heightLine.js
359 ms
font-awesome.css
6 ms
async-script.js
490 ms
top.css
502 ms
layout.css
606 ms
evoslider.css
550 ms
jquery-1.7.1.min.js
946 ms
jquery.easing.1.3.js
662 ms
jquery.evoslider-2.1.4.js
1198 ms
evoslider-setting.js
510 ms
common.css
807 ms
user.css
681 ms
widgets.js
117 ms
plusone.js
115 ms
like.php
172 ms
bnr_2_20111017093335512.gif
392 ms
cms_20160301_024033399.jpg
704 ms
btnSearch.png
208 ms
top.png
198 ms
top.png
359 ms
top.png
200 ms
top.png
356 ms
top.png
369 ms
image.php
756 ms
titSide_w250.png
671 ms
image.php
1543 ms
image.php
765 ms
image.php
712 ms
image.php
878 ms
image.php
1033 ms
bnr_11_20141028111317620.jpg
1527 ms
bnr_11_20150327113302787.jpg
1099 ms
bnr_11_20120119154221375.jpg
1520 ms
bnr_11_20120119154235761.jpg
1680 ms
bnr_5_20151022140103703.jpg
1402 ms
bnr_5_20151002004459284.jpg
1525 ms
bnr_5_20150129103823335.jpg
1767 ms
bnr_5_20150302173608860.jpg
1747 ms
bnr_5_20140701093215675.jpg
1762 ms
bnr_5_201407010927480.jpg
1784 ms
bnr_5_20140602102736800.jpg
2140 ms
bnr_5_2014120517341199.jpg
2034 ms
bnr_5_20150428164607229.jpg
1929 ms
bnr_5_201501291106011.jpg
1947 ms
bnr_12_20110319133749792.gif
1933 ms
bnr_12_20110319133757718.gif
1999 ms
bnr_12_2013071614472811.jpg
2108 ms
bnr_12_20130712102131824.jpg
2102 ms
bnr_12_20130712102222243.jpg
2124 ms
bnr_12_20130716144824551.gif
2194 ms
bnr_12_20140320102240382.jpg
2366 ms
cb=gapi.loaded_0
17 ms
cb=gapi.loaded_1
31 ms
fastbutton
93 ms
analytics.js
32 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
138 ms
postmessageRelay
76 ms
qeKvIRsJabD.js
193 ms
LVx-xkvaJ0b.png
208 ms
collect
43 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
26 ms
titMain_w690.png
2305 ms
image.php
2570 ms
image.php
2545 ms
3193398744-postmessagerelay.js
16 ms
rpc:shindig_random.js
34 ms
cb=gapi.loaded_0
3 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
43 ms
cms_20160317_12095418.jpg
2853 ms
cms_20160228_220456695.jpg
3190 ms
cms_20160224_131334709.jpg
2730 ms
ico_star_5.png
2401 ms
jot
92 ms
bnr_13_20111227121703740.jpg
2419 ms
bnr_13_20111227114353585.gif
2256 ms
bnr_13_20120606142027169.jpg
2248 ms
bnr_13_20120606142905188.jpg
2599 ms
bnr_17_20160229214747170.jpg
2566 ms
bnr_17_20160229214732907.jpg
2715 ms
title_bar.png
2296 ms
thumbnail_004.jpg
2308 ms
spinner.gif
2112 ms
slide_004.jpg
2327 ms
icoNew.gif
2017 ms
ico14.gif
2074 ms
ico02.gif
2146 ms
icoTitMailmaga.png
2145 ms
icoPhoto.gif
2093 ms
titMain_w790.png
2212 ms
fuefuki-kanko.jp accessibility score
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
fuefuki-kanko.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
Browser errors were logged to the console
Page has valid source maps
fuefuki-kanko.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Fuefuki-kanko.jp 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 Fuefuki-kanko.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.
fuefuki-kanko.jp
Open Graph data is detected on the main page of Fuefuki Kanko. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: