Tools & Wizards About Us

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

grieving.com

Grieving.com Support for All Loss & Grief Types

Page Load Speed

3.6 sec in total

First Response

114 ms

Resources Loaded

3 sec

Page Rendered

510 ms

About Website

Welcome to grieving.com homepage info - get ready to check Grieving best content for United States right away, or after learning these important things about grieving.com

Grieving.com is a community of grieving people supporting other grieving people. All loss types (child, parent, mate, grandparent, brother, son, pet, hospice etc) welcomed with no judgements. People f...

Visit grieving.com

Key Findings

We analyzed Grieving.com page load time and found that the first response time was 114 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.

Performance Metrics

grieving.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

grieving.com

114 ms

forums.grieving.com

663 ms

341e4a57816af3ba440d891ca87450ff_framework.css.3937cf230d43483c660aaaf3bc666217.css

72 ms

05e81b71abe4f22d6eb8d1a929494829_responsive.css.4d261c6a8afa5fd476f72a063c13bdb6.css

89 ms

90eb5adf50a8c640f633d47fd7eb1778_core.css.b9e1fa75c34f6705050e07bd110d7794.css

96 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 46% of them (24 requests) were addressed to the original Grieving.com, 50% (26 requests) were made to Forums.grieving.com and 4% (2 requests) were made to Paypalobjects.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Forums.grieving.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 604.8 kB (73%)

Content Size

826.2 kB

After Optimization

221.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Grieving.com main page is 826.2 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. 15% of websites need less resources to load. Javascripts take 383.4 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 112.0 kB

  • Original 126.8 kB
  • After minification 113.8 kB
  • After compression 14.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 112.0 kB or 88% of the original size.

Image Optimization

-10%

Potential reduce by 4.2 kB

  • Original 40.5 kB
  • After minification 36.3 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. Grieving images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 261.6 kB

  • Original 383.4 kB
  • After minification 382.7 kB
  • After compression 121.8 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 261.6 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 227.0 kB

  • Original 275.5 kB
  • After minification 268.3 kB
  • After compression 48.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. Grieving.com needs all CSS files to be minified and compressed as it can save up to 227.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (52%)

Requests Now

25

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grieving. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

grieving.com accessibility score

74

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

grieving.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grieving.com 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 Grieving.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Grieving. 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: