2 sec in total
626 ms
1.1 sec
248 ms
Visit yeoldarmory.com now to see the best up-to-date Yeoldarmory content and also check out these interesting facts you probably never knew about yeoldarmory.com
Ye Old Store of War
Visit yeoldarmory.comWe analyzed Yeoldarmory.com page load time and found that the first response time was 626 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
yeoldarmory.com performance score
626 ms
163 ms
111 ms
81 ms
116 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 97% of them (61 requests) were addressed to the original Yeoldarmory.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (626 ms) belongs to the original domain Yeoldarmory.com.
Page size can be reduced by 428.2 kB (45%)
958.7 kB
530.5 kB
In fact, the total size of Yeoldarmory.com main page is 958.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 447.5 kB which makes up the majority of the site volume.
Potential reduce by 52.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. 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 52.8 kB or 85% of the original size.
Potential reduce by 29.1 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. Yeoldarmory images are well optimized though.
Potential reduce by 161.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 161.8 kB or 69% of the original size.
Potential reduce by 184.5 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. Yeoldarmory.com needs all CSS files to be minified and compressed as it can save up to 184.5 kB or 86% of the original size.
Number of requests can be reduced by 22 (36%)
61
39
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yeoldarmory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
yeoldarmory.com
626 ms
style.css
163 ms
layout.css
111 ms
styles.css
81 ms
prettyPhoto.css
116 ms
jquery.js
183 ms
jquery-migrate.min.js
128 ms
third-party.js
147 ms
jquery.flexslider.min.js
149 ms
jquery.prettyPhoto.js
194 ms
general.js
193 ms
thickbox.css
193 ms
css
25 ms
red.css
198 ms
shortcodes.css
207 ms
custom.css
217 ms
wp-emoji-release.min.js
93 ms
ye_old_armory_sm.png
72 ms
14-225-400x500.jpg
98 ms
07-937-400x500.jpg
72 ms
38-614n-400x500.jpg
95 ms
38-7033-400x500.jpg
94 ms
22-1088_001-400x500.jpg
95 ms
22-523_001-300x300.jpg
96 ms
27-302D-200x250.jpg
95 ms
38-7017-200x250.jpg
111 ms
22-1040L-200x250.jpg
120 ms
22-1016g-150x150.jpg
134 ms
27-380-200x250.jpg
122 ms
22-4111G-200x250.jpg
123 ms
27-007-200x250.jpg
125 ms
27-191-200x250.jpg
158 ms
27-311D-200x250.jpg
171 ms
30-089-200x250.jpg
160 ms
22-108-200x250.jpg
171 ms
22-709-200x250.jpg
180 ms
06-184f-200x250.jpg
201 ms
04-541L-200x250.jpg
203 ms
07-411-200x250.jpg
205 ms
47-106l-200x250.jpg
207 ms
29-711_WEB_NEW-200x250.jpg
226 ms
22-7252-200x250.jpg
221 ms
07-859-200x250.jpg
245 ms
10-16AM-200x250.jpg
243 ms
04-558-200x250.jpg
240 ms
22-1111c-200x250.jpg
242 ms
22-28-200x250.jpg
261 ms
27-208-200x250.jpg
258 ms
ico-search.png
270 ms
logo_sm_mono.png
268 ms
2hig-tnMw8lXZsjwuh-9ow.ttf
40 ms
jquery.form.min.js
252 ms
scripts.js
215 ms
add-to-cart.min.js
240 ms
jquery.blockUI.min.js
246 ms
woocommerce.min.js
245 ms
jquery.cookie.min.js
224 ms
cart-fragments.min.js
221 ms
wp-embed.min.js
226 ms
bg-hatch.png
392 ms
ico-cart.png
391 ms
ico-tel.png
392 ms
arrow-superfish.png
55 ms
yeoldarmory.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yeoldarmory.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Yeoldarmory.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.
yeoldarmory.com
Open Graph data is detected on the main page of Yeoldarmory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: