19.7 sec in total
2.6 sec
16.7 sec
368 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.6 sec and then it took 17.1 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
Value18.1 s
0/100
10%
Value28.9 s
0/100
25%
Value39.2 s
0/100
10%
Value1,710 ms
11/100
30%
Value0.051
99/100
15%
Value59.5 s
0/100
10%
2608 ms
958 ms
947 ms
10488 ms
33 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 61% of them (40 requests) were addressed to the original Intex.co.nz, 9% (6 requests) were made to Fonts.googleapis.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (10.5 sec) belongs to the original domain Intex.co.nz.
Page size can be reduced by 288.6 kB (33%)
873.1 kB
584.6 kB
In fact, the total size of Intex.co.nz main page is 873.1 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. 55% of websites need less resources to load. Images take 345.1 kB which makes up the majority of the site volume.
Potential reduce by 122.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 122.1 kB or 76% of the original size.
Potential reduce by 154.0 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. Obviously, Intex needs image optimization as it can save up to 154.0 kB or 45% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 6.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. This website has mostly compressed JavaScripts.
Potential reduce by 5.6 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 24 (50%)
48
24
The browser has sent 48 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 9 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
intex.co.nz
2608 ms
48db4a03c75d5b97667520f4f8cbbbce.min.css
958 ms
styles-l.min.css
947 ms
fd0127460ee50b3114976e396eded447.min.js
10488 ms
css
33 ms
css
46 ms
css
50 ms
css
50 ms
bootstrap.min.css
751 ms
animate.optimized.css
687 ms
type9.css
692 ms
custom.css
1003 ms
design_nz_web_main.css
931 ms
settings_nz_web_main.css
1012 ms
font-awesome.min.css
29 ms
5911826.js
67 ms
js
71 ms
sf-pro-display
25 ms
css2
15 ms
css2
15 ms
print.min.css
671 ms
logo_1.png
677 ms
nz_web_main.png
1133 ms
NZ_Flag.png
676 ms
AU_Flag.png
676 ms
UK_Flag.png
677 ms
USA_Flag.png
868 ms
Engineering_1.png
951 ms
Partners_1.png
1193 ms
shop_1.png
944 ms
ITDC_34841_69c006d2-120f-49f4-a67c-efe7486a7209.png
946 ms
icon-fb.png
1119 ms
icon-insta.png
1236 ms
icon-linkedin.png
1204 ms
icon-youtube.png
1226 ms
icon-twitter.png
1592 ms
icon-chat.png
1424 ms
icon-tiktok.png
1450 ms
SFPRODISPLAYREGULAR.woff
13 ms
SFPRODISPLAYREGULAR.woff
1897 ms
SFPRODISPLAYMEDIUM.woff
35 ms
SFPRODISPLAYMEDIUM.woff
1947 ms
SFPRODISPLAYBOLD.woff
35 ms
SFPRODISPLAYBOLD.woff
1955 ms
Artwork12_9563fd16-bed8-4a8c-bda7-df5760fee97b.png
155 ms
Search_header.png
151 ms
porto-icons.woff
1697 ms
rubix.webp
1650 ms
reseller.webp
1791 ms
shop-column.webp
1940 ms
sf_pro_display_semibold.woff
2351 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
53 ms
opensans-600.woff
2054 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
71 ms
opensans-700.woff
2092 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
86 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
108 ms
opensans-400.woff
2141 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
100 ms
opensans-300.woff
2151 ms
gtm.js
104 ms
banner.js
91 ms
5911826.js
116 ms
conversations-embed.js
88 ms
collectedforms.js
90 ms
js
49 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
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
intex.co.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 doesn't use 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 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: