Access gohealthy.co.nz. GO Healthy

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value19.5 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value3,080 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

gohealthy.co.nz

515 ms

gohealthy.co.nz

857 ms

mutation-observer.js

211 ms

fonts.css

22 ms

bootstrap.min.css

632 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 71% of them (55 requests) were addressed to the original Gohealthy.co.nz, 8% (6 requests) were made to Youtube.com and 6% (5 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Gohealthy.co.nz.

Content Size

3.2 MB

After Optimization

2.6 MB

In fact, the total size of Gohealthy.co.nz main page is 3.2 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 36.2 kB

Original 43.3 kB
After minification 35.0 kB
After compression 7.1 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 8.4 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 36.2 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 237.0 kB

Original 2.4 MB
After minification 2.1 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. GO Healthy images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 264.9 kB

Original 581.0 kB
After minification 581.0 kB
After compression 316.1 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 264.9 kB or 46% of the original size.

CSS Optimization

-23%

Potential reduce by 38.1 kB

Original 163.5 kB
After minification 163.5 kB
After compression 125.4 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. Gohealthy.co.nz needs all CSS files to be minified and compressed as it can save up to 38.1 kB or 23% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gohealthy.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 Gohealthy.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

gohealthy.co.nz

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

Report Summary

Performance

Accessibility

Best Practices

SEO

GO Healthy - Home

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

gohealthy.co.nz

gohealthy.co.nz

mutation-observer.js

fonts.css

bootstrap.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

gohealthy.co.nz

gohealthy.co.nz

mutation-observer.js

fonts.css

bootstrap.min.css

umbraco.css

magnific-popup.css

core.min.css

jquery-3.7.1.min.js

bootstrap.min.js

lodash.custom.min.js

cookies_min.js

jquery.magnific-popup.min.js

product.min.css

testimonials.min.css

home.min.css

vendor.min.js

core.min.js

isotope.pkgd.min.js

imagesloaded.pkgd.min.js

gtm.js

hqdefault.jpg

backgroundTexture.png

new-range-sm.png

pro-series-range-2.png

top-sellers-sm.png

vir-defence.png

ashwaganha.png

GO-magnesium-sleep.png

delivery.png

Stockist.png

playBtn.png

sponsor.png

hqdefault.jpg

hqdefault.jpg

hqdefault.jpg

CsGIWtZW3nE

hqdefault.jpg

goh0495-canstar_desktop-1380x760px-final6.jpg

goh0495-canstar_mobile-750x970px-final2.jpg

uTWJm-sblk4

story.png

ingredients.jpg