Tools & Wizards About Us
ediblegoldleaf.nz screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

ediblegoldleaf.nz

Edible Gold Leaf NZ | Gold Flakes, Gold Dust, Gold Crumps

Page Load Speed

7.9 sec in total

First Response

1.1 sec

Resources Loaded

6.6 sec

Page Rendered

173 ms

ediblegoldleaf.nz screenshot

About Website

Visit ediblegoldleaf.nz now to see the best up-to-date Edible Gold Leaf content and also check out these interesting facts you probably never knew about ediblegoldleaf.nz

Visit ediblegoldleaf.nz

Key Findings

We analyzed Ediblegoldleaf.nz page load time and found that the first response time was 1.1 sec 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

ediblegoldleaf.nz performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value20.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,430 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.289

42/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

ediblegoldleaf.nz

1092 ms

bh4be.css

642 ms

bh4be.css

442 ms

bh4bg.css

1094 ms

js

136 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 62% of them (38 requests) were addressed to the original Ediblegoldleaf.nz, 15% (9 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Ediblegoldleaf.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.2 kB (15%)

Content Size

889.1 kB

After Optimization

756.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ediblegoldleaf.nz main page is 889.1 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. 70% of websites need less resources to load. Javascripts take 401.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 128.5 kB

  • Original 152.6 kB
  • After minification 152.1 kB
  • After compression 24.2 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 128.5 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 152.1 kB
  • After minification 152.1 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. Edible Gold Leaf images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.5 kB

  • Original 401.2 kB
  • After minification 401.2 kB
  • After compression 398.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 1.3 kB

  • Original 183.1 kB
  • After minification 183.1 kB
  • After compression 181.9 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. Ediblegoldleaf.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (76%)

Requests Now

49

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ediblegoldleaf.nz

ediblegoldleaf.nz

1092 ms

bh4be.css

bh4be.css

642 ms

bh4be.css

bh4be.css

442 ms

bh4bg.css

bh4bg.css

1094 ms

js

js

136 ms

api.js

api.js

104 ms

bh4bf.js

bh4bf.js

887 ms

bh4be.js

bh4be.js

669 ms

bh4be.js

bh4be.js

882 ms

bh4be.js

bh4be.js

873 ms

bh4be.js

bh4be.js

661 ms

bh4be.js

bh4be.js

880 ms

bh4be.js

bh4be.js

882 ms

bh4be.js

bh4be.js

1245 ms

bh4be.js

bh4be.js

1246 ms

bh4be.js

bh4be.js

1245 ms

bh4be.js

bh4be.js

1245 ms

bh4be.js

bh4be.js

1246 ms

bh4be.js

bh4be.js

1374 ms

bh4be.js

bh4be.js

1374 ms

bh4be.js

bh4be.js

1375 ms

bh4be.js

bh4be.js

1376 ms

bh4be.js

bh4be.js

1375 ms

bh4be.js

bh4be.js

1376 ms

bh4be.js

bh4be.js

1513 ms

bh4be.js

bh4be.js

1518 ms

bh4be.js

bh4be.js

1522 ms

bh4be.js

bh4be.js

1522 ms

bh4be.js

bh4be.js

1524 ms

bh4be.js

bh4be.js

1525 ms

bh4be.js

bh4be.js

1724 ms

bh4bg.js

bh4bg.js

1733 ms

new_logo.jpg

new_logo.jpg

570 ms

edible_slide.jpg

edible_slide.jpg

1424 ms

pure-gold-leaf-24k-gold-1-300x300.jpg

pure-gold-leaf-24k-gold-1-300x300.jpg

661 ms

blank.gif

blank.gif

661 ms

recaptcha__en.js

recaptcha__en.js

101 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

900 ms

js

js

84 ms

analytics.js

analytics.js

79 ms

collect

collect

12 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

243 ms

anchor

anchor

59 ms

css

css

57 ms

ediblegoldleaf.nz

ediblegoldleaf.nz

647 ms

styles__ltr.css

styles__ltr.css

41 ms

recaptcha__en.js

recaptcha__en.js

44 ms

IDLZ5bdCrEGdGR5FKKZfiIWvV7rMSlbAHUEzxUIOBQg.js

IDLZ5bdCrEGdGR5FKKZfiIWvV7rMSlbAHUEzxUIOBQg.js

33 ms

webworker.js

webworker.js

63 ms

logo_48.png

logo_48.png

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

120 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

139 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

140 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

139 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

139 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

138 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

91 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

107 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

108 ms

recaptcha__en.js

recaptcha__en.js

32 ms

loader.gif

loader.gif

217 ms

Accessibility Review

ediblegoldleaf.nz accessibility score

76

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ediblegoldleaf.nz best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ediblegoldleaf.nz SEO score

85

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

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 Ediblegoldleaf.nz 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 Ediblegoldleaf.nz 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

ediblegoldleaf.nz

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