9.6 sec in total
879 ms
8.4 sec
311 ms
Click here to check amazing Puccho content for Japan. Otherwise, check out these important facts you probably never knew about puccho.jp
ようこそ!ぷっちょワールドへ! UHA味覚糖ぷっちょの公式ホームページだよ
Visit puccho.jpWe analyzed Puccho.jp page load time and found that the first response time was 879 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
puccho.jp performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value5.4 s
19/100
25%
Value5.3 s
57/100
10%
Value60 ms
100/100
30%
Value0.013
100/100
15%
Value4.1 s
87/100
10%
879 ms
333 ms
501 ms
339 ms
345 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 90% of them (85 requests) were addressed to the original Puccho.jp, 4% (4 requests) were made to Google-analytics.com and 2% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Puccho.jp.
Page size can be reduced by 59.7 kB (5%)
1.2 MB
1.2 MB
In fact, the total size of Puccho.jp main page is 1.2 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 16.3 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.3 kB or 77% of the original size.
Potential reduce by 29.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. Puccho images are well optimized though.
Potential reduce by 5.5 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 5.5 kB or 11% of the original size.
Potential reduce by 8.0 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. Puccho.jp needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 74% of the original size.
Number of requests can be reduced by 25 (27%)
92
67
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puccho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
puccho.jp
879 ms
styles.css
333 ms
top.css
501 ms
topslide1.css
339 ms
os.js
345 ms
jsapi
16 ms
jquery.featureList-1.0.0.js
363 ms
slide1.js
669 ms
slide2.js
697 ms
reset.css
384 ms
basestyle.css
377 ms
ie6.css
374 ms
urchin.js
9 ms
conversion.js
22 ms
jquery.min.js
5 ms
ga.js
77 ms
background_img.jpg
167 ms
top_img.jpg
835 ms
logo.jpg
499 ms
menu1.jpg
350 ms
menu2.jpg
364 ms
menu3.jpg
378 ms
menu4.jpg
504 ms
menu5.jpg
715 ms
menu6.jpg
725 ms
menu7.jpg
753 ms
menu8.jpg
831 ms
pucho_hp.gif
835 ms
contact.gif
1077 ms
twitter_bt.png
1261 ms
bunner_bt2.png
1334 ms
slide1bk.jpg
1331 ms
slide1_menu1.png
1175 ms
slide1_menu2.png
1177 ms
slide1_menu3.png
1408 ms
slide2_201603_4.jpg
2338 ms
slide2_201603_1.jpg
2213 ms
slide2_201603_2.jpg
2159 ms
slide1_l_waku1.gif
1662 ms
slide1_l_waku3.gif
1726 ms
slide1_l_waku2.gif
1738 ms
slide_201603.jpg
2735 ms
slide1_waku_r.gif
2078 ms
2_back.jpg
2311 ms
puccho_set.gif
2426 ms
ironnapucho108.png
3154 ms
ironnapucho109.png
3082 ms
ironnapucho110.png
3224 ms
ironnapucho70.png
3230 ms
ironnapucho83.png
3342 ms
ironnapucho37.png
3564 ms
ironnapucho36.png
3993 ms
64 ms
__utm.gif
27 ms
__utm.gif
15 ms
32 ms
ironnapucho85.png
3916 ms
ironnapucho94.png
3975 ms
ironnapucho82.png
3851 ms
ironnapucho84.png
4085 ms
ironnapucho81.png
4247 ms
puccho_travel.gif
3846 ms
travel.png
3693 ms
msg.png
4029 ms
scenery.jpg
4106 ms
tree.png
3866 ms
chara.gif
4404 ms
waku.png
3969 ms
contents_title.gif
3987 ms
contents1.jpg
4235 ms
contents2.jpg
4238 ms
contents3.jpg
4257 ms
contents4.jpg
4192 ms
info_new.gif
4076 ms
star.gif
4198 ms
new.gif
4100 ms
mobile_1.jpg
4228 ms
mobile_2.jpg
4606 ms
satelite.gif
3772 ms
footer_bk.jpg
3909 ms
footerimg.jpg
3910 ms
anime1.gif
3810 ms
anime2.gif
4068 ms
anime3.gif
3869 ms
anime4.gif
3664 ms
sun.gif
3371 ms
anime5.gif
3800 ms
anime6.gif
3608 ms
cloud.png
3444 ms
plane.gif
3565 ms
attention.gif
3173 ms
uha.gif
2793 ms
slide1_menubk.gif
2941 ms
arrow.gif
2895 ms
puccho.jp accessibility score
puccho.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
puccho.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puccho.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 Puccho.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
puccho.jp
Open Graph description is not detected on the main page of Puccho. 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: