3.9 sec in total
740 ms
3 sec
153 ms
Welcome to matsukawaya.jp homepage info - get ready to check Matsukawaya best content right away, or after learning these important things about matsukawaya.jp
松河屋老舗は文久二年に創業された御菓子所です。
Visit matsukawaya.jpWe analyzed Matsukawaya.jp page load time and found that the first response time was 740 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
matsukawaya.jp performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value14.2 s
0/100
25%
Value12.2 s
3/100
10%
Value350 ms
73/100
30%
Value0
100/100
15%
Value10.9 s
21/100
10%
740 ms
522 ms
535 ms
35 ms
55 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 51% of them (46 requests) were addressed to the original Matsukawaya.jp, 16% (14 requests) were made to O.twimg.com and 9% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Matsukawaya.jp.
Page size can be reduced by 104.9 kB (14%)
742.3 kB
637.4 kB
In fact, the total size of Matsukawaya.jp main page is 742.3 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. 65% of websites need less resources to load. Images take 635.5 kB which makes up the majority of the site volume.
Potential reduce by 16.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 16.1 kB or 70% of the original size.
Potential reduce by 21.7 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. Matsukawaya images are well optimized though.
Potential reduce by 23.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 23.7 kB or 74% of the original size.
Potential reduce by 43.4 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. Matsukawaya.jp needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 84% of the original size.
Number of requests can be reduced by 27 (31%)
88
61
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Matsukawaya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
matsukawaya.jp
740 ms
common.css
522 ms
swfobject_modified.js
535 ms
all.js
35 ms
plusone.js
55 ms
widgets.js
88 ms
clearfix.css
175 ms
text.css
181 ms
navi.css
194 ms
cb=gapi.loaded_0
48 ms
s1358997579.gif
1051 ms
top_bg.jpg
197 ms
flash.jpg
694 ms
ft_bt04.gif
362 ms
top_bar2.gif
201 ms
navi_m01.gif
355 ms
navi0101.gif
361 ms
navi0102.gif
722 ms
navi0103.gif
745 ms
navi0104.gif
882 ms
navi0105.gif
582 ms
navi0106.gif
582 ms
navi_m04.gif
762 ms
navi0401.gif
762 ms
navi0402.gif
865 ms
navi0403.gif
900 ms
navi0404.gif
926 ms
navi0405.gif
941 ms
navi_freedial.gif
941 ms
navi_m03.gif
1038 ms
navi0301.gif
1057 ms
navi0307.gif
1080 ms
navi0308.gif
1110 ms
navi0302.gif
1121 ms
navi0303.gif
1122 ms
navi0304.gif
1210 ms
navi0305.gif
1232 ms
navi0306.gif
1257 ms
navi_m02.gif
1293 ms
navi0201.gif
1300 ms
navi0202.gif
1300 ms
navi0203.gif
1386 ms
top_news.gif
1407 ms
news01.jpg
1615 ms
pagetop.gif
1476 ms
97 ms
bnr_blog.jpg
1625 ms
google.gif
1448 ms
xd_arbiter.php
75 ms
xd_arbiter.php
98 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
161 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
186 ms
cb=gapi.loaded_1
30 ms
fastbutton
93 ms
postmessageRelay
61 ms
like.php
75 ms
cb=gapi.loaded_0
17 ms
cb=gapi.loaded_1
17 ms
3193398744-postmessagerelay.js
32 ms
rpc:shindig_random.js
31 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
46 ms
ft_bt01.gif
1365 ms
ft_bt02.gif
1387 ms
wy1X4hBW7e7.js
39 ms
LVx-xkvaJ0b.png
47 ms
cb=gapi.loaded_0
3 ms
syndication
119 ms
345740735687061504
165 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
52 ms
ft_bt03.gif
1314 ms
proxy.jpg
201 ms
proxy.jpg
315 ms
proxy.jpg
394 ms
proxy.jpg
360 ms
proxy.jpg
376 ms
proxy.jpg
373 ms
proxy.jpg
386 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
30 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
56 ms
260_02_normal.jpg
193 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
24 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
83 ms
proxy.jpg
199 ms
proxy.jpg
259 ms
proxy.jpg
235 ms
proxy.jpg
226 ms
proxy.jpg
204 ms
proxy.jpg
176 ms
proxy.jpg
192 ms
jot.html
26 ms
matsukawaya.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.
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.
matsukawaya.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
Page has valid source maps
matsukawaya.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 Matsukawaya.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 Matsukawaya.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.
matsukawaya.jp
Open Graph description is not detected on the main page of Matsukawaya. 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: