1.7 sec in total
130 ms
1.4 sec
184 ms
Visit intimeofsorrow.com now to see the best up-to-date Intimeofsorrow content for United States and also check out these interesting facts you probably never knew about intimeofsorrow.com
Find sympathy gifts and ideas at In Time of Sorrow. Offer comfort with bereavement and grief gifts for spouses, children, parents, siblings, and others.
Visit intimeofsorrow.comWe analyzed Intimeofsorrow.com page load time and found that the first response time was 130 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
intimeofsorrow.com performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value2.0 s
96/100
25%
Value2.0 s
99/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.0 s
99/100
10%
130 ms
48 ms
60 ms
56 ms
41 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 10% of them (6 requests) were addressed to the original Intimeofsorrow.com, 19% (11 requests) were made to Conversionsondemand.com and 15% (9 requests) were made to Ep.yimg.com. The less responsive or slowest element that took the longest time to load (548 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 511.7 kB (66%)
776.0 kB
264.3 kB
In fact, the total size of Intimeofsorrow.com main page is 776.0 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. 65% of websites need less resources to load. Javascripts take 585.7 kB which makes up the majority of the site volume.
Potential reduce by 42.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. 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 42.9 kB or 77% of the original size.
Potential reduce by 3.0 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. Intimeofsorrow images are well optimized though.
Potential reduce by 446.5 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 446.5 kB or 76% of the original size.
Potential reduce by 19.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. Intimeofsorrow.com needs all CSS files to be minified and compressed as it can save up to 19.2 kB or 78% of the original size.
Number of requests can be reduced by 35 (65%)
54
19
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intimeofsorrow. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.intimeofsorrow.com
130 ms
mobileredirector.js
48 ms
css-base.css
60 ms
css-element.css
56 ms
css-contents.css
41 ms
css-edits.css
71 ms
jquery.min.js
7 ms
jquery-ui.min.js
8 ms
jquery-ui.css
21 ms
ysw-accordion-nav-styles.css
32 ms
loader_536a99d.js
40 ms
view_webform.js
111 ms
ysw-accordion-nav-script.js
25 ms
ywa.js
51 ms
ysw-accordion-nav-script.js
23 ms
ysw-accordion-nav-styles.css
20 ms
img-39502.gif
58 ms
bbbsealh1US.gif
218 ms
twitter-a.png
65 ms
yhst-78133703087364_2267_71231400
43 ms
memorial-keepsake-gifts-49.gif
44 ms
garden-memorial-gifts-35.gif
46 ms
memorial-jewelry-59.gif
186 ms
sympathy-gift-baskets-64.gif
63 ms
plus-minus.gif
43 ms
css-base.css
61 ms
1458468747030___fc_yhst-78133703087364.js
69 ms
merchant.js
33 ms
cod-scripts-loader.js
76 ms
analytics.js
29 ms
gradient_top.png
23 ms
like.php
83 ms
collect
15 ms
ads
215 ms
combo
6 ms
combo
15 ms
cookieCheck_initial.js.php
33 ms
TY3MhkXpWJ-.js
481 ms
LVx-xkvaJ0b.png
548 ms
promo_manager_bui_a784667.js
8 ms
global_script.php
49 ms
cpers-3ab41d0.js
6 ms
promo_manager_bui_193214.css
41 ms
product
59 ms
sprite.png
27 ms
generate-fp2.php
20 ms
cod-services-loader.php
211 ms
561a10c0007c013264457a163e74bed5.gif
69 ms
ts
108 ms
thickbox.css
64 ms
hoverad.css
72 ms
thickbox.js
68 ms
nwevents-1.2.5-new.js
77 ms
nwmatcher-1.2.5-min-new.js
74 ms
loading.gif
13 ms
webform-out.js
28 ms
00ec633e8cbb46827bb29a384343fcf6
67 ms
recaptcha_ajax.js
16 ms
jquery.min.js
12 ms
intimeofsorrow.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
intimeofsorrow.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
intimeofsorrow.com SEO score
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intimeofsorrow.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Intimeofsorrow.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
intimeofsorrow.com
Open Graph description is not detected on the main page of Intimeofsorrow. 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: