Tools & Wizards About Us
cortex.co.nz screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

cortex.co.nz

Cortex Limited | For Better Business Control | cortex.co.nz

Page Load Speed

5.3 sec in total

First Response

623 ms

Resources Loaded

4.4 sec

Page Rendered

297 ms

cortex.co.nz screenshot

About Website

Visit cortex.co.nz now to see the best up-to-date Cortex content and also check out these interesting facts you probably never knew about cortex.co.nz

We're the business enabler. We specialise in building software solutions that provide insight into how a business is working – and how it can work better.

Visit cortex.co.nz

Key Findings

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

Performance Metrics

cortex.co.nz performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.5 s

48/100

10%

Network Requests Diagram

cortex.co.nz

623 ms

cortex.co.nz

955 ms

cortex-2fe7f6.webflow.c1c7d3c3e.min.css

242 ms

js

481 ms

js-1

717 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 92% of them (34 requests) were addressed to the original Cortex.co.nz, 3% (1 request) were made to Js.hs-analytics.net and 3% (1 request) were made to Js.hs-banner.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Cortex.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 kB (14%)

Content Size

23.2 kB

After Optimization

19.9 kB

  • JavaScript

In fact, the total size of Cortex.co.nz main page is 23.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 23.2 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 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 web page is already compressed.

JavaScript Optimization

-14%

Potential reduce by 3.3 kB

  • Original 23.2 kB
  • After minification 23.2 kB
  • After compression 19.9 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 3.3 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (21%)

Requests Now

29

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cortex.co.nz

cortex.co.nz

623 ms

cortex.co.nz

cortex.co.nz

955 ms

cortex-2fe7f6.webflow.c1c7d3c3e.min.css

cortex-2fe7f6.webflow.c1c7d3c3e.min.css

242 ms

js

js

481 ms

js-1

js-1

717 ms

cmsslider.js

cmsslider.js

947 ms

jquery-3.5.1.min.dc5e7f18c8.js

jquery-3.5.1.min.dc5e7f18c8.js

957 ms

webflow.e1613f72e.js

webflow.e1613f72e.js

1452 ms

23988245.js

23988245.js

966 ms

648f1bd5a37d6238ef36a8f6_cortex_logo.svg

648f1bd5a37d6238ef36a8f6_cortex_logo.svg

723 ms

6492e7b7facf45d0ac6fa3d1_home-banner-1.webp

6492e7b7facf45d0ac6fa3d1_home-banner-1.webp

1693 ms

6493172dca9027bb1ba326b6_intranet-platforms.webp

6493172dca9027bb1ba326b6_intranet-platforms.webp

1172 ms

647dd6cc54b50a794ffde5c5_Arrow%20Right.svg

647dd6cc54b50a794ffde5c5_Arrow%20Right.svg

945 ms

6493172d87fa9e0793613293_web-applications.webp

6493172d87fa9e0793613293_web-applications.webp

1194 ms

6493172deba96b524e74c4d1_start-up-development.webp

6493172deba96b524e74c4d1_start-up-development.webp

1207 ms

64efab639b0b4a64419781d5_image%202.png

64efab639b0b4a64419781d5_image%202.png

1652 ms

6493172cdc66515444d6d10c_ratings-engine.webp

6493172cdc66515444d6d10c_ratings-engine.webp

1409 ms

648f207148dec1f2075402c4_bearing_360_logo.svg

648f207148dec1f2075402c4_bearing_360_logo.svg

1436 ms

648f2070259a699a3643be62_Hype_dexte_logo.svg

648f2070259a699a3643be62_Hype_dexte_logo.svg

1443 ms

648f2070a37d6238ef3aa3f8_Solve_it_logo.svg

648f2070a37d6238ef3aa3f8_Solve_it_logo.svg

1449 ms

648f2070464b7cc8abfa9955_Nexus_logo.svg

648f2070464b7cc8abfa9955_Nexus_logo.svg

1648 ms

648f20701719cb1751d982bf_Sealed_air_logo.svg

648f20701719cb1751d982bf_Sealed_air_logo.svg

1678 ms

648f207032f94fd8cc9edc6f_SBT_group_logo.svg

648f207032f94fd8cc9edc6f_SBT_group_logo.svg

1683 ms

648f2070ead0ed4bde32a7c5_Rhenus_logo.svg

648f2070ead0ed4bde32a7c5_Rhenus_logo.svg

1691 ms

648f207065d52688346ea41b_oji_fibre_logo.svg

648f207065d52688346ea41b_oji_fibre_logo.svg

1884 ms

648f2070d557a43ba6d48789_NetIoGix_logo.svg

648f2070d557a43ba6d48789_NetIoGix_logo.svg

1887 ms

648f2070c67475da7b000769_new_port_logo.svg

648f2070c67475da7b000769_new_port_logo.svg

1917 ms

648f207065d52688346ea36c_Diversey_logo.svg

648f207065d52688346ea36c_Diversey_logo.svg

1922 ms

648f20701719cb1751d9824d_Leading_edge_logo.svg

648f20701719cb1751d9824d_Leading_edge_logo.svg

1934 ms

64879f31082e08788d6c353a_LinkedIn.svg

64879f31082e08788d6c353a_LinkedIn.svg

1933 ms

647dba24155d0a94f97b2fcc_Onest-Bold.ttf

647dba24155d0a94f97b2fcc_Onest-Bold.ttf

2542 ms

647dba5c85d4a6eadabaa1e3_Onest-Thin.ttf

647dba5c85d4a6eadabaa1e3_Onest-Thin.ttf

2309 ms

647dba4ccdf8acb90fd3aa8f_Onest-Medium.ttf

647dba4ccdf8acb90fd3aa8f_Onest-Medium.ttf

2349 ms

647dba54284342c55bb966bc_Onest-Regular.ttf

647dba54284342c55bb966bc_Onest-Regular.ttf

2354 ms

23988245.js

23988245.js

71 ms

banner.js

banner.js

64 ms

collectedforms.js

collectedforms.js

150 ms

Accessibility Review

cortex.co.nz accessibility score

95

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

Best Practices

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

SEO Factors

cortex.co.nz SEO score

100

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

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

cortex.co.nz

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