11.8 sec in total
1.5 sec
9.6 sec
649 ms
Welcome to tsuge-kushi.com homepage info - get ready to check Tsuge Kushi best content for Japan right away, or after learning these important things about tsuge-kushi.com
大正八年、湯の街・別府で創業した別府つげ工芸。つげ櫛から始まった別府つげ工芸では、 初代より引き継がれている独自の彫刻技術と透かし彫りの技術を駆使し、つげブラシを製作しております。昔からの職人の思いとこだわりを胸に、職人が皆様に寄り添ったものづくりを目指し、日々製作に励んでおります。
Visit tsuge-kushi.comWe analyzed Tsuge-kushi.com page load time and found that the first response time was 1.5 sec and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tsuge-kushi.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value13.8 s
0/100
25%
Value11.8 s
4/100
10%
Value550 ms
54/100
30%
Value0.268
46/100
15%
Value10.5 s
23/100
10%
1495 ms
25 ms
1408 ms
345 ms
351 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 59% of them (82 requests) were addressed to the original Tsuge-kushi.com, 13% (18 requests) were made to Maps.googleapis.com and 10% (14 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Tsuge-kushi.com.
Page size can be reduced by 1.2 MB (27%)
4.4 MB
3.2 MB
In fact, the total size of Tsuge-kushi.com main page is 4.4 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. 70% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 34.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 34.7 kB or 78% of the original size.
Potential reduce by 73.4 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. Tsuge Kushi images are well optimized though.
Potential reduce by 715.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 715.1 kB or 70% of the original size.
Potential reduce by 362.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. Tsuge-kushi.com needs all CSS files to be minified and compressed as it can save up to 362.3 kB or 86% of the original size.
Number of requests can be reduced by 54 (42%)
129
75
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tsuge Kushi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
www.tsuge-kushi.com
1495 ms
font-awesome.min.css
25 ms
foundation.css
1408 ms
reset.css
345 ms
import.css
351 ms
usces_cart.css
880 ms
font-awesome.min.css
26 ms
foundation.min.js
771 ms
jquery.min.js
28 ms
style.css
504 ms
styles.css
513 ms
fancybox.css
724 ms
font-awesome.css
13 ms
functional.css
668 ms
admin-ajax.php
1153 ms
admin-ajax.php
1451 ms
usces_default.css
890 ms
usces_cart.css
1329 ms
usces_cart.css
1063 ms
jquery.js
1682 ms
jquery-migrate.min.js
1178 ms
jquery.fancybox.js
1591 ms
usces_cart.js
1180 ms
flexslider.css
1200 ms
public.css
1226 ms
style-light.css
1294 ms
jquery.form.min.js
1532 ms
scripts.js
1391 ms
scroll-back-to-top.js
1390 ms
wp-embed.min.js
1466 ms
jquery.flexslider-min.js
2381 ms
all.frontend.min.js
1832 ms
basic.css
1590 ms
style2.css
1634 ms
layout.css
1676 ms
styled.css
1704 ms
pages.css
1764 ms
analytics.js
41 ms
logo.jpg
529 ms
tel_oita.jpg
580 ms
tel_tokyo.jpg
354 ms
gnavi_01.jpg
180 ms
gnavi_02.jpg
181 ms
gnavi_03.jpg
344 ms
gnavi_04.jpg
347 ms
gnavi_05.jpg
515 ms
gnavi_06.jpg
520 ms
gnavi_07.jpg
711 ms
01.jpg
2391 ms
02.jpg
1761 ms
03.jpg
2743 ms
04.jpg
2202 ms
photo2_thum.jpg
971 ms
photo3_thum.jpg
1495 ms
photo4_thum.jpg
1497 ms
photo5_thum.jpg
1789 ms
photo6_thum.jpg
1763 ms
photo7_thum.jpg
2717 ms
photo8_thum.jpg
2113 ms
photo9_thum.jpg
2146 ms
photo1_thum.jpg
2585 ms
img_title01.png
2323 ms
btn_topnavi01.png
2395 ms
btn_topnavi02.png
2851 ms
btn_topnavi03.png
2562 ms
btn_topnavi04.png
3166 ms
img_title02.png
2734 ms
index_img_01.jpg
3579 ms
img_topabout01.png
2885 ms
img_topabout02.png
2904 ms
img_topabout03.png
3070 ms
wp-emoji-release.min.js
3716 ms
bg_footer.png
3023 ms
collect
22 ms
maps
90 ms
maps
118 ms
fontawesome-webfont.woff
11 ms
fontawesome-webfont.woff
11 ms
fontawesome-webfont.woff
10 ms
embed
502 ms
bg_f_maptxt2_01.png
3240 ms
bg_f_maptxt01.png
3190 ms
embed
512 ms
bnr_sidetitle.jpg
3062 ms
footerlogo.jpg
3789 ms
mine_botm2.png
3384 ms
loading-icon-128x128.gif
3221 ms
light-arrows.png
3073 ms
bg_top.jpg
4710 ms
bg_topabout.jpg
4726 ms
bg_footernavi.jpg
3230 ms
js
189 ms
init_embed.js
58 ms
bg_footernavi1.png
3203 ms
sidenavi.jpg
2933 ms
common.js
114 ms
map.js
176 ms
google4.png
130 ms
overlay.js
123 ms
util.js
195 ms
onion.js
192 ms
search_impl.js
192 ms
StaticMapService.GetMapImage
368 ms
StaticMapService.GetMapImage
666 ms
stats.js
49 ms
openhand_8_8.cur
37 ms
ViewportInfoService.GetViewportInfo
174 ms
ViewportInfoService.GetViewportInfo
167 ms
transparent.png
162 ms
kh
252 ms
ViewportInfoService.GetViewportInfo
196 ms
controls.js
78 ms
ViewportInfoService.GetViewportInfo
69 ms
kh
355 ms
bg_ico01.jpg
2572 ms
bg_direction_nav.png
2575 ms
vt
379 ms
css
251 ms
entity11.png
216 ms
vt
273 ms
vt
293 ms
vt
272 ms
vt
250 ms
ViewportInfoService.GetViewportInfo
134 ms
mapcnt6.png
127 ms
vt
224 ms
vt
237 ms
vt
275 ms
vt
248 ms
vt
220 ms
vt
270 ms
vt
310 ms
tmapctrl.png
59 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
74 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
100 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
98 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
98 ms
AuthenticationService.Authenticate
44 ms
AuthenticationService.Authenticate
15 ms
tsuge-kushi.com 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
tsuge-kushi.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
tsuge-kushi.com SEO score
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tsuge-kushi.com 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 Tsuge-kushi.com 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.
tsuge-kushi.com
Open Graph description is not detected on the main page of Tsuge Kushi. 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: