Tools & Wizards About Us
intex.com.au screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

intex.com.au

Walls & Ceilings Since 1989 | Intex International

Page Load Speed

10.1 sec in total

First Response

1.2 sec

Resources Loaded

8.6 sec

Page Rendered

351 ms

intex.com.au screenshot

About Website

Visit intex.com.au now to see the best up-to-date Intex content for Australia and also check out these interesting facts you probably never knew about intex.com.au

Intex International is engaged in the design and manufacturing of the complete system of tools, equipment, and accessories for the Walls and Ceilings industry.

Visit intex.com.au

Key Findings

We analyzed Intex.com.au page load time and found that the first response time was 1.2 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

intex.com.au performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value2,870 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.383

27/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

Network Requests Diagram

intex.com.au

1157 ms

calendar.css

450 ms

styles-m.css

1184 ms

owl.carousel.css

697 ms

jquery.fancybox.css

701 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 86% of them (138 requests) were addressed to the original Intex.com.au, 7% (12 requests) were made to Cdn.intex.com.au and 3% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Intex.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 278.9 kB (15%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intex.com.au main page is 1.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 97.1 kB

  • Original 115.9 kB
  • After minification 108.6 kB
  • After compression 18.8 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 97.1 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 20.6 kB

  • Original 1.0 MB
  • After minification 986.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. Intex images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 151.2 kB

  • Original 467.0 kB
  • After minification 413.9 kB
  • After compression 315.8 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 151.2 kB or 32% of the original size.

CSS Optimization

-5%

Potential reduce by 10.1 kB

  • Original 213.3 kB
  • After minification 213.1 kB
  • After compression 203.3 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. Intex.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 135 (91%)

Requests Now

149

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intex.com.au

intex.com.au

1157 ms

calendar.css

calendar.css

450 ms

styles-m.css

styles-m.css

1184 ms

owl.carousel.css

owl.carousel.css

697 ms

jquery.fancybox.css

jquery.fancybox.css

701 ms

porto-icons-codes.css

porto-icons-codes.css

702 ms

simple-line-icons.css

simple-line-icons.css

717 ms

animation.css

animation.css

715 ms

font-awesome.min.css

font-awesome.min.css

940 ms

tooltipster.min.css

tooltipster.min.css

939 ms

attachment.css

attachment.css

941 ms

font-awesome.min.css

font-awesome.min.css

956 ms

magnific-popup.css

magnific-popup.css

957 ms

algoliasearch.css

algoliasearch.css

1174 ms

style.css

style.css

1174 ms

owl.carousel.css

owl.carousel.css

1180 ms

wallets.css

wallets.css

1214 ms

styles-l.css

styles-l.css

1284 ms

require.js

require.js

1459 ms

mixins.js

mixins.js

1412 ms

requirejs-config.js

requirejs-config.js

1430 ms

css

css

32 ms

css

css

52 ms

css

css

55 ms

css

css

52 ms

bootstrap.optimized.min.css

bootstrap.optimized.min.css

91 ms

animate.optimized.css

animate.optimized.css

91 ms

type9.css

type9.css

91 ms

custom.css

custom.css

92 ms

design_base.css

design_base.css

94 ms

settings_base.css

settings_base.css

93 ms

font-awesome.min.css

font-awesome.min.css

34 ms

gtm.js

gtm.js

89 ms

intex_logo_1_.png

intex_logo_1_.png

22 ms

rubix_homepage_logo.png

rubix_homepage_logo.png

23 ms

intex-box-logo.png

intex-box-logo.png

22 ms

icon-fb.png

icon-fb.png

21 ms

intex_logo.png

intex_logo.png

264 ms

jquery.js

jquery.js

609 ms

common.js

common.js

247 ms

dataPost.js

dataPost.js

245 ms

bootstrap.js

bootstrap.js

245 ms

app.js

app.js

252 ms

form-key-provider.js

form-key-provider.js

478 ms

mage-translation-dictionary.js

mage-translation-dictionary.js

481 ms

theme.js

theme.js

481 ms

apear.js

apear.js

472 ms

SFPRODISPLAYREGULAR.woff

SFPRODISPLAYREGULAR.woff

645 ms

autocomplete.js

autocomplete.js

692 ms

typeahead.js

typeahead.js

690 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

36 ms

opensans-700.woff

opensans-700.woff

741 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

37 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

69 ms

opensans-600.woff

opensans-600.woff

759 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

69 ms

opensans-400.woff

opensans-400.woff

852 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

69 ms

opensans-300.woff

opensans-300.woff

894 ms

jquery-mixin.js

jquery-mixin.js

908 ms

intex-icon.ttf

intex-icon.ttf

934 ms

rubix_banner.png

rubix_banner.png

22 ms

store_banner.png

store_banner.png

14 ms

owl.carousel.min.js

owl.carousel.min.js

879 ms

lozad.js

lozad.js

818 ms

template.js

template.js

877 ms

confirm.js

confirm.js

918 ms

widget.js

widget.js

963 ms

main.js

main.js

1012 ms

bootstrap.js

bootstrap.js

1028 ms

domReady.js

domReady.js

1027 ms

types.js

types.js

1109 ms

layout.js

layout.js

1151 ms

text.js

text.js

963 ms

smart-keyboard-handler.js

smart-keyboard-handler.js

1007 ms

mage.js

mage.js

1021 ms

jquery.lazyload.js

jquery.lazyload.js

899 ms

underscore.js

underscore.js

922 ms

wrapper.js

wrapper.js

692 ms

translate.js

translate.js

519 ms

modal.js

modal.js

573 ms

version.js

version.js

528 ms

scripts.js

scripts.js

496 ms

knockout.js

knockout.js

734 ms

knockout-es5.js

knockout-es5.js

610 ms

engine.js

engine.js

640 ms

bootstrap.js

bootstrap.js

690 ms

observable_array.js

observable_array.js

697 ms

bound-nodes.js

bound-nodes.js

719 ms

main.js

main.js

761 ms

registry.js

registry.js

755 ms

console-logger.js

console-logger.js

798 ms

js-translation.json

js-translation.json

776 ms

animate.js

animate.js

589 ms

modal-popup.html

modal-popup.html

516 ms

modal-slide.html

modal-slide.html

629 ms

modal-custom.html

modal-custom.html

663 ms

key-codes.js

key-codes.js

705 ms

core.js

core.js

713 ms

z-index.js

z-index.js

743 ms

observable_source.js

observable_source.js

573 ms

renderer.js

renderer.js

680 ms

knockout-repeat.js

knockout-repeat.js

668 ms

knockout-fast-foreach.js

knockout-fast-foreach.js

718 ms

resizable.js

resizable.js

715 ms

i18n.js

i18n.js

754 ms

scope.js

scope.js

768 ms

range.js

range.js

868 ms

mage-init.js

mage-init.js

902 ms

keyboard.js

keyboard.js

950 ms

optgroup.js

optgroup.js

955 ms

after-render.js

after-render.js

995 ms

autoselect.js

autoselect.js

1010 ms

datepicker.js

datepicker.js

1104 ms

outer_click.js

outer_click.js

1136 ms

fadeVisible.js

fadeVisible.js

1185 ms

collapsible.js

collapsible.js

1192 ms

staticChecked.js

staticChecked.js

1237 ms

simple-checked.js

simple-checked.js

1249 ms

bind-html.js

bind-html.js

1341 ms

tooltip.js

tooltip.js

1377 ms

color-picker.js

color-picker.js

2085 ms

events.js

events.js

1404 ms

arrays.js

arrays.js

1331 ms

compare.js

compare.js

1344 ms

misc.js

misc.js

1431 ms

objects.js

objects.js

1437 ms

strings.js

strings.js

1427 ms

template.js

template.js

1484 ms

local.js

local.js

1477 ms

logger.js

logger.js

1545 ms

entry-factory.js

entry-factory.js

1464 ms

console-output-handler.js

console-output-handler.js

1470 ms

formatter.js

formatter.js

1503 ms

message-pool.js

message-pool.js

1506 ms

levels-pool.js

levels-pool.js

1550 ms

logger-utils.js

logger-utils.js

1572 ms

data.js

data.js

1505 ms

disable-selection.js

disable-selection.js

1545 ms

focusable.js

focusable.js

1513 ms

form.js

form.js

1579 ms

ie.js

ie.js

1573 ms

keycode.js

keycode.js

1559 ms

labels.js

labels.js

1504 ms

jquery-patch.js

jquery-patch.js

1553 ms

plugin.js

plugin.js

1521 ms

safe-active-element.js

safe-active-element.js

1575 ms

safe-blur.js

safe-blur.js

1566 ms

scroll-parent.js

scroll-parent.js

1552 ms

tabbable.js

tabbable.js

1504 ms

unique-id.js

unique-id.js

1557 ms

class.js

class.js

1528 ms

loader.js

loader.js

1574 ms

async.js

async.js

1560 ms

tooltip.html

tooltip.html

1426 ms

entry.js

entry.js

988 ms

moment.js

moment.js

1025 ms

spectrum.js

spectrum.js

900 ms

tinycolor.js

tinycolor.js

925 ms

dom-observer.js

dom-observer.js

239 ms

bindings.js

bindings.js

234 ms

Accessibility Review

intex.com.au accessibility score

68

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

[role]s do not have all required [aria-*] attributes

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

intex.com.au best practices score

92

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

Page has valid source maps

SEO Factors

intex.com.au SEO score

87

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Intex.com.au 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 Intex.com.au 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

intex.com.au

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