10.1 sec in total
1.3 sec
8.5 sec
295 ms
Welcome to tsunose.co.jp homepage info - get ready to check Tsunose best content right away, or after learning these important things about tsunose.co.jp
大阪の名物として多くの方に親しまれている「粟おこし」。長年の伝統とこだわりから生まれた豊かな風味は、いつの時代も本物の味として選ばれ続けています。
Visit tsunose.co.jpWe analyzed Tsunose.co.jp page load time and found that the first response time was 1.3 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
tsunose.co.jp performance score
name
value
score
weighting
Value24.6 s
0/100
10%
Value37.9 s
0/100
25%
Value54.9 s
0/100
10%
Value440 ms
64/100
30%
Value0.594
11/100
15%
Value36.4 s
0/100
10%
1281 ms
335 ms
849 ms
354 ms
563 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 91% of them (61 requests) were addressed to the original Tsunose.co.jp, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Tsunose.co.jp.
Page size can be reduced by 234.6 kB (23%)
1.0 MB
771.1 kB
In fact, the total size of Tsunose.co.jp main page is 1.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. 30% of websites need less resources to load. Images take 715.6 kB which makes up the majority of the site volume.
Potential reduce by 25.2 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 25.2 kB or 76% of the original size.
Potential reduce by 21.9 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. Tsunose images are well optimized though.
Potential reduce by 76.7 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 76.7 kB or 57% of the original size.
Potential reduce by 110.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. Tsunose.co.jp needs all CSS files to be minified and compressed as it can save up to 110.7 kB or 90% of the original size.
Number of requests can be reduced by 12 (18%)
66
54
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tsunose. 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 JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.tsunose.co.jp
1281 ms
style.css
335 ms
theme.css
849 ms
files_common.css
354 ms
files_pc.css
563 ms
jquery.SimplaModalwindow.css
371 ms
inquiry-form.css
536 ms
jquery.js
1314 ms
jquery-migrate.min.js
738 ms
jquery.SimplaModalwindow.js
750 ms
ajaxzip2.js
926 ms
jquery.upload.js
940 ms
all.js
163 ms
bg.jpg
436 ms
ga.js
141 ms
00_header.jpg
530 ms
pc_teaser_01.jpg
746 ms
button_cartin_on_02.gif
355 ms
button_cartin_02.gif
360 ms
theme.css
906 ms
00_menu_001.jpg
398 ms
00_menu_002.jpg
718 ms
00_menu_003.jpg
733 ms
00_menu_004_02.jpg
962 ms
00_menu_005.jpg
931 ms
00_menu_006.jpg
1089 ms
00_title_000-e1395729212220.jpg
1279 ms
title_news.jpg
1139 ms
read_more_btn.jpg
1297 ms
sp1.gif
1351 ms
00_bnr_001.jpg
1696 ms
00_bnr_002.jpg
1843 ms
00_bnr_003.jpg
1944 ms
00_bnr_004.jpg
2009 ms
00_title_003.jpg
1684 ms
00_title_004.jpg
1716 ms
00_img_001_01.jpg
2241 ms
00_img_001_02.jpg
2073 ms
00_img_001_03.jpg
2063 ms
00_img_001_04.jpg
2203 ms
00_img_001_06.jpg
2301 ms
00_title_005.jpg
2441 ms
00_img_002_01.jpg
2597 ms
00_img_002_02.jpg
2431 ms
00_img_002_03.jpg
2602 ms
00_title_006_02.jpg
2610 ms
00_img_003_akihuyu01.jpg
2854 ms
00_img_003_id20.jpg
2782 ms
00_img_003_id19.jpg
2847 ms
00_img_003_id18.jpg
2987 ms
141 ms
00_img_003_id33.jpg
2987 ms
xd_arbiter.php
129 ms
xd_arbiter.php
253 ms
__utm.gif
14 ms
00_img_003_id34.jpg
2684 ms
00_title_007.jpg
2793 ms
00_img_003_akihuyu02.jpg
3017 ms
00_img_003_id24.jpg
2697 ms
00_img_003_id21.jpg
2637 ms
00_img_003_id31.jpg
2619 ms
00_img_003_id29.jpg
2685 ms
00_img_003_id35.jpg
2611 ms
00_title_008.jpg
2639 ms
footer_02.jpg
2897 ms
loading.gif
2660 ms
close.png
2634 ms
tsunose.co.jp 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.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
tsunose.co.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
Issues were logged in the Issues panel in Chrome Devtools
tsunose.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Tsunose.co.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 Tsunose.co.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.
tsunose.co.jp
Open Graph description is not detected on the main page of Tsunose. 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: