4.9 sec in total
40 ms
4.3 sec
541 ms
Welcome to legacy-collectibles.com homepage info - get ready to check Legacy Collectibles best content for United States right away, or after learning these important things about legacy-collectibles.com
We are Civil War, World War 1, and World War 2 collectors who take pride in providing great prices on unique military collectibles. Buy yours online today.
Visit legacy-collectibles.comWe analyzed Legacy-collectibles.com page load time and found that the first response time was 40 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
legacy-collectibles.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value29.0 s
0/100
25%
Value11.7 s
4/100
10%
Value1,840 ms
9/100
30%
Value0.065
97/100
15%
Value32.7 s
0/100
10%
40 ms
50 ms
13 ms
27 ms
26 ms
Our browser made a total of 195 requests to load all elements on the main page. We found that 88% of them (172 requests) were addressed to the original Legacy-collectibles.com, 9% (18 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Legacy-collectibles.com.
Page size can be reduced by 922.9 kB (14%)
6.7 MB
5.8 MB
In fact, the total size of Legacy-collectibles.com main page is 6.7 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. Only a small number of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 333.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 149.7 kB, which is 42% 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 333.8 kB or 94% of the original size.
Potential reduce by 57.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. Legacy Collectibles images are well optimized though.
Potential reduce by 523.1 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 523.1 kB or 19% of the original size.
Potential reduce by 8.3 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. Legacy-collectibles.com has all CSS files already compressed.
Number of requests can be reduced by 139 (82%)
169
30
The browser has sent 169 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legacy Collectibles. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 114 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
legacy-collectibles.com
40 ms
www.legacy-collectibles.com
50 ms
calendar.css
13 ms
styles-m.css
27 ms
owl.carousel.css
26 ms
jquery.fancybox.css
26 ms
porto-icons-codes.css
24 ms
simple-line-icons.css
24 ms
animation.css
53 ms
font-awesome.min.css
53 ms
custom.css
53 ms
amslick.min.css
51 ms
style.css
55 ms
owl.carousel.css
55 ms
blog-m.css
65 ms
blog-new.css
65 ms
blog-custom.css
65 ms
styles-l.css
58 ms
require.js
64 ms
mixins.js
63 ms
requirejs-config.js
77 ms
css
88 ms
js
124 ms
css
112 ms
css
163 ms
css
162 ms
bootstrap.optimized.min.css
81 ms
animate.optimized.css
73 ms
type11.css
73 ms
custom.css
75 ms
design_default.css
80 ms
settings_default.css
80 ms
default_0.js
192 ms
default_0_addition.js
81 ms
jquery.js
38 ms
common.js
32 ms
dataPost.js
31 ms
bootstrap.js
31 ms
app.js
13 ms
form-key-provider.js
55 ms
mage-translation-dictionary.js
54 ms
theme.js
53 ms
main.js
42 ms
bootstrap.js
42 ms
domReady.js
66 ms
template.js
66 ms
confirm.js
2596 ms
widget.js
67 ms
jquery-mixin.js
64 ms
shop_newsletter_popup.jpg
2540 ms
logo-popup_1.png
2536 ms
logo.png
2537 ms
img_transparent.png
2538 ms
20240729-img_2660.jpg
2541 ms
20240802-img_3946.jpg
2540 ms
20240801-img_3538.jpg
2557 ms
20240708-img_7401.jpg
2547 ms
banner1.jpg
2541 ms
banner2.jpg
2543 ms
banner3.jpg
2542 ms
banner4.jpg
2544 ms
banner5.jpg
2551 ms
banner6.jpg
2544 ms
gun-stories.jpg
2551 ms
gun_channel.jpg
2547 ms
cash-for-collectibles.jpg
2555 ms
american_express.png
2549 ms
discover.png
2552 ms
mastercard.png
2555 ms
visa.png
2552 ms
types.js
67 ms
layout.js
67 ms
jquery.cookie.js
67 ms
jquery.fancybox.js
66 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
97 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
101 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
192 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
193 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
199 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
196 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
196 ms
text.js
65 ms
underscore.js
65 ms
knockout.js
65 ms
knockout-es5.js
64 ms
wrapper.js
62 ms
apear.js
27 ms
smart-keyboard-handler.js
28 ms
mage.js
27 ms
jquery.lazyload.js
27 ms
scripts.js
28 ms
engine.js
30 ms
bootstrap.js
27 ms
observable_array.js
62 ms
bound-nodes.js
28 ms
version.js
119 ms
porto-icons.woff
120 ms
translate.js
116 ms
modal.js
117 ms
main.js
118 ms
registry.js
117 ms
cookie-wrapper.js
119 ms
js-translation.json
124 ms
console-logger.js
71 ms
animate.js
71 ms
knockout-repeat.js
68 ms
knockout-fast-foreach.js
69 ms
events.js
68 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
63 ms
opensans-400.woff
120 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
67 ms
opensans-300.woff
113 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
64 ms
opensans-600.woff
113 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
65 ms
opensans-700.woff
113 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
65 ms
renderer.js
54 ms
resizable.js
55 ms
i18n.js
57 ms
scope.js
96 ms
range.js
96 ms
mage-init.js
98 ms
keyboard.js
96 ms
optgroup.js
97 ms
after-render.js
98 ms
autoselect.js
98 ms
datepicker.js
99 ms
outer_click.js
100 ms
fadeVisible.js
100 ms
collapsible.js
99 ms
staticChecked.js
100 ms
simple-checked.js
100 ms
bind-html.js
99 ms
tooltip.js
100 ms
color-picker.js
99 ms
observable_source.js
62 ms
sw_megamenu.js
50 ms
owl.carousel.min.js
23 ms
modal-popup.html
23 ms
modal-slide.html
76 ms
modal-custom.html
22 ms
key-codes.js
20 ms
core.js
20 ms
z-index.js
20 ms
local.js
20 ms
js.cookie.js
70 ms
async.js
69 ms
arrays.js
75 ms
slider-bar.png
75 ms
compare.js
74 ms
misc.js
74 ms
objects.js
74 ms
strings.js
73 ms
template.js
74 ms
logger.js
75 ms
entry-factory.js
73 ms
console-output-handler.js
75 ms
formatter.js
76 ms
message-pool.js
73 ms
levels-pool.js
75 ms
logger-utils.js
76 ms
loader.js
75 ms
mfblogunveil.js
53 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
82 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf
83 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf
84 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf
83 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
91 ms
print.css
83 ms
tooltip.html
200 ms
spectrum.js
197 ms
tinycolor.js
199 ms
class.js
197 ms
moment.js
7 ms
slide04.jpg
99 ms
data.js
23 ms
disable-selection.js
24 ms
focusable.js
24 ms
form.js
24 ms
ie.js
24 ms
keycode.js
25 ms
labels.js
24 ms
jquery-patch.js
25 ms
plugin.js
25 ms
safe-active-element.js
25 ms
safe-blur.js
25 ms
scroll-parent.js
26 ms
tabbable.js
26 ms
unique-id.js
25 ms
dom-observer.js
26 ms
bindings.js
26 ms
entry.js
26 ms
UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD8.ttf
159 ms
fontawesome-webfont.woff
158 ms
legacy-collectibles.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
[role]s do not have all required [aria-*] attributes
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
legacy-collectibles.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
legacy-collectibles.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Legacy-collectibles.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 Legacy-collectibles.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.
legacy-collectibles.com
Open Graph description is not detected on the main page of Legacy Collectibles. 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: