4.4 sec in total
963 ms
3 sec
446 ms
Click here to check amazing Sharedsorrows content for United States. Otherwise, check out these important facts you probably never knew about sharedsorrows.com
Funeral Planning - Funeral Pre-planning Guide for making funeral arrangements. Online funeral planning tools with funeral cost estimates - SharedSorrow.com
Visit sharedsorrows.comWe analyzed Sharedsorrows.com page load time and found that the first response time was 963 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
sharedsorrows.com performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value1.5 s
100/100
10%
Value120 ms
97/100
30%
Value0.202
61/100
15%
Value2.9 s
96/100
10%
963 ms
459 ms
175 ms
264 ms
177 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 83% of them (86 requests) were addressed to the original Sharedsorrows.com, 5% (5 requests) were made to Images-na.ssl-images-amazon.com and 3% (3 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Sharedsorrows.com.
Page size can be reduced by 1.2 MB (44%)
2.6 MB
1.5 MB
In fact, the total size of Sharedsorrows.com main page is 2.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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 36.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 5.1 kB, which is 11% 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 36.8 kB or 80% of the original size.
Potential reduce by 138.4 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. Obviously, Sharedsorrows needs image optimization as it can save up to 138.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 869.0 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 869.0 kB or 70% of the original size.
Potential reduce by 117.0 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. Sharedsorrows.com needs all CSS files to be minified and compressed as it can save up to 117.0 kB or 82% of the original size.
Number of requests can be reduced by 59 (59%)
100
41
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sharedsorrows. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
sharedsorrows.com
963 ms
PaymentWidgets.js
459 ms
home_new.css
175 ms
style.css
264 ms
menu.css
177 ms
planner.css
183 ms
obit_form.css
177 ms
planner_central_wp.css
188 ms
eulogy_form_wp.css
218 ms
q-a-plus.css
228 ms
royalslider.css
228 ms
default.css
228 ms
wpbdp.css
231 ms
styles.css
262 ms
googlemaps.css
270 ms
wpbdp-ratings.css
278 ms
styles.css
278 ms
style.css
284 ms
front.css
307 ms
jquery.js
393 ms
jquery-migrate.min.js
316 ms
royal-slider-7.0.min.js
322 ms
jquery.easing.1.3.min.js
323 ms
comment-reply.min.js
329 ms
js
88 ms
googlemaps.js
352 ms
wpbdp.js
363 ms
jquery.raty.min.js
358 ms
wpbdp-ratings.js
354 ms
jquery.cycle.all.2.72.js
990 ms
api.js
83 ms
style.css
385 ms
script.js
395 ms
grief.js
401 ms
tabs.js
405 ms
jquery.cycle.all.2.72.js
430 ms
internalNew.css
88 ms
forms.css
98 ms
blog.css
107 ms
qm.js
432 ms
qm_pure_css.js
476 ms
qm_round_corners.js
477 ms
qm_round_items.js
477 ms
functions.js
340 ms
printVersion.js
335 ms
clergy_contribute.js
439 ms
plannerFunctionality.js
435 ms
q-a-plus.js
429 ms
jquery.form.min.js
401 ms
scripts.js
391 ms
frontend.js
391 ms
categories-module.js
391 ms
jquery-1.4.2.min.js
74 ms
PaymentWidgets_core._V1447951220_.js
85 ms
common.js
53 ms
util.js
89 ms
geocoder.js
110 ms
recaptcha__en.js
102 ms
ga.js
89 ms
close-button.png
76 ms
body-bg.jpg
157 ms
donate.jpg
159 ms
feedback.jpg
152 ms
Providers-Tab.png
154 ms
header-bg-new.jpg
157 ms
logo-new1.png
358 ms
login-new.png
258 ms
back-trans.png
261 ms
border_repeat.png
262 ms
GooglePlusButtons.png
350 ms
FaceBookButtons.png
347 ms
LinkedInButtons.png
353 ms
YouTubeButtons.png
352 ms
TwitterButtons.png
352 ms
Flowers.png
348 ms
Urns1.png
259 ms
Keepsakes.png
260 ms
CareFund1.png
256 ms
Legal_202x116.png
346 ms
Chairs202x1161.png
353 ms
FH202x1161.png
349 ms
Bridge202x116.png
391 ms
search-icon.gif
352 ms
blank.gif
1049 ms
feature-product-left-back.png
297 ms
controls-sprite.png
318 ms
more-info.png
316 ms
feature-product-right-back.png
247 ms
hospital-icon.png
257 ms
icon2.png
265 ms
icon3.png
300 ms
__utm.gif
68 ms
jsonp
374 ms
widgets
394 ms
grab.png
101 ms
controls-sprite.png
103 ms
Resources2.png
305 ms
preloader.gif
124 ms
clear.gif
101 ms
Planning2.png
195 ms
jquery-1.4.2.min._CB199267522_.js
10 ms
jQuery-UI._CB191420144_.js
13 ms
cba_checkout._CB331011687_.js
27 ms
sharedsorrows.com accessibility score
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
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.
sharedsorrows.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
sharedsorrows.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sharedsorrows.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 Sharedsorrows.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.
sharedsorrows.com
Open Graph description is not detected on the main page of Sharedsorrows. 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: