5.7 sec in total
1.1 sec
4.4 sec
237 ms
Visit funari.jp now to see the best up-to-date Funari content and also check out these interesting facts you probably never knew about funari.jp
「ほうとう日本一」のタイトル獲得の山梨ほうとう専門店『歩成』は山梨県産の厳選素材と職人の業が調和した、極上〈こだわり〉のほうとうです。甲府、勝沼、ほったらかし温泉観光の際は是非、お立ち寄り下さい。
Visit funari.jpWe analyzed Funari.jp page load time and found that the first response time was 1.1 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
funari.jp performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value11.3 s
0/100
25%
Value8.6 s
17/100
10%
Value940 ms
29/100
30%
Value0.774
5/100
15%
Value11.2 s
20/100
10%
1135 ms
874 ms
541 ms
373 ms
376 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 85% of them (46 requests) were addressed to the original Funari.jp, 4% (2 requests) were made to Apis.google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Funari.jp.
Page size can be reduced by 229.2 kB (29%)
780.8 kB
551.6 kB
In fact, the total size of Funari.jp main page is 780.8 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. 25% of websites need less resources to load. Images take 437.1 kB which makes up the majority of the site volume.
Potential reduce by 11.7 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 11.7 kB or 71% of the original size.
Potential reduce by 2.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. Funari images are well optimized though.
Potential reduce by 177.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 177.0 kB or 64% of the original size.
Potential reduce by 38.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. Funari.jp needs all CSS files to be minified and compressed as it can save up to 38.3 kB or 79% of the original size.
Number of requests can be reduced by 39 (75%)
52
13
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funari. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.funari.jp
1135 ms
style.css
874 ms
response.css
541 ms
iview.css
373 ms
jquery.bxslider.css
376 ms
style.css
388 ms
styles.css
531 ms
easy-fancybox.css.php
764 ms
jquery.min.js
13 ms
jquery.fancybox-1.3.4.pack.js
932 ms
plusone.js
35 ms
jquery.rollover.js
409 ms
responsive-nav.js
715 ms
footerFixed.js
548 ms
smoothScroll.js
602 ms
gallery.js
728 ms
css_browser_selector.js
780 ms
breakpoints.js
796 ms
raphael-min.js
1567 ms
iview.js
1480 ms
jquery.bxslider.min.js
1264 ms
jquery.easing.js
945 ms
jquery.form.js
1332 ms
scripts.js
1177 ms
jquery.easing-1.3.pack.js
1132 ms
jquery.mousewheel-3.0.4.pack.js
1149 ms
jquery.metadata.js
1198 ms
conversion.js
17 ms
reset.css
751 ms
cb=gapi.loaded_0
29 ms
bg.jpg
358 ms
head_bg.png
372 ms
logo-pc.gif
359 ms
gnav.gif
374 ms
icon_fb.gif
195 ms
icon_tw.gif
177 ms
main_08.jpg
1049 ms
news_bg.png
389 ms
news_title.png
538 ms
news_btn.png
540 ms
news_line.png
559 ms
category-publicity.gif
562 ms
category-info.gif
582 ms
category-media.gif
718 ms
banner_03c.jpg
934 ms
banner_02.jpg
927 ms
btn_pagetop.gif
749 ms
footer_nav.gif
775 ms
copyright.gif
896 ms
ga.js
30 ms
57 ms
iconmenu.png
888 ms
__utm.gif
19 ms
37 ms
funari.jp 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
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
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.
funari.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
funari.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
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 Funari.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 Funari.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.
funari.jp
Open Graph description is not detected on the main page of Funari. 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: