57.5 sec in total
165 ms
38.5 sec
18.9 sec
Visit legacy.com now to see the best up-to-date Legacy content for United States and also check out these interesting facts you probably never knew about legacy.com
Legacy.com features obituaries from nearly 10,000 newspaper and funeral home partners from around the US. Publish your obituary with any of our 2,700+ newspaper partners and create a lasting memorial ...
Visit legacy.comWe analyzed Legacy.com page load time and found that the first response time was 165 ms and then it took 57.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
legacy.com performance score
165 ms
455 ms
110 ms
1717 ms
1175 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 29% of them (20 requests) were addressed to the original Legacy.com, 26% (18 requests) were made to Static-cms.legacy.com and 15% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (12.5 sec) relates to the external source A1625899514.cdn.optimizely.com.
Page size can be reduced by 5.0 MB (58%)
8.6 MB
3.6 MB
In fact, the total size of Legacy.com main page is 8.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 5.2 MB which makes up the majority of the site volume.
Potential reduce by 116.0 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 116.0 kB or 71% of the original size.
Potential reduce by 2.6 MB
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. Obviously, Legacy needs image optimization as it can save up to 2.6 MB or 49% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.2 MB
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 2.2 MB or 73% of the original size.
Potential reduce by 143.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. Legacy.com needs all CSS files to be minified and compressed as it can save up to 143.5 kB or 83% of the original size.
Number of requests can be reduced by 17 (30%)
56
39
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legacy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
legacy.com
165 ms
www.legacy.com
455 ms
styles.252e5eb37c7eb134f7a1ebea5e0e51ce.css
110 ms
1736730124.js
1717 ms
vendor.002b4d515879f34e8651.js
1175 ms
app.41353c7ac8bb4b1c28b1.js
1175 ms
platform.js
1456 ms
pinit.js
1331 ms
api.js
1612 ms
event
7861 ms
a1625899514.html
12538 ms
houston_sunset_-_gettyimages-675795803_-_1280x350_0.jpg
7213 ms
asbury-park-press-obituaries__r3uT2.jpeg
7252 ms
hartford-courant-obituaries__2oi0d.png
7211 ms
the-advocate-obituaries__1y-PQ.jpg
7161 ms
chicago-sun-times-obituaries__3chNi.jpeg
7161 ms
the-birmingham-news-obituaries__1Rcwl.png
7161 ms
the-buffalo-news-obituaries__1z1JC.png
6901 ms
Jumbotron-Cityscape-Rosa-Parks-1280x300__2nhS0.jpg
7308 ms
look_up_map__2cq6x.gif
7307 ms
Jumbotron-Starry-Sky-Gandi-1280x300__3FlBi.jpg
7308 ms
steely-hero.jpg
7159 ms
loss-parent-crop.jpg
7122 ms
mother-teresa-hero-getty_0.jpg
7121 ms
overdose-tree_1600x500.png
6898 ms
jerry_lewis_getty_hero.jpg
7121 ms
hobert_nelson_200x200.jpg
7306 ms
ned-garver.png
7307 ms
danerbalcon1.jpg
7306 ms
bobsheridan.jpg
7306 ms
victor_segura_200x200.jpg
7304 ms
hutchinson.jpg
7243 ms
ashbery-hero.jpg
7587 ms
becker-hero_0.jpg
7554 ms
shelley_berman_1600x500.jpg
7555 ms
randerson-hero_0.jpg
7587 ms
massimino-hero.jpg
7553 ms
houston_sunset_-_gettyimages-675795803_-_1600x500.jpg
7553 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
2311 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
6787 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
7194 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
7194 ms
gtm.js
6764 ms
3IFMwfRa07i-auYR-B-zNYnF5uFdDttMLvmWuJdhhgs.ttf
1422 ms
rEy5tGc5HdXy56Xvd4f3I1FZMcfX2SbzQ69I7OWmkGo.ttf
2121 ms
rEy5tGc5HdXy56Xvd4f3I306qf9KHRHwsVx7iw5MXmY.ttf
1405 ms
a5QZnvmn5amyNI-t2BMkWCtfYakCkPqOMDce0h_3gD8.ttf
1753 ms
4j4TR-EfnvCt43InYpUNDDolfeppZzFSKvLyJNPKLMk.ttf
1948 ms
4j4TR-EfnvCt43InYpUNDCxQL91WRy8t8mPvAX_dIgA.ttf
2004 ms
quant.js
418 ms
beacon.js
290 ms
analytics.js
87 ms
1664607.js
1105 ms
legacy.js
1104 ms
rules-p-57OGVHgSOoedo.js
1406 ms
linkid.js
1229 ms
json
4652 ms
sdk.js
4453 ms
recaptcha__en.js
4503 ms
widgets.js
3984 ms
the-arizona-republic-obituaries__2Peh8.jpeg
1912 ms
event
510 ms
northjersey-dot-com-obituaries__1qt4d.jpeg
678 ms
dallas-morning-news-obituaries__2J7tQ.png
830 ms
savannah_morning_news__22onh.png
831 ms
the-salt-lake-tribune-obituaries__3KUtq.png
831 ms
News_and_Observer__FRpY1.jpg
631 ms
1326221fae87240d35cc7d37cdf204d5
301 ms
legacy.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Legacy.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Legacy.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.com
Open Graph description is not detected on the main page of Legacy. 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: