7 sec in total
739 ms
6.1 sec
166 ms
Visit indus.my now to see the best up-to-date Indus content and also check out these interesting facts you probably never knew about indus.my
We are a company that supply heavy duty equipment for construction in Kuala Lumpur, KL, Malaysia. We supply heavy duty equipment parts, hydraulic hoses, industrial hoses, and undercarriage parts. Besi...
Visit indus.myWe analyzed Indus.my page load time and found that the first response time was 739 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
indus.my performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value6.3 s
10/100
25%
Value11.2 s
5/100
10%
Value280 ms
81/100
30%
Value0.264
46/100
15%
Value8.3 s
39/100
10%
739 ms
1316 ms
67 ms
812 ms
1065 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Indus.my, 78% (45 requests) were made to Cdn1.npcdn.net and 5% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Cdn1.npcdn.net.
Page size can be reduced by 93.5 kB (11%)
848.8 kB
755.3 kB
In fact, the total size of Indus.my main page is 848.8 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. 40% of websites need less resources to load. Images take 555.3 kB which makes up the majority of the site volume.
Potential reduce by 30.5 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 30.5 kB or 74% of the original size.
Potential reduce by 50.5 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. Indus images are well optimized though.
Potential reduce by 6.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. This website has mostly compressed JavaScripts.
Potential reduce by 5.7 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. Indus.my needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 11% of the original size.
Number of requests can be reduced by 34 (67%)
51
17
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
indus.my
739 ms
www.indus.my
1316 ms
font-awesome.css
67 ms
style.css
812 ms
general_v1.css
1065 ms
color_style.css
895 ms
gumby.css
96 ms
sweetalert2.min.css
82 ms
style.css
802 ms
banner.css
346 ms
jquery.min.js
30 ms
jquery-migrate-3.0.0.min.js
25 ms
jquery-ui.css
30 ms
jquery-ui.theme.min.css
103 ms
jquery.fancybox.js
117 ms
jquery.fancybox.css
125 ms
slick.css
134 ms
slick-theme.css
143 ms
slick.min.js
154 ms
jquery.qrcode-0.12.0.min.js
164 ms
validate.min.js
174 ms
janimate.js
185 ms
janimate.css
198 ms
owl.carousel.min.css
206 ms
owl.theme.newpages.css
218 ms
owl.carousel.js
236 ms
jquery.colourbrightness.min.js
245 ms
animate.css
256 ms
sweetalert2.min.js
265 ms
jquery.nivo.slider.js
274 ms
default.css
287 ms
nivo-slider.css
295 ms
jquery-ui.min.js
28 ms
jquery.matchHeight-min.js
306 ms
jquery.dotdotdot.min.js
316 ms
css
30 ms
css
18 ms
bg.jpg
1428 ms
search_btn(3).png
732 ms
1417752433banner1.jpg
1457 ms
1417752428banner2.jpg
1474 ms
1417752423banner3.jpg
1026 ms
1417686882homeslide.jpg
715 ms
line.jpg
1471 ms
fbevents.js
51 ms
xfbml.customerchat.js
79 ms
top.jpg
1443 ms
menu_bg.png
1778 ms
loading.gif
1421 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
65 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
66 ms
1421292888content.jpg
2134 ms
footerbg.jpg
2155 ms
success_icon.png
1431 ms
fontawesome-webfont.woff
2856 ms
np_add_cart.php
799 ms
arrows.png
1357 ms
bullets.png
1359 ms
indus.my accessibility score
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
Image elements do not have [alt] attributes
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
indus.my 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
Browser errors were logged to the console
Page has valid source maps
indus.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indus.my 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 Indus.my main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
indus.my
Open Graph data is detected on the main page of Indus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: