Tools & Wizards About Us
hx.systems screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

hx.systems

HX.Systems - offering IoT-oriented devices to retail partners & b2b

Page Load Speed

19.2 sec in total

First Response

2.5 sec

Resources Loaded

16.5 sec

Page Rendered

150 ms

hx.systems screenshot

About Website

Welcome to hx.systems homepage info - get ready to check HX best content for South Africa right away, or after learning these important things about hx.systems

HX.Systems provides control solutions for IoT devices enabling you to monitor & manage your equipment remotely as well as to secure your network

Visit hx.systems

Key Findings

We analyzed Hx.systems page load time and found that the first response time was 2.5 sec and then it took 16.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

hx.systems performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.119

85/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

2493 ms

wp-emoji-release.min.js

490 ms

style.css

775 ms

style.min.css

852 ms

mediaelementplayer-legacy.min.css

849 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 41% of them (31 requests) were addressed to the original Hx.systems, 36% (27 requests) were made to I0.wp.com and 7% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (9.7 sec) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.8 kB (4%)

Content Size

2.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hx.systems main page is 2.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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 73.1 kB

  • Original 90.0 kB
  • After minification 88.1 kB
  • After compression 16.9 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 73.1 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 589 B

  • Original 1.9 MB
  • After minification 1.9 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. HX images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 237 B

  • Original 123.2 kB
  • After minification 123.2 kB
  • After compression 123.0 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.

CSS Optimization

-3%

Potential reduce by 3.8 kB

  • Original 116.3 kB
  • After minification 116.3 kB
  • After compression 112.5 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. Hx.systems has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (48%)

Requests Now

69

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2493 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

490 ms

style.css

style.css

775 ms

style.min.css

style.min.css

852 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

849 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

878 ms

front.css

front.css

930 ms

wpfront-scroll-top.min.css

wpfront-scroll-top.min.css

928 ms

dashicons.min.css

dashicons.min.css

1386 ms

css

css

118 ms

style.css

style.css

1128 ms

all.css

all.css

312 ms

v4-shims.css

v4-shims.css

372 ms

jetpack.css

jetpack.css

1132 ms

jquery.min.js

jquery.min.js

1479 ms

jquery-migrate.min.js

jquery-migrate.min.js

1232 ms

entry-date.js

entry-date.js

1230 ms

responsive-menu.js

responsive-menu.js

1400 ms

js

js

179 ms

flexslider.css

flexslider.css

1299 ms

public.css

public.css

1425 ms

icons.css

icons.css

1435 ms

shortcodes.css

shortcodes.css

1580 ms

photon.min.js

photon.min.js

1578 ms

wpfront-scroll-top.min.js

wpfront-scroll-top.min.js

1583 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

1666 ms

index.js

index.js

1736 ms

e-202239.js

e-202239.js

77 ms

css

css

20 ms

easy-table.css

easy-table.css

745 ms

fbevents.js

fbevents.js

281 ms

gtm.js

gtm.js

277 ms

linkedin_icon.png

linkedin_icon.png

1260 ms

main_bg.jpg

main_bg.jpg

1077 ms

108.png

108.png

563 ms

FaceBook-icon.png

FaceBook-icon.png

1336 ms

south-africa-icon.png

south-africa-icon.png

1809 ms

HX-australia_400.png

HX-australia_400.png

2390 ms

GSM-Commander-NZ-Products.jpg

GSM-Commander-NZ-Products.jpg

2176 ms

Noke-pro.jpg

Noke-pro.jpg

2484 ms

Fing-Fingbox.jpg

Fing-Fingbox.jpg

3051 ms

Domotz-New-Zealand.jpg

Domotz-New-Zealand.jpg

3146 ms

GSM-Commander-products.png

GSM-Commander-products.png

4713 ms

HX-GSMC-Nok%C3%A9.jpg

HX-GSMC-Nok%C3%A9.jpg

4407 ms

GSM-2.jpg

GSM-2.jpg

3930 ms

GSM-Commander-automation.jpg

GSM-Commander-automation.jpg

4133 ms

Noke-Padlock-and-HD-together-wtih-App.png

Noke-Padlock-and-HD-together-wtih-App.png

5306 ms

Noke-business-case.jpg

Noke-business-case.jpg

4517 ms

Noke_U-Lock.jpg

Noke_U-Lock.jpg

5539 ms

FINGBOX.png

FINGBOX.png

6557 ms

Parental-control-features.jpg

Parental-control-features.jpg

6847 ms

Fingbox-protecting-your-family.jpg

Fingbox-protecting-your-family.jpg

6461 ms

Cyber-crime-teach-Cyber-safe.jpg

Cyber-crime-teach-Cyber-safe.jpg

7061 ms

Domotz-Solution-with-Box.png

Domotz-Solution-with-Box.png

8591 ms

HX-Domtz-solution.jpg

HX-Domtz-solution.jpg

7074 ms

domotz-channel-pro-awards.jpg

domotz-channel-pro-awards.jpg

8301 ms

HX-Fingbox-Domotz.jpg

HX-Fingbox-Domotz.jpg

8387 ms

GSM-C.png

GSM-C.png

9740 ms

MicroTIK_logo_ct_mod-1-300x121.png

MicroTIK_logo_ct_mod-1-300x121.png

7882 ms

mtcna.png

mtcna.png

7601 ms

mtcre.png

mtcre.png

8209 ms

cropped-HX.Systems-au-logo.png

cropped-HX.Systems-au-logo.png

674 ms

analytics.js

analytics.js

426 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

358 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

358 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff

427 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

440 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

472 ms

style-glass.png

style-glass.png

532 ms

193744934547447

193744934547447

215 ms

forkawesome-webfont.woff

forkawesome-webfont.woff

965 ms

bg_direction_nav.png

bg_direction_nav.png

312 ms

481070752631948

481070752631948

131 ms

collect

collect

56 ms

collect

collect

52 ms

openbridge_plugin.js

openbridge_plugin.js

1420 ms

Accessibility Review

hx.systems accessibility score

90

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

hx.systems 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

hx.systems 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

    EN

  • Encoding

    UTF-8

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

hx.systems

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