Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

dearly.com.au

Dearly Plaques & Memorials | Aluminium Markers | Cemetery Markers

Page Load Speed

19.4 sec in total

First Response

704 ms

Resources Loaded

18.3 sec

Page Rendered

397 ms

dearly.com.au screenshot

About Website

Welcome to dearly.com.au homepage info - get ready to check Dearly best content right away, or after learning these important things about dearly.com.au

Originally designed as interim grave markers, Dearly Plaques & Memorials has grown to provide a variety of attractive markers for all types of outdoor situations.

Visit dearly.com.au

Key Findings

We analyzed Dearly.com.au page load time and found that the first response time was 704 ms and then it took 18.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

dearly.com.au performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value18.9 s

0/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

dearly.com.au

704 ms

dearly.com.au

11717 ms

wc-blocks-vendors-style.css

467 ms

wc-blocks-style.css

986 ms

woocommerce-layout.css

719 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 88% of them (42 requests) were addressed to the original Dearly.com.au, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (11.7 sec) belongs to the original domain Dearly.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 214.1 kB (6%)

Content Size

3.5 MB

After Optimization

3.3 MB

In fact, the total size of Dearly.com.au main page is 3.5 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. 50% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 112.2 kB

  • Original 151.0 kB
  • After minification 150.2 kB
  • After compression 38.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 112.2 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 22 B

  • Original 2.8 MB
  • After minification 2.8 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. Dearly images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 96.9 kB

  • Original 361.6 kB
  • After minification 357.1 kB
  • After compression 264.7 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 96.9 kB or 27% of the original size.

CSS Optimization

-4%

Potential reduce by 5.0 kB

  • Original 116.1 kB
  • After minification 116.1 kB
  • After compression 111.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. Dearly.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (53%)

Requests Now

40

After Optimization

19

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

Accessibility Review

dearly.com.au accessibility score

95

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible name

Best Practices

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

SEO Factors

dearly.com.au SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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 Dearly.com.au 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 Dearly.com.au 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 Dearly. 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: