3.8 sec in total
153 ms
3.5 sec
161 ms
Welcome to woodyjones.com homepage info - get ready to check WOODY JONES best content right away, or after learning these important things about woodyjones.com
Your story told by mechanical wooden sculptures (automata).Custom made and commentary scenes available.
Visit woodyjones.comWe analyzed Woodyjones.com page load time and found that the first response time was 153 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
woodyjones.com performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value5.4 s
21/100
25%
Value44.6 s
0/100
10%
Value127,120 ms
0/100
30%
Value0.52
15/100
15%
Value154.8 s
0/100
10%
153 ms
18 ms
34 ms
75 ms
9 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Woodyjones.com, 37% (38 requests) were made to Fonts.gstatic.com and 26% (27 requests) were made to Nebula.wsimg.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Nebula.wsimg.com.
Page size can be reduced by 1.3 MB (10%)
12.6 MB
11.3 MB
In fact, the total size of Woodyjones.com main page is 12.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 12.0 MB which makes up the majority of the site volume.
Potential reduce by 42.9 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 42.9 kB or 82% of the original size.
Potential reduce by 821.3 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. WOODY JONES images are well optimized though.
Potential reduce by 87.3 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 87.3 kB or 52% of the original size.
Potential reduce by 311.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. Woodyjones.com needs all CSS files to be minified and compressed as it can save up to 311.7 kB or 83% of the original size.
Number of requests can be reduced by 19 (31%)
62
43
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WOODY JONES. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.woodyjones.com
153 ms
css
18 ms
css
34 ms
site.css
75 ms
duel.js
9 ms
jq.js
72 ms
5fa1505430f385afce9c435c9da7c95c
19 ms
subNavigation.js
34 ms
social.share.js
16 ms
cookiemanager.js
14 ms
iebackground.js
19 ms
fbb4cc4d136f80f28a7fe3b2edd7526e
731 ms
018b8083d77d9c39739dca2e31df1b99
737 ms
44874ba1fe073fc9b13190e735136d65
741 ms
49db41613f0886490f22237cb472e4cd
739 ms
ab69ada85a2820613a7b77f85644990a
735 ms
88574ca2937a29fc02eda2f0dddb53d5
734 ms
3792426cc946c888548543c67363f456
732 ms
d3173ae3a4b09698935f8ae23f8561c4
894 ms
a7777a7ae6fa89884c3abdf4d3162e48
895 ms
a7536f17a72f2c3f45c79dbda9b8b99a
1325 ms
98f93bbf946612f14feddadfee34a1a5
1034 ms
aa21acd2bb627a2ab981d2e864874099
1040 ms
563219d9644f2d3ad5b755ca7d88555a
1329 ms
8d52f20208705e041a37e1c9c05fc5d9
1340 ms
c27d2092317c5c4dac37f6d04a8236aa
1328 ms
ef085025bfbf79156ff0b237b1a113a8
1328 ms
45088d0815792aad30839c61f40800ed
1339 ms
6ce4cd02e8a7b80895018aabd1176b37
1945 ms
107f064444e4681f9d31ef6192fa8361
1941 ms
632d06b0b1fda585554069652cf273a4
1945 ms
4703c91d58821f0f69048716c1dc9e03
1941 ms
ae50ff8ecff5a72d7e600f9ef71f3472
1942 ms
d544339378c484e4d2181f014e584932
1943 ms
bd490d9adb4e8b9ae3125feac6093387
2116 ms
43ab77aaf6915a24b607d89d101eaa83
2117 ms
e5bc11f9cb598206730da276ab22a899
2118 ms
util.window.js
8 ms
util.instances.js
7 ms
util.model.js
15 ms
helper.js
11 ms
pM4d8xtWPvg
82 ms
browser.js
26 ms
_vyghQC0IQ4
65 ms
k0MJYCmPpko
73 ms
sLnznD_3pr0
75 ms
qlSbyIcZ6Xk
67 ms
G6uia1qlU3I
76 ms
mrIU6_8jg50
635 ms
www-player.css
21 ms
www-embed-player.js
159 ms
base.js
221 ms
fetch-polyfill.js
71 ms
ad_status.js
370 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQUwaEQXjM.woff
217 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQUwaEQXjN_mQ.woff
358 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4vaVQUwaEQXjN_mQ.woff
354 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4iaVQUwaEQXjN_mQ.woff
361 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4jaVQUwaEQXjN_mQ.woff
362 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4saVQUwaEQXjN_mQ.woff
362 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQUwaEQXjN_mQ.woff
359 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVQUwaEQXjN_mQ.woff
363 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff
363 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQUwaEQXjN_mQ.woff
367 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4vaVQUwaEQXjN_mQ.woff
366 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4iaVQUwaEQXjN_mQ.woff
367 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4jaVQUwaEQXjN_mQ.woff
366 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4saVQUwaEQXjN_mQ.woff
369 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQUwaEQXjN_mQ.woff
369 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVQUwaEQXjN_mQ.woff
372 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQUwaEQXjM.woff
371 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQUwaEQXjN_mQ.woff
371 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4vaVQUwaEQXjN_mQ.woff
371 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4iaVQUwaEQXjN_mQ.woff
375 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4jaVQUwaEQXjN_mQ.woff
375 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4saVQUwaEQXjN_mQ.woff
641 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQUwaEQXjN_mQ.woff
641 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4taVQUwaEQXjN_mQ.woff
641 ms
qs_eGd-h9f3_frMeplByuCjrJjGTr5iyl3j-JE2Mo0s.js
508 ms
embed.js
157 ms
id
298 ms
Create
789 ms
Create
776 ms
Create
784 ms
Create
789 ms
Create
869 ms
Create
833 ms
Create
745 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
670 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
673 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
1341 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
1347 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
1352 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
1349 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
1348 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
1348 ms
KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff
1349 ms
KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff
1351 ms
KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff
1355 ms
KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff
1355 ms
KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff
1353 ms
KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff
1351 ms
woodyjones.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
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.
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.
woodyjones.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
Browser errors were logged to the console
Page has valid source maps
woodyjones.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Woodyjones.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Woodyjones.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.
woodyjones.com
Open Graph data is detected on the main page of WOODY JONES. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: