Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

hillyers.co.nz

Home | Hillyers Hand Made

Page Load Speed

577 ms in total

First Response

58 ms

Resources Loaded

462 ms

Page Rendered

57 ms

About Website

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

Visit hillyers.co.nz

Key Findings

We analyzed Hillyers.co.nz page load time and found that the first response time was 58 ms and then it took 519 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

hillyers.co.nz performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

www.hillyers.co.nz

58 ms

minified.js

29 ms

focus-within-polyfill.js

27 ms

polyfill.min.js

61 ms

thunderbolt-commons.60ed9a5a.bundle.min.js

108 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hillyers.co.nz, 42% (22 requests) were made to Static.wixstatic.com and 28% (15 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (174 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.5 MB (32%)

Content Size

20.1 MB

After Optimization

13.6 MB

In fact, the total size of Hillyers.co.nz main page is 20.1 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. Only a small number of websites need less resources to load. Images take 19.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 521.9 kB

  • Original 653.3 kB
  • After minification 651.6 kB
  • After compression 131.4 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 521.9 kB or 80% of the original size.

Image Optimization

-31%

Potential reduce by 6.0 MB

  • Original 19.2 MB
  • After minification 13.2 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. Obviously, Hillyers needs image optimization as it can save up to 6.0 MB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 244.4 kB
  • After minification 244.4 kB
  • After compression 240.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.

Requests Breakdown

Number of requests can be reduced by 10 (28%)

Requests Now

36

After Optimization

26

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

Accessibility Review

hillyers.co.nz accessibility score

100

Accessibility Issues

Best Practices

hillyers.co.nz 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

High

Page has valid source maps

SEO Factors

hillyers.co.nz SEO score

90

Search Engine Optimization Advices

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 Hillyers.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 Hillyers.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

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