8.7 sec in total
545 ms
7.5 sec
603 ms
Click here to check amazing Woodypuddy content for Japan. Otherwise, check out these important facts you probably never knew about woodypuddy.com
「あそびと暮らす」をコンセプトにおままごと、知育玩具の木製おもちゃブランド「ウッディプッディ」の直営オンラインショップです。
Visit woodypuddy.comWe analyzed Woodypuddy.com page load time and found that the first response time was 545 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
woodypuddy.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value6.7 s
8/100
25%
Value21.6 s
0/100
10%
Value2,550 ms
4/100
30%
Value0.202
61/100
15%
Value21.8 s
1/100
10%
545 ms
937 ms
1794 ms
519 ms
523 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 27% of them (43 requests) were addressed to the original Woodypuddy.com, 29% (46 requests) were made to C16.future-shop.jp and 18% (29 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source C16.future-shop.jp.
Page size can be reduced by 349.8 kB (14%)
2.6 MB
2.2 MB
In fact, the total size of Woodypuddy.com main page is 2.6 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.2 MB which makes up the majority of the site volume.
Potential reduce by 81.8 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. This page needs HTML code to be minified as it can gain 33.4 kB, which is 35% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 81.8 kB or 87% of the original size.
Potential reduce by 96.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. Woodypuddy images are well optimized though.
Potential reduce by 26.8 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 26.8 kB or 34% of the original size.
Potential reduce by 144.6 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. Woodypuddy.com needs all CSS files to be minified and compressed as it can save up to 144.6 kB or 87% of the original size.
Number of requests can be reduced by 53 (34%)
157
104
The browser has sent 157 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Woodypuddy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
woodypuddy.com
545 ms
www.woodypuddy.com
937 ms
set.css
1794 ms
r_system_preset.css
519 ms
system_DesignSettings.css
523 ms
system_SizeColorSettings.css
349 ms
system_LayoutSettings.css
358 ms
original.css
380 ms
jquery.min.js
33 ms
fs2api.js
1449 ms
ld.js
24 ms
poplink.css
555 ms
poplink.js
576 ms
default.css
407 ms
layout.css
556 ms
module.css
554 ms
base.css
971 ms
stylet.css
1282 ms
item_tmp.css
574 ms
dc.js
155 ms
536 ms
system_SizeColorSettings.css
345 ms
index.html
365 ms
newpink.gif
369 ms
calendar.html
364 ms
kanban_honten.jpg
1076 ms
top_nav-point.jpg
367 ms
point_sub-nav.jpg
371 ms
okaidoku.gif
1195 ms
ranking.jpg
1042 ms
sethazure.jpg
1046 ms
coping.jpg
1047 ms
member.jpg
1044 ms
ttl-s.jpg
1221 ms
search_b.jpg
1228 ms
LEFT_BUTTON_r1_c1.jpg
1574 ms
left_login.jpg
1232 ms
left_mypage.jpg
1250 ms
left_logout.jpg
1366 ms
top_mainbn_wrp.jpg
1580 ms
leftbn_pickup1.jpg
1991 ms
leftbn_mobile03.jpg
1769 ms
rare_set.jpg
1789 ms
rare_item.jpg
1884 ms
1448_thumbnail.jpg
1756 ms
1414_thumbnail.jpg
1943 ms
1257_thumbnail.jpg
1944 ms
1322_thumbnail.jpg
2143 ms
1416_thumbnail.jpg
1967 ms
bn415x150.jpg
2057 ms
gl-nav.jpg
1427 ms
leftbn_first.jpg
1076 ms
top_gut.jpg
1040 ms
top_new.jpg
1039 ms
leftbar_item.jpg
1041 ms
list_01.jpg
807 ms
top_mainbn_info.jpg
1248 ms
bar_newitem.jpg
1223 ms
bar_ninkiitem.jpg
1218 ms
36_thumbnail.jpg
1595 ms
945_thumbnail.jpg
1431 ms
231_thumbnail.jpg
1399 ms
1193_thumbnail.jpg
1589 ms
629_thumbnail.jpg
1437 ms
top_mainbn415_01.jpg
2137 ms
bar_03.jpg
1601 ms
36_3.jpg
1609 ms
tuduki_btn.png
1614 ms
231_1_expand.jpg
1957 ms
19_1_expand.jpg
1965 ms
29_1_expand.jpg
1779 ms
1_1.jpg
1788 ms
top_mainbn202_01.jpg
2006 ms
top_mainbn202_02.jpg
1958 ms
top_mainbn_annai.jpg
1966 ms
top_mainbn_kodawari.jpg
2324 ms
top_mainbn_wrp.jpg
2136 ms
top_mainbn_brandhid.jpg
2335 ms
footbar_infomation.jpg
2152 ms
foot_pay_ttl.jpg
2182 ms
visa.gif
2301 ms
mastercard.gif
2314 ms
jcb.gif
2332 ms
amex.gif
2359 ms
diners.gif
2477 ms
event
85 ms
event
369 ms
likebox.php
381 ms
__utm.gif
17 ms
bi.js
344 ms
reset.css
699 ms
common.css
1780 ms
jquery.min.js
18 ms
newpink.gif
1775 ms
jTuqQ-OPDr6.css
88 ms
n370yiaI2G6.css
103 ms
dbNRhrdsQao.css
121 ms
uzCGVqplqq-.css
137 ms
1-xIpmMldel.css
165 ms
cCIltMJutxu.css
156 ms
_rx8naC75Dy.js
213 ms
x5F9OMjKyLw.js
211 ms
ICDbTSzjQEg.js
144 ms
TTCre3391I0.js
152 ms
njO1TPvGzoR.js
210 ms
rFmE1g6Dkoz.js
272 ms
7cm7D75Y0Sf.js
262 ms
C-h3nYPqETO.js
257 ms
oRoBXlHCpEy.js
258 ms
336JejShbZp.js
260 ms
sj-JwAJi4AH.js
259 ms
DKRU1bYTkTw.js
261 ms
ZNPAadQNc33.js
264 ms
W0OV23mIOyO.js
266 ms
36TdwhIHusi.js
265 ms
b_6HNn_J2BZ.js
267 ms
551 ms
nissen.gif
2002 ms
11904703_1162180200464897_1415596262489089491_n.jpg
273 ms
safe_image.php
292 ms
10421208_1116326508383600_6931795422042342747_n.jpg
266 ms
12006352_132293883787980_7007831974251267437_n.jpg
276 ms
10959456_1563939620541187_3885015267362503808_n.jpg
326 ms
12112472_525067357660219_8431462957870279836_n.jpg
267 ms
11057347_10206093733734654_2018074965029138124_n.jpg
277 ms
1150859_280712205402410_296635440_n.jpg
277 ms
12718390_778074425670486_2417110697262344147_n.jpg
337 ms
582297_259291310867414_1209023522_n.jpg
297 ms
12240046_854403738011357_149893104272517803_n.jpg
287 ms
11227765_565956666889611_980004265800766665_n.jpg
288 ms
11990659_868900909858530_5397452190681885292_n.jpg
419 ms
12687985_1163040007042066_9172030753024030537_n.jpg
301 ms
12227565_763765450419111_8683004727316346079_n.jpg
301 ms
12191731_688681051269001_1792489698248798866_n.jpg
344 ms
12705557_1271345842881665_6553225978768094277_n.jpg
361 ms
12705654_1263803903635859_960787902224029266_n.jpg
457 ms
12670060_1259150987434484_42760741943415742_n.jpg
376 ms
12647156_1259151087434474_679221985361193529_n.jpg
404 ms
12644816_1257333227616260_1729755058526180734_n.jpg
441 ms
12654466_1257333244282925_2188183604013006865_n.jpg
442 ms
wL6VQj7Ab77.png
65 ms
s7jcwEQH7Sx.png
65 ms
QDwYpIaRyfG.png
65 ms
a-ZN6WoEOje.png
65 ms
foot_deli_ttl.jpg
1645 ms
pUFVdPjIRct.png
56 ms
foot_jikantai_ttl.jpg
1489 ms
foot_deli_time02.jpg
1493 ms
foot_order_ttl.jpg
1506 ms
foot_0120_ttl.jpg
1602 ms
foot_meyasu_ttl.jpg
1467 ms
foot_care_ttl.jpg
1478 ms
foot_re_ttl.jpg
1464 ms
I6-MnjEovm5.js
18 ms
vlXaquuXMrr.js
19 ms
ring10b.jpg
696 ms
gutsugutsubox.jpg
710 ms
g05-2080.jpg
367 ms
zukan_slide2.jpg
551 ms
partyset.jpg
533 ms
dis.aspx
368 ms
woodypuddy.com 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
button, link, and menuitem elements do not have accessible names.
[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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
woodypuddy.com 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
woodypuddy.com 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 Woodypuddy.com 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 Woodypuddy.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.
woodypuddy.com
Open Graph description is not detected on the main page of Woodypuddy. 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: