11.9 sec in total
2.1 sec
9.5 sec
333 ms
Visit intex.co.nz now to see the best up-to-date Intex content and also check out these interesting facts you probably never knew about intex.co.nz
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.co.nzWe analyzed Intex.co.nz page load time and found that the first response time was 2.1 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
intex.co.nz performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value5.4 s
20/100
25%
Value17.2 s
0/100
10%
Value1,500 ms
14/100
30%
Value0.38
27/100
15%
Value22.6 s
1/100
10%
2107 ms
429 ms
1146 ms
659 ms
659 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 86% of them (140 requests) were addressed to the original Intex.co.nz, 7% (12 requests) were made to Cdn.intex.co.nz 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.co.nz.
Page size can be reduced by 235.1 kB (13%)
1.8 MB
1.6 MB
In fact, the total size of Intex.co.nz 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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 104.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. 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 104.1 kB or 85% of the original size.
Potential reduce by 17.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.
Potential reduce by 104.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 104.0 kB or 25% of the original size.
Potential reduce by 9.8 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.co.nz has all CSS files already compressed.
Number of requests can be reduced by 134 (91%)
148
14
The browser has sent 148 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 27 to 1 for CSS and as a result speed up the page load time.
intex.co.nz
2107 ms
calendar.css
429 ms
styles-m.css
1146 ms
owl.carousel.css
659 ms
jquery.fancybox.css
659 ms
porto-icons-codes.css
664 ms
simple-line-icons.css
681 ms
animation.css
685 ms
font-awesome.min.css
884 ms
tooltipster.min.css
885 ms
attachment.css
889 ms
font-awesome.min.css
913 ms
magnific-popup.css
915 ms
style.css
1106 ms
owl.carousel.css
1111 ms
wallets.css
1113 ms
amslick.min.css
1142 ms
styles-l.css
1384 ms
require.js
1378 ms
mixins.js
1340 ms
requirejs-config.js
1349 ms
css
31 ms
css
49 ms
css
53 ms
css
54 ms
bootstrap.optimized.min.css
88 ms
animate.optimized.css
92 ms
type9.css
94 ms
custom.css
96 ms
design_nz.css
104 ms
settings_nz.css
109 ms
gtm.js
89 ms
intex_logo_1_.png
24 ms
rubix_homepage_logo.png
22 ms
intex-box-logo.png
40 ms
icon-fb.png
22 ms
intex_logo.png
252 ms
jquery.js
604 ms
common.js
236 ms
dataPost.js
242 ms
bootstrap.js
242 ms
app.js
234 ms
form-key-provider.js
458 ms
mage-translation-dictionary.js
456 ms
theme.js
469 ms
apear.js
454 ms
SFPRODISPLAYREGULAR.woff
613 ms
SFPRODISPLAYMEDIUM.woff
1167 ms
SFPRODISPLAYBOLD.woff
1200 ms
autocomplete.js
673 ms
typeahead.js
669 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
36 ms
opensans-700.woff
822 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
55 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
75 ms
opensans-600.woff
837 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
74 ms
opensans-400.woff
959 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
75 ms
opensans-300.woff
966 ms
jquery-mixin.js
1019 ms
intex-icon.ttf
1059 ms
rubix_banner.png
72 ms
store_banner.png
49 ms
owl.carousel.min.js
1103 ms
lozad.js
1042 ms
domReady.js
1077 ms
types.js
1111 ms
layout.js
1175 ms
bootstrap.js
1204 ms
main.js
1226 ms
template.js
1249 ms
confirm.js
1295 ms
widget.js
1336 ms
text.js
1187 ms
smart-keyboard-handler.js
1197 ms
mage.js
1224 ms
jquery.lazyload.js
1111 ms
underscore.js
1091 ms
wrapper.js
720 ms
main.js
518 ms
registry.js
483 ms
console-logger.js
510 ms
knockout.js
809 ms
knockout-es5.js
585 ms
engine.js
583 ms
bootstrap.js
646 ms
observable_array.js
675 ms
bound-nodes.js
709 ms
scripts.js
791 ms
translate.js
727 ms
modal.js
782 ms
version.js
766 ms
js-translation.json
755 ms
animate.js
682 ms
arrays.js
609 ms
compare.js
608 ms
misc.js
672 ms
objects.js
701 ms
strings.js
755 ms
template.js
832 ms
local.js
771 ms
logger.js
784 ms
entry-factory.js
828 ms
console-output-handler.js
867 ms
formatter.js
918 ms
message-pool.js
990 ms
levels-pool.js
995 ms
logger-utils.js
1012 ms
observable_source.js
954 ms
renderer.js
997 ms
knockout-repeat.js
993 ms
knockout-fast-foreach.js
1058 ms
resizable.js
1060 ms
i18n.js
1082 ms
scope.js
1117 ms
range.js
1159 ms
mage-init.js
1223 ms
keyboard.js
1280 ms
optgroup.js
1286 ms
after-render.js
1312 ms
autoselect.js
1340 ms
datepicker.js
1362 ms
outer_click.js
1396 ms
fadeVisible.js
1334 ms
collapsible.js
1346 ms
staticChecked.js
1382 ms
simple-checked.js
1350 ms
bind-html.js
1364 ms
tooltip.js
1402 ms
color-picker.js
1335 ms
events.js
1350 ms
modal-popup.html
1399 ms
modal-slide.html
1351 ms
modal-custom.html
1367 ms
key-codes.js
1399 ms
core.js
1339 ms
z-index.js
1345 ms
entry.js
1341 ms
moment.js
1287 ms
class.js
1180 ms
loader.js
1230 ms
async.js
1108 ms
tooltip.html
484 ms
spectrum.js
557 ms
tinycolor.js
561 ms
data.js
345 ms
disable-selection.js
448 ms
focusable.js
444 ms
form.js
457 ms
ie.js
559 ms
keycode.js
551 ms
labels.js
568 ms
jquery-patch.js
670 ms
plugin.js
679 ms
safe-active-element.js
679 ms
safe-blur.js
778 ms
scroll-parent.js
789 ms
tabbable.js
791 ms
unique-id.js
896 ms
dom-observer.js
691 ms
bindings.js
681 ms
intex.co.nz accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
[role]s do not have all required [aria-*] attributes
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
intex.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
intex.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intex.co.nz 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.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.
intex.co.nz
Open Graph data is detected on the main page of Intex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: