38.9 sec in total
865 ms
37.1 sec
942 ms
Welcome to imtc.my homepage info - get ready to check IMTC best content for Malaysia right away, or after learning these important things about imtc.my
Leading International Training Provider | Training Centre in Malaysia provides rich selection of training courses in Kuala Lumpur, Dubai, London
Visit imtc.myWe analyzed Imtc.my page load time and found that the first response time was 865 ms and then it took 38 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 8 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
imtc.my performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.2 s
11/100
25%
Value26.9 s
0/100
10%
Value44,600 ms
0/100
30%
Value0.052
98/100
15%
Value68.9 s
0/100
10%
865 ms
435 ms
588 ms
437 ms
453 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 54% of them (76 requests) were addressed to the original Imtc.my, 21% (29 requests) were made to Static.xx.fbcdn.net and 10% (14 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Imtc.my.
Page size can be reduced by 734.6 kB (29%)
2.5 MB
1.8 MB
In fact, the total size of Imtc.my main page is 2.5 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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 53.3 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 53.3 kB or 81% of the original size.
Potential reduce by 11.9 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. IMTC images are well optimized though.
Potential reduce by 290.7 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 290.7 kB or 64% of the original size.
Potential reduce by 378.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. Imtc.my needs all CSS files to be minified and compressed as it can save up to 378.8 kB or 83% of the original size.
Number of requests can be reduced by 51 (40%)
126
75
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMTC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
imtc.my
865 ms
font-awesome.css
435 ms
bootstrap.min.css
588 ms
slicknav.css
437 ms
sumoselect.css
453 ms
slick.css
451 ms
flags.css
478 ms
site.css
645 ms
responsive.css
622 ms
_.pagespeed.jo.MI49t_29yF.js
4906 ms
jquery.min.js
532 ms
bootstrap.min.js
5258 ms
jquery.slicknav.js
5290 ms
jssor.slider-20.mini.js
6535 ms
slick.min.js
5336 ms
jquery.sumoselect.js
617 ms
global.js
5335 ms
fbevents.js
228 ms
logo.png
4859 ms
world.jpg
5126 ms
b8728d60f02342ba8f1e7a2aafbd4837575e7c7d_290x250_fixed.jpg
5072 ms
7a754d0ce70ba9244021213bf76c4dd4ec972bc3_290x250_fixed.jpg
5354 ms
d3dcca1e11cc15305584bb893ab34d110937e5b1_290x250_fixed.jpg
9955 ms
6e9dc36c9ed806ee7143faaa1b531ac0efb86f4d_290x250_fixed.jpg
9296 ms
61f3a35f15bfe75f210e61d8901eec9ed66f8e56_290x250_fixed.jpg
9936 ms
b00e448cac277a7b286960e2d10d964deb46ff72_290x250_fixed.jpg
9933 ms
a209874a1253eb7da142d9f2da19190ce6176416_290x250_fixed.jpg
10273 ms
5c6753581c22a7c43a9acfb8c7a6025b83497977_290x250_fixed.jpg
10273 ms
d6bc1f75680c48219595dad20c8630b0e204ee92_290x250_fixed.jpg
9959 ms
43ce20a835e6ab4ce22416014f3ac899bfd6d85c_290x250_fixed.jpg
10087 ms
b6a3729fad3ebf5e7430b2044a89fead0e08d1bd_290x250_fixed.jpg
10137 ms
29ec4bd312d1945193c39e89691fc00653fae0ae_290x250_fixed.jpg
14410 ms
6bb9721bd5c0eb4ff0ebfe7180f2de74cf25883d_290x250_fixed.jpg
10313 ms
657514ef2b9ad285b960ffc724aeede26db66ad8_290x250_fixed.jpe
14936 ms
16fb09ff68ad565810416ff751ed33259a131f70_290x250_fixed.jpg
15019 ms
client1.jpg
14942 ms
client2.jpg
14960 ms
client3.jpg
14965 ms
client4.jpg
14540 ms
client5.jpg
15082 ms
client6.jpg
15157 ms
client7.jpg
15174 ms
client8.jpg
15372 ms
209c7b3d9430cc62c3d257be057a695e9b53eb58_100x100_fixed.png
19775 ms
985d3033d472e516bb6c5942874f0b8f6edbd5d6_100x100_fixed.png
19776 ms
sdk.js
314 ms
41aa4998ebbf6a70f7d322dc8ee1deac3e6d81a3_100x100_fixed.png
15214 ms
ba33e7ee5d7b130a74f9fd4ad1c97e5edc9e6b3d_100x100_fixed.png
19734 ms
fontawesome-webfont.woff
19683 ms
207 ms
216 ms
49 ms
xd_arbiter.php
513 ms
D5UjVpPua4k
523 ms
c2de6634ce76060ae32ef142ec51ba3f6e8945db_100x100_fixed.png
15728 ms
www-embed-player-vfl5foy2V.css
1147 ms
www-embed-player.js
1861 ms
base.js
2325 ms
glyphicons-halflings-regular.woff
15535 ms
ad23a47ba11cbad4297b925884bbb6f136aaa000_100x100_fixed.png
15411 ms
89121016415792ec7cadba83e6f27c8e0c5f7672_100x100_fixed.png
15451 ms
ff14ea85146369277a3448b7811630947677020d_100x100_fixed.png
15401 ms
5e01d31777c3dac39a04ed753466d5a2335b70ce_100x100_fixed.png
15447 ms
2969a9486a1df446be0cd3e74e4532b83d55e561_100x100_fixed.png
15371 ms
logo-footer.png
19710 ms
image1-thumbnail.jpg
19729 ms
analytics.js
590 ms
page.php
420 ms
image2-thumbnail.jpg
18529 ms
collect
48 ms
3nB4xc2_6jL.css
535 ms
DHQqLLtVOYz.css
718 ms
LJCv51DxJBw.css
743 ms
rIiqPPB00f-.css
1224 ms
YF_27oR5jov.css
1382 ms
emc7iBXdI_a.css
1467 ms
SRSW8M763HA.js
1657 ms
ullQFyhrQFI.js
1772 ms
y97Ig99UVTs.js
1716 ms
KHAtULXOQuz.js
1713 ms
W4NL_XloU4d.js
1724 ms
XlY_wsDnClE.js
1727 ms
rR4Qw0p7TFQ.js
2057 ms
ULtnh-HfQSw.js
1726 ms
d_-F4IIjJo3.js
1728 ms
FOagnU9QnXq.js
1838 ms
Cw6QosZRsiU.js
1838 ms
i8XO-4kv8i7.js
1839 ms
z5eMxBRE-Ji.js
1839 ms
7YklgZdHLYS.js
1847 ms
eACiSk3I2K6.js
1847 ms
6IFzBT9uHU-.js
1943 ms
ga-audiences
392 ms
F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js
204 ms
ad_status.js
403 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
679 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
729 ms
12928159_508039689321385_5967098678064522599_n.jpg
497 ms
safe_image.php
568 ms
safe_image.php
621 ms
safe_image.php
776 ms
553507_168279399964084_509125389_n.jpg
552 ms
1917063_201328390242662_9090001975664711367_n.jpg
662 ms
12541109_548030902028730_6908661195415842352_n.jpg
1155 ms
12512564_472952186246803_7823168396483629983_n.jpg
1149 ms
284225_196613120391822_6290394_n.jpg
1149 ms
12920315_606714672828452_146990091298380020_n.jpg
742 ms
11223312_1317422598274158_1406085073944046759_n.jpg
744 ms
1488310_451722381594814_1495489485_n.jpg
768 ms
11998894_1769476849941061_1976963460675158173_n.jpg
896 ms
12932817_511135615678459_4411284604585494010_n.jpg
899 ms
12924468_511135185678502_1623128093704047249_n.jpg
897 ms
12924512_511135182345169_6096488839873597909_n.jpg
920 ms
12321684_511135179011836_8322008156873492407_n.jpg
928 ms
wL6VQj7Ab77.png
86 ms
1JLnMyDN79z.png
83 ms
6zltWv6aFID.png
86 ms
gm-8CYVMZ_l.png
83 ms
ye4Amg-qrtc.js
200 ms
FASTu8Ostla.png
116 ms
image4-thumbnail.jpg
15458 ms
image1.jpg
15265 ms
image2.jpg
15464 ms
image4.jpg
15476 ms
flags.png
15414 ms
loading.gif
15285 ms
a22.png
15401 ms
trainers_bg.jpg
19539 ms
cd-top-arrow.svg
19538 ms
banner-0.jpg
20401 ms
VXcANLwwL5J.js
58 ms
banner-1.jpg
15761 ms
slide-new1.jpg
15688 ms
banner-2.jpg
15469 ms
slide-new2.jpg
15521 ms
banner-3.jpg
15545 ms
slide-new3.jpg
15536 ms
banner-4.jpg
15813 ms
slide-new4.jpg
19718 ms
fontawesome-webfont.ttf
15578 ms
imtc.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
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
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
imtc.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
imtc.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Imtc.my 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 Imtc.my 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.
imtc.my
Open Graph description is not detected on the main page of IMTC. 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: