5.9 sec in total
101 ms
5.3 sec
450 ms
Click here to check amazing Jon Wye content. Otherwise, check out these important facts you probably never knew about jonwye.com
Artist-driven handmade graphic leather belts, t-shirts, wallets, and now Pirate Chef series apparel from Jon Wye.
Visit jonwye.comWe analyzed Jonwye.com page load time and found that the first response time was 101 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
jonwye.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value21.2 s
0/100
25%
Value9.5 s
12/100
10%
Value370 ms
71/100
30%
Value0.372
28/100
15%
Value21.7 s
1/100
10%
101 ms
35 ms
97 ms
28 ms
107 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 96% of them (141 requests) were addressed to the original Jonwye.com, 1% (2 requests) were made to Use.typekit.net and 1% (2 requests) were made to D3e1rqjpcan0d2.cloudfront.net. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Jonwye.com.
Page size can be reduced by 223.8 kB (5%)
4.1 MB
3.9 MB
In fact, the total size of Jonwye.com main page is 4.1 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. 75% 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 3.6 MB which makes up the majority of the site volume.
Potential reduce by 62.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 62.3 kB or 84% of the original size.
Potential reduce by 68.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. Jon Wye images are well optimized though.
Potential reduce by 91.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 91.7 kB or 23% of the original size.
Potential reduce by 890 B
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. Jonwye.com has all CSS files already compressed.
Number of requests can be reduced by 120 (86%)
139
19
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jon Wye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 113 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
jonwye.com
101 ms
jonwye.com
35 ms
calendar.css
97 ms
styles-m.css
28 ms
custom.css
107 ms
vbcard.css
21 ms
wallets.css
20 ms
styles-l.css
115 ms
require.js
145 ms
mixins.js
44 ms
requirejs-config.js
44 ms
custom.js
58 ms
de4bbce83b4858531cd70b601.js
92 ms
email-decode.min.js
44 ms
ykg6ivs.css
131 ms
print.css
110 ms
p.css
42 ms
jon-wye-logo.png
102 ms
Wallets.jpg
54 ms
jonwye-home-banner.jpg
36 ms
home-clutch.jpg
186 ms
home-newest.jpg
39 ms
home-fred.jpg
38 ms
home-popular.jpg
40 ms
Guitar_Straps.jpg
59 ms
jquery.js
85 ms
common.js
42 ms
dataPost.js
37 ms
bootstrap.js
42 ms
search-icon.png
62 ms
app.js
144 ms
form-key-provider.js
61 ms
mage-translation-dictionary.js
60 ms
theme.js
68 ms
shopping-cart-icon.png
46 ms
opensans-400.woff
161 ms
opensans-300.woff
165 ms
opensans-600.woff
169 ms
opensans-700.woff
186 ms
d
23 ms
Luma-Icons.woff
217 ms
template.js
237 ms
confirm.js
159 ms
widget.js
160 ms
domReady.js
157 ms
main.js
170 ms
bootstrap.js
162 ms
twitter.png
259 ms
facebook.png
175 ms
jquery-mixin.js
258 ms
registry.js
161 ms
storage.js
165 ms
text.js
161 ms
url.js
166 ms
smart-keyboard-handler.js
167 ms
mage.js
174 ms
ie-class-fixer.js
179 ms
jquery-migrate.js
257 ms
types.js
107 ms
layout.js
207 ms
underscore.js
65 ms
translate.js
73 ms
modal.js
80 ms
version.js
79 ms
knockout.js
87 ms
knockout-es5.js
96 ms
engine.js
88 ms
bootstrap.js
784 ms
observable_array.js
88 ms
bound-nodes.js
1789 ms
scripts.js
91 ms
amazon-pay-config.js
93 ms
storage-wrapper.js
98 ms
js-translation.json
1768 ms
main.js
78 ms
modal-popup.html
2722 ms
modal-slide.html
2744 ms
modal-custom.html
2737 ms
key-codes.js
731 ms
core.js
739 ms
z-index.js
751 ms
wrapper.js
736 ms
observable_source.js
2707 ms
renderer.js
1696 ms
console-logger.js
3699 ms
js.storage.js
1690 ms
arrays.js
1789 ms
compare.js
1798 ms
misc.js
3677 ms
objects.js
2676 ms
strings.js
2686 ms
template.js
3682 ms
knockout-repeat.js
3028 ms
knockout-fast-foreach.js
2029 ms
resizable.js
2026 ms
i18n.js
2035 ms
scope.js
2038 ms
range.js
2043 ms
mage-init.js
2046 ms
keyboard.js
2051 ms
optgroup.js
2056 ms
after-render.js
2059 ms
autoselect.js
2066 ms
datepicker.js
2076 ms
outer_click.js
3708 ms
fadeVisible.js
2082 ms
collapsible.js
2090 ms
staticChecked.js
2098 ms
simple-checked.js
2109 ms
bind-html.js
2119 ms
tooltip.js
2127 ms
color-picker.js
2130 ms
data.js
2125 ms
disable-selection.js
1184 ms
focusable.js
1183 ms
form.js
1192 ms
ie.js
1194 ms
keycode.js
1091 ms
labels.js
1092 ms
jquery-patch.js
237 ms
plugin.js
232 ms
safe-active-element.js
241 ms
safe-blur.js
252 ms
scroll-parent.js
253 ms
tabbable.js
262 ms
unique-id.js
262 ms
events.js
268 ms
loader.js
271 ms
cookie-wrapper.js
280 ms
class.js
283 ms
async.js
294 ms
tooltip.html
230 ms
spectrum.js
227 ms
tinycolor.js
238 ms
js.cookie.js
90 ms
dom-observer.js
72 ms
bindings.js
80 ms
local.js
11 ms
logger.js
11 ms
entry-factory.js
12 ms
console-output-handler.js
15 ms
formatter.js
848 ms
message-pool.js
17 ms
levels-pool.js
20 ms
logger-utils.js
857 ms
entry.js
10 ms
moment.js
11 ms
jonwye.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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.
jonwye.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Issues were logged in the Issues panel in Chrome Devtools
jonwye.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jonwye.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 Jonwye.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.
jonwye.com
Open Graph description is not detected on the main page of Jon Wye. 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: