Tools & Wizards About Us
ambergrisnz.co.nz screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ambergrisnz.co.nz

Ambergris NZ | Most trusted/longest Ambergris trader in NZ

Page Load Speed

11.8 sec in total

First Response

1 sec

Resources Loaded

10.3 sec

Page Rendered

544 ms

ambergrisnz.co.nz screenshot

About Website

Welcome to ambergrisnz.co.nz homepage info - get ready to check Ambergris NZ best content right away, or after learning these important things about ambergrisnz.co.nz

The most trusted & longest Ambergris trader in NZ. Ambergris is a valuable material used in the manufacture of perfume in many parts of the world.

Visit ambergrisnz.co.nz

Key Findings

We analyzed Ambergrisnz.co.nz page load time and found that the first response time was 1 sec and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

ambergrisnz.co.nz performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

www.ambergrisnz.co.nz

1011 ms

align.module.css

675 ms

fieldgroup.module.css

683 ms

container-inline.module.css

674 ms

clearfix.module.css

669 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 90% of them (76 requests) were addressed to the original Ambergrisnz.co.nz, 6% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Ambergrisnz.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.5 kB (5%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ambergrisnz.co.nz main page is 2.0 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 28.0 kB

  • Original 34.9 kB
  • After minification 32.9 kB
  • After compression 7.0 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 28.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 2.4 kB

  • Original 1.5 MB
  • After minification 1.5 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. Ambergris NZ images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 45.5 kB

  • Original 467.7 kB
  • After minification 464.4 kB
  • After compression 422.2 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

-34%

Potential reduce by 16.5 kB

  • Original 48.2 kB
  • After minification 47.1 kB
  • After compression 31.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. Ambergrisnz.co.nz needs all CSS files to be minified and compressed as it can save up to 16.5 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (82%)

Requests Now

77

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ambergrisnz.co.nz

www.ambergrisnz.co.nz

1011 ms

align.module.css

align.module.css

675 ms

fieldgroup.module.css

fieldgroup.module.css

683 ms

container-inline.module.css

container-inline.module.css

674 ms

clearfix.module.css

clearfix.module.css

669 ms

details.module.css

details.module.css

704 ms

hidden.module.css

hidden.module.css

750 ms

item-list.module.css

item-list.module.css

1382 ms

js.module.css

js.module.css

1372 ms

nowrap.module.css

nowrap.module.css

1376 ms

position-container.module.css

position-container.module.css

1375 ms

progress.module.css

progress.module.css

1400 ms

reset-appearance.module.css

reset-appearance.module.css

1436 ms

resize.module.css

resize.module.css

2034 ms

sticky-header.module.css

sticky-header.module.css

2047 ms

system-status-counter.css

system-status-counter.css

2051 ms

system-status-report-counters.css

system-status-report-counters.css

2040 ms

system-status-report-general-info.css

system-status-report-general-info.css

2058 ms

tablesort.module.css

tablesort.module.css

2113 ms

tree-child.module.css

tree-child.module.css

2686 ms

views.module.css

views.module.css

2705 ms

views_slideshow_cycle.css

views_slideshow_cycle.css

2706 ms

webform_bootstrap.css

webform_bootstrap.css

2714 ms

style.css

style.css

2721 ms

overwrite.css

overwrite.css

2814 ms

all.js

all.js

100 ms

v4-shims.js

v4-shims.js

116 ms

css

css

48 ms

jquery.min.js

jquery.min.js

3332 ms

underscore-min.js

underscore-min.js

3370 ms

element.matches.js

element.matches.js

3375 ms

object.assign.js

object.assign.js

3373 ms

once.min.js

once.min.js

3405 ms

jquery.once.min.js

jquery.once.min.js

3440 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

3978 ms

drupal.js

drupal.js

4028 ms

drupal.init.js

drupal.init.js

4025 ms

drupal.bootstrap.js

drupal.bootstrap.js

4041 ms

attributes.js

attributes.js

4065 ms

theme.js

theme.js

4106 ms

affix.js

affix.js

3981 ms

alert.js

alert.js

4008 ms

button.js

button.js

4023 ms

carousel.js

carousel.js

4024 ms

collapse.js

collapse.js

4033 ms

dropdown.js

dropdown.js

4064 ms

modal.js

modal.js

3976 ms

tooltip.js

tooltip.js

3972 ms

popover.js

popover.js

4001 ms

scrollspy.js

scrollspy.js

3996 ms

tab.js

tab.js

3995 ms

transition.js

transition.js

4047 ms

ofi.min.js

ofi.min.js

3990 ms

scripts.js

scripts.js

3954 ms

webform.behaviors.js

webform.behaviors.js

3992 ms

jquery.once.bc.js

jquery.once.bc.js

3998 ms

states.js

states.js

3988 ms

states.js

states.js

4024 ms

webform.states.js

webform.states.js

3971 ms

webform_bootstrap.states.js

webform_bootstrap.states.js

3975 ms

popover.js

popover.js

3996 ms

tooltip.js

tooltip.js

4018 ms

json2.js

json2.js

3987 ms

jquery.cycle.all.js

jquery.cycle.all.js

3905 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

23 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

27 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

37 ms

KFOkCnqEu92Fr1Mu51xIIzQ.woff

KFOkCnqEu92Fr1Mu51xIIzQ.woff

48 ms

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

48 ms

views_slideshow_cycle.js

views_slideshow_cycle.js

3973 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

3989 ms

views_slideshow.js

views_slideshow.js

3972 ms

logo.png

logo.png

3363 ms

logo.png

logo.png

3339 ms

whale-2.jpg

whale-2.jpg

3338 ms

whale-1.jpg

whale-1.jpg

2782 ms

whale-3.jpg

whale-3.jpg

3821 ms

whale-4.jpg

whale-4.jpg

4028 ms

whale-5.jpg

whale-5.jpg

4011 ms

flag.svg

flag.svg

3902 ms

whatisit.jpg

whatisit.jpg

3286 ms

home_img1_0.jpg

home_img1_0.jpg

2750 ms

home_img2_1.jpg

home_img2_1.jpg

2766 ms

home_img3_0.jpg

home_img3_0.jpg

2753 ms

Accessibility Review

ambergrisnz.co.nz accessibility score

87

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

ambergrisnz.co.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

High

Page has valid source maps

SEO Factors

ambergrisnz.co.nz SEO score

83

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

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 Ambergrisnz.co.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 Ambergrisnz.co.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

ambergrisnz.co.nz

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