3.6 sec in total
28 ms
2.9 sec
682 ms
Click here to check amazing Legacy Stories content for United States. Otherwise, check out these important facts you probably never knew about legacystories.org
Everything needed to build a digital legacy portfolio that can enrich your family for generations.
Visit legacystories.orgWe analyzed Legacystories.org page load time and found that the first response time was 28 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
legacystories.org performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value13.6 s
0/100
25%
Value13.0 s
2/100
10%
Value7,110 ms
0/100
30%
Value0.002
100/100
15%
Value19.1 s
3/100
10%
28 ms
471 ms
91 ms
120 ms
123 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 73% of them (77 requests) were addressed to the original Legacystories.org, 9% (10 requests) were made to Ws.sharethis.com and 6% (6 requests) were made to S3.mylivechat.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Legacystories.org.
Page size can be reduced by 702.4 kB (20%)
3.5 MB
2.8 MB
In fact, the total size of Legacystories.org main page is 3.5 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. 60% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 38.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. This page needs HTML code to be minified as it can gain 9.2 kB, which is 19% 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 38.9 kB or 80% of the original size.
Potential reduce by 286.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 Stories images are well optimized though.
Potential reduce by 272.6 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 272.6 kB or 63% of the original size.
Potential reduce by 104.2 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. Legacystories.org needs all CSS files to be minified and compressed as it can save up to 104.2 kB or 82% of the original size.
Number of requests can be reduced by 32 (31%)
103
71
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legacy Stories. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
legacystories.org
28 ms
www.legacystories.org
471 ms
system.css
91 ms
general.css
120 ms
styles.css
123 ms
coda-slider-wide.css
108 ms
nav.css
74 ms
coda-slider-2.0.css
83 ms
reset.css
143 ms
meanmenu.css
159 ms
typography2.php
251 ms
mootools-core.js
234 ms
core.js
201 ms
caption.js
188 ms
ajax_1.5.pack.js
215 ms
jquery-1.11.1.min.js
239 ms
jquery.meanmenu.js
240 ms
buttons.js
54 ms
chatinline.aspx
166 ms
system.css
179 ms
livechat.aspx
225 ms
bg-header.jpg
148 ms
legacy-Stories.png
150 ms
button_readmore.jpg
150 ms
create_account_icon.png
144 ms
arrow.png
145 ms
block_img01.jpg
146 ms
block_img02.jpg
171 ms
block_img03.jpg
173 ms
bg-body.jpg
184 ms
legacy-background.jpg
233 ms
underline.jpg
220 ms
block_img01.jpg
218 ms
block_img02.jpg
236 ms
block_img03.jpg
307 ms
aaps_image01.png
307 ms
aaps_image02.png
322 ms
family_tree.png
321 ms
tool_chest.png
333 ms
be-a-provider.png
312 ms
conicerge.png
317 ms
request-a-bid.png
326 ms
legacy-shop.png
392 ms
visit.png
384 ms
aph.png
424 ms
I-ASK-Horizontal.jpg
424 ms
naepc-logo.png
408 ms
planned-giving.png
434 ms
ins-webx.png
467 ms
goodson-manley.png
465 ms
carrier.png
496 ms
anderson.png
540 ms
sowards.png
534 ms
ir-logo.jpg
612 ms
aaronmiller.png
580 ms
provider.png
579 ms
ford-health.png
578 ms
jsml.js
79 ms
getAllAppDefault.esi
32 ms
iseniorsolutions.png
444 ms
legacyhomecare.png
468 ms
sunlight-support.png
511 ms
comfortkeepers.png
511 ms
homecare.png
514 ms
visiting-angels.png
520 ms
resources.aspx
80 ms
amada.png
525 ms
dementia-logo.png
513 ms
getSegment.php
291 ms
cherished-memory.png
560 ms
picturesproseandprint.png
506 ms
preserving-life-stories.png
516 ms
photomemory4you.png
508 ms
myhistorian.png
514 ms
inpage_4_exit.png
36 ms
inpage_4_down.png
47 ms
inpage_4_offline.png
82 ms
savinghistory.png
455 ms
marjorieturner.png
472 ms
icon-FB.png
532 ms
icon-TW.png
536 ms
youtube_logo.png
527 ms
index.php
1701 ms
footer_background.jpg
533 ms
list-ico.png
503 ms
t.dhj
33 ms
t.dhj
13 ms
hbpix
168 ms
cm
78 ms
x35248
148 ms
s-3271.xgi
16 ms
28 ms
xrefid.xgi
3 ms
29 ms
23064
30 ms
index.html
32 ms
buttons-secure.css
15 ms
sharethis_16.png
19 ms
facebook_16.png
11 ms
twitter_16.png
11 ms
linkedin_16.png
13 ms
email_16.png
16 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
7 ms
st.1188278743c14064d5e8ae56c8ada29c.js
10 ms
icon-FB-hover.png
37 ms
icon-TW-hover.png
27 ms
legacystories.org 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
ARIA input fields do not have accessible names
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
legacystories.org 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
Missing source maps for large first-party JavaScript
legacystories.org 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 Legacystories.org 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 Legacystories.org 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.
legacystories.org
Open Graph description is not detected on the main page of Legacy Stories. 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: