Tools & Wizards About Us

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

gravecard.com

Personalised Memorial Cards In Gift Box - Precious Thoughts Gravecard

Page Load Speed

7.6 sec in total

First Response

790 ms

Resources Loaded

6.3 sec

Page Rendered

563 ms

About Website

Click here to check amazing Gravecard content. Otherwise, check out these important facts you probably never knew about gravecard.com

Personalised waterproof memorial cards - We offer a range of cards for various occasions that include Anniversaries, Mothers Day, Fathers Day, Birthdays.

Visit gravecard.com

Key Findings

We analyzed Gravecard.com page load time and found that the first response time was 790 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

gravecard.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

gravecard.com

790 ms

css

34 ms

htn6k.css

83 ms

htn6k.css

162 ms

htn6k.css

230 ms

Our browser made a total of 222 requests to load all elements on the main page. We found that 97% of them (216 requests) were addressed to the original Gravecard.com, 1% (3 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (790 ms) belongs to the original domain Gravecard.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 462.7 kB (7%)

Content Size

6.6 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gravecard.com main page is 6.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. 80% 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.9 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 174.2 kB

  • Original 199.1 kB
  • After minification 197.5 kB
  • After compression 24.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 174.2 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 170.1 kB

  • Original 5.9 MB
  • After minification 5.7 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. Gravecard images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 65.1 kB

  • Original 271.1 kB
  • After minification 271.1 kB
  • After compression 206.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 65.1 kB or 24% of the original size.

CSS Optimization

-24%

Potential reduce by 53.3 kB

  • Original 219.0 kB
  • After minification 218.9 kB
  • After compression 165.7 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. Gravecard.com needs all CSS files to be minified and compressed as it can save up to 53.3 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 126 (58%)

Requests Now

217

After Optimization

91

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

gravecard.com accessibility score

90

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.

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

Best Practices

gravecard.com best practices score

92

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

SEO Factors

gravecard.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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 Gravecard.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 Gravecard.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 data is detected on the main page of Gravecard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: