Access intelligentretail.co.nz. Australia & New Zealand Retail POS Systems

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

intelligentretail.co.nz

650 ms

www.intelligentretail.com.au

3209 ms

css

37 ms

styles.css

287 ms

style.css

538 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Intelligentretail.co.nz, 68% (54 requests) were made to Intelligentretail.com.au and 19% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Intelligentretail.com.au.

Content Size

2.7 MB

After Optimization

1.3 MB

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

HTML Optimization

-58%

Potential reduce by 374 B

Original 647 B
After minification 559 B
After compression 273 B

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 88 B, which is 14% 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 374 B or 58% of the original size.

Image Optimization

-7%

Potential reduce by 69.5 kB

Original 1.0 MB
After minification 944.2 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. Intelligent Retail images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 774.0 kB

Original 1.1 MB
After minification 1.1 MB
After compression 318.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 774.0 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 502.4 kB

Original 585.5 kB
After minification 578.5 kB
After compression 83.1 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. Intelligentretail.co.nz needs all CSS files to be minified and compressed as it can save up to 502.4 kB or 86% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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

intelligentretail.co.nz

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

Australia & New Zealand Retail POS Systems - Intelligent Retail

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

intelligentretail.co.nz

www.intelligentretail.com.au

css

styles.css

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

intelligentretail.co.nz

www.intelligentretail.com.au

css

styles.css

style.css

font-awesome.min.css

style.min.css

stylesheet.min.css

webkit_stylesheet.css

style_dynamic.css

responsive.min.css

style_dynamic_responsive.css

js_composer.css

custom_css.css

style.css

www.intelligentretail.com.au

jquery.js

jquery-migrate.min.js

jquery.form.min.js

scripts.js

qode-like.min.js

plugins.js

jquery.carouFredSel-6.2.1.min.js

lemmon-slider.min.js

jquery.fullPage.min.js

jquery.mousewheel.min.js

jquery.touchSwipe.min.js

isotope.pkgd.min.js

TweenLite.min.js

ScrollToPlugin.min.js

smoothPageScroll.min.js

js

default_dynamic.js

default.min.js

custom_js.js

js_composer_front.js

wp-embed.min.js

wp-emoji-release.min.js

style.css

gtm.js

analytics.js

logo-ir-colour.png

logo-ir-white.png