Report Summary

  • 97

    Performance

    Renders faster than
    95% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

intimeofsorrow.com

Index of /

Page Load Speed

1.7 sec in total

First Response

130 ms

Resources Loaded

1.4 sec

Page Rendered

184 ms

intimeofsorrow.com screenshot

About Website

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.com

Key Findings

We 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.

Performance Metrics

intimeofsorrow.com performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

96/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

www.intimeofsorrow.com

130 ms

mobileredirector.js

48 ms

css-base.css

60 ms

css-element.css

56 ms

css-contents.css

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 Optimization Overview & Recommendations

Page size can be reduced by 511.7 kB (66%)

Content Size

776.0 kB

After Optimization

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.

HTML Optimization

-77%

Potential reduce by 42.9 kB

  • Original 55.6 kB
  • After minification 55.2 kB
  • After compression 12.7 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.

Image Optimization

-3%

Potential reduce by 3.0 kB

  • Original 110.0 kB
  • After minification 107.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.

JavaScript Optimization

-76%

Potential reduce by 446.5 kB

  • Original 585.7 kB
  • After minification 480.4 kB
  • After compression 139.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 446.5 kB or 76% of the original size.

CSS Optimization

-78%

Potential reduce by 19.2 kB

  • Original 24.7 kB
  • After minification 19.2 kB
  • After compression 5.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. 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.

Requests Breakdown

Number of requests can be reduced by 35 (65%)

Requests Now

54

After Optimization

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.

Accessibility Review

intimeofsorrow.com accessibility score

86

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

intimeofsorrow.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

intimeofsorrow.com SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: