13.4 sec in total
747 ms
12.4 sec
232 ms
Visit iproperty.time.com.my now to see the best up-to-date Iproperty TIME content for Malaysia and also check out these interesting facts you probably never knew about iproperty.time.com.my
TIME dotCom delivers domestic and global connectivity, cloud and data centre solutions in Malaysia and beyond over our 100% fibre optic network.
Visit iproperty.time.com.myWe analyzed Iproperty.time.com.my page load time and found that the first response time was 747 ms and then it took 12.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
iproperty.time.com.my performance score
name
value
score
weighting
Value11.8 s
0/100
10%
Value22.5 s
0/100
25%
Value31.7 s
0/100
10%
Value47,190 ms
0/100
30%
Value0.495
16/100
15%
Value73.4 s
0/100
10%
747 ms
1022 ms
2126 ms
59 ms
23 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Iproperty.time.com.my, 64% (110 requests) were made to Time.com.my and 5% (8 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Apps.time.com.my.
Page size can be reduced by 380.1 kB (14%)
2.6 MB
2.3 MB
In fact, the total size of Iproperty.time.com.my main page is 2.6 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 91.7 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 91.7 kB or 78% of the original size.
Potential reduce by 221.1 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. Iproperty TIME images are well optimized though.
Potential reduce by 55.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 55.7 kB or 25% of the original size.
Potential reduce by 11.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. Iproperty.time.com.my needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 18% of the original size.
Number of requests can be reduced by 106 (69%)
154
48
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iproperty TIME. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 46 to 1 for CSS and as a result speed up the page load time.
iproperty.time.com.my
747 ms
iproperty.time.com.my
1022 ms
www.time.com.my
2126 ms
js
59 ms
recorder.js
23 ms
gtm.js
189 ms
slick.css
267 ms
slick-theme.css
539 ms
colorbox.css
747 ms
jquery.colorbox.min.js
784 ms
jquery.min.js
1283 ms
jquery.once.js
782 ms
drupal.js
792 ms
views_slideshow.js
791 ms
jquery.jgrowl.min.js
992 ms
nicemessages.js
1055 ms
views_slideshow_cycle.js
1038 ms
jquery.cycle.all.js
1050 ms
adapt.min.js
1052 ms
jquery.matchHeight-min.js
1239 ms
unslider.min.js
1296 ms
stacktable.js
1306 ms
scripts.js
1313 ms
js_injector_1.js
1308 ms
js_injector_2.js
1486 ms
js_injector_5.js
1533 ms
js_injector_6.js
1583 ms
js_injector_7.js
1605 ms
js_injector_8.js
1606 ms
js_injector_9.js
1606 ms
system.base.css
1738 ms
system.menus.css
1821 ms
system.messages.css
1838 ms
system.theme.css
1845 ms
views_slideshow.css
1852 ms
aggregator.css
1862 ms
book.css
1994 ms
date.css
2075 ms
field.css
2097 ms
node.css
2103 ms
user.css
2148 ms
fc-pre-chat-form-v2.js
110 ms
widget.js
103 ms
jquery-ui.css
110 ms
jquery-ui.js
132 ms
font-awesome.min.css
88 ms
FontAwesome.otf
105 ms
fontawesome-webfont.eot
114 ms
fontawesome-webfont.svg
141 ms
fontawesome-webfont.ttf
124 ms
fontawesome-webfont.woff
128 ms
fontawesome-webfont.woff2
125 ms
workflow_admin_ui.css
2164 ms
conversion_async.js
54 ms
57 ms
51 ms
optimize.js
71 ms
insight.min.js
58 ms
bat.js
58 ms
js
81 ms
31 ms
views.css
2016 ms
19 ms
analytics.js
98 ms
136025011.js
114 ms
collect
26 ms
136025011
57 ms
collect
12 ms
ga-audiences
18 ms
clarity.js
31 ms
ckeditor.css
1820 ms
ctools.css
1650 ms
custompage.css
1603 ms
jquery.jgrowl.min.css
1634 ms
nicemessages_positions.css
1654 ms
nicemessages_drupal.css
1748 ms
20 ms
shadows.css
1616 ms
views_slideshow_controls_text.css
1609 ms
views_slideshow_cycle.css
1599 ms
unsemantic-grid-responsive-tablet.css
1635 ms
normalize.css
1652 ms
stylesheet.css
1550 ms
font-awesome.min.css
1574 ms
mediaquery.css
1605 ms
css_injector_1.css
1600 ms
css_injector_2.css
1631 ms
css_injector_3.css
1671 ms
css_injector_5.css
1556 ms
css_injector_6.css
1609 ms
css_injector_9.css
1577 ms
css_injector_10.css
1572 ms
css_injector_11.css
1590 ms
css_injector_12.css
1638 ms
css_injector_13.css
1561 ms
css_injector_14.css
1641 ms
fresh_chat.css
1624 ms
unsemantic-grid-desktop.css
1597 ms
fresh_chat.js
1620 ms
slick.min.js
1666 ms
scripts2.js
1569 ms
j.php
98 ms
hotjar-2072731.js
152 ms
logo.png
273 ms
FTTH-Banner-Desktop-2022-04-01.png
3265 ms
FTTO-Banner-Desktop-2022-04-01.png
1542 ms
HomePageBanner-ENT-Desktop_2022_01.png
2279 ms
HomepageMobile-FTTH.png
1880 ms
FTTO-Banner-Mobile-2021-11-01.png
1305 ms
HomePageBanner-ENT-Mobile_2022_01.png
1536 ms
1Gbps%20Home%20BB-bk.png
1557 ms
Internet%20Direct.png
1791 ms
Private%20Leased%20Line.png
1798 ms
business-icon-map-grey.png
1804 ms
icon-live-chat.png
2046 ms
icon-live-chat-TIME.png
2070 ms
close-magenta.png
2058 ms
mef30-logo_0.png
2161 ms
meflso-logo_0.png
2301 ms
mef30sdwan-logo.png
2795 ms
footer_sst.png
2325 ms
timefooterlogo.jpg
2429 ms
popup-close.png
2519 ms
din-light-webfont.woff
2519 ms
menu-dot.gif
2523 ms
icon-coverage-desktop.png
2634 ms
icon-search-mobile.png
2745 ms
din-condensed-webfont.woff
2732 ms
v.gif
20 ms
navi.png
2739 ms
dot.gif
2838 ms
highlight-bg.gif
2926 ms
Selfcare_Laptop.png
2945 ms
support_homepage.png
3216 ms
arrow.png
2993 ms
Unresolved.png
3101 ms
fontawesome-webfont.woff
68 ms
fontawesome-webfont.woff
3144 ms
din-bold-webfont.woff
3170 ms
modules.8203b45d0468dcab4b64.js
89 ms
3709 ms
search-api2.json
3152 ms
chat-bubble-black-lg.png
3266 ms
ytc.js
58 ms
fbevents.js
42 ms
ld.js
85 ms
events.js
79 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
32 ms
slick.woff
3282 ms
595456404301135
396 ms
10059272.json
21 ms
visit-data
415 ms
syncframe
18 ms
558359562164561
235 ms
631032944997221
136 ms
tags
233 ms
tags
240 ms
bubble-chat-icon-rounded.png
2238 ms
pixel
26 ms
fledge-igmembership
933 ms
cm
975 ms
pixel
14 ms
fledge-igmembership
1031 ms
cm
968 ms
down-white.png
2081 ms
ajax-loader.gif
2327 ms
slick.ttf
286 ms
slick.svg
367 ms
fc-pre-chat-form-v2.css
21 ms
event
777 ms
c.gif
43 ms
iproperty.time.com.my 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
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.
iproperty.time.com.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
iproperty.time.com.my 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
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iproperty.time.com.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 Iproperty.time.com.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.
iproperty.time.com.my
Open Graph description is not detected on the main page of Iproperty TIME. 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: