Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

ollivier.co.nz

Ollivier & Co - Home of Corax Cadastral digital GIS data for New Zealand Maps

Page Load Speed

3.1 sec in total

First Response

1.2 sec

Resources Loaded

1.8 sec

Page Rendered

107 ms

ollivier.co.nz screenshot

About Website

Click here to check amazing Ollivier content. Otherwise, check out these important facts you probably never knew about ollivier.co.nz

Visit ollivier.co.nz

Key Findings

We analyzed Ollivier.co.nz page load time and found that the first response time was 1.2 sec and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

ollivier.co.nz performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value1.0 s

100/100

10%

Network Requests Diagram

ollivier.co.nz

1192 ms

logotop.gif

512 ms

logolite.gif

1007 ms

logobelow.gif

690 ms

index2.php

205 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 83% of them (5 requests) were addressed to the original Ollivier.co.nz, 17% (1 request) were made to Www4.clustrmaps.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ollivier.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.0 kB (39%)

Content Size

28.3 kB

After Optimization

17.3 kB

In fact, the total size of Ollivier.co.nz main page is 28.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 20.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 5.8 kB

  • Original 7.9 kB
  • After minification 6.4 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 1.5 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.8 kB or 74% of the original size.

Image Optimization

-25%

Potential reduce by 5.1 kB

  • Original 20.4 kB
  • After minification 15.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. Obviously, Ollivier needs image optimization as it can save up to 5.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ollivier. According to our analytics all requests are already optimized.

Accessibility Review

ollivier.co.nz accessibility score

59

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

ollivier.co.nz best practices score

67

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

SEO Factors

ollivier.co.nz SEO score

54

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ollivier.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ollivier.co.nz main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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