Tools & Wizards About Us
time.com.my screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

time.com.my

Time for Home

Page Load Speed

15.5 sec in total

First Response

737 ms

Resources Loaded

14.5 sec

Page Rendered

258 ms

time.com.my screenshot

About Website

Welcome to time.com.my homepage info - get ready to check Time best content for Malaysia right away, or after learning these important things about time.com.my

Get The Complete Kabel Besar Package: 600Mbps at RM99 for first 6 months plus FREE WiFi 6 router and mesh. Sign up now!

Visit time.com.my

Key Findings

We analyzed Time.com.my page load time and found that the first response time was 737 ms and then it took 14.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

time.com.my performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value20.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value35.7 s

0/100

25%

SI (Speed Index)

Value33.6 s

0/100

10%

TBT (Total Blocking Time)

Value3,590 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.871

4/100

15%

TTI (Time to Interactive)

Value35.0 s

0/100

10%

Network Requests Diagram

time.com.my

737 ms

www.time.com.my

1034 ms

colorbox.css

485 ms

jquery.colorbox.min.js

492 ms

jquery.min.js

1220 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 93% of them (93 requests) were addressed to the original Time.com.my, 2% (2 requests) were made to Code.jquery.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.7 sec) relates to the external source Apps.time.com.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 978.3 kB (35%)

Content Size

2.8 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Time.com.my main page is 2.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. 45% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 62.6 kB

  • Original 73.7 kB
  • After minification 66.7 kB
  • After compression 11.2 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 62.6 kB or 85% of the original size.

Image Optimization

-20%

Potential reduce by 429.5 kB

  • Original 2.1 MB
  • After minification 1.7 MB

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, Time needs image optimization as it can save up to 429.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 262.4 kB

  • Original 356.9 kB
  • After minification 295.4 kB
  • After compression 94.5 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 262.4 kB or 74% of the original size.

CSS Optimization

-83%

Potential reduce by 223.8 kB

  • Original 268.6 kB
  • After minification 208.6 kB
  • After compression 44.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. Time.com.my needs all CSS files to be minified and compressed as it can save up to 223.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (59%)

Requests Now

97

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 22 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

time.com.my

time.com.my

737 ms

www.time.com.my

www.time.com.my

1034 ms

colorbox.css

colorbox.css

485 ms

jquery.colorbox.min.js

jquery.colorbox.min.js

492 ms

jquery.min.js

jquery.min.js

1220 ms

jquery.once.js

jquery.once.js

498 ms

drupal.js

drupal.js

759 ms

views_slideshow.js

views_slideshow.js

1237 ms

jquery.jgrowl.min.js

jquery.jgrowl.min.js

979 ms

nicemessages.js

nicemessages.js

980 ms

jquery.cycle.all.js

jquery.cycle.all.js

1463 ms

views_slideshow_cycle.js

views_slideshow_cycle.js

1487 ms

adapt.min.js

adapt.min.js

1458 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

1469 ms

unslider.min.js

unslider.min.js

1696 ms

stacktable.js

stacktable.js

1700 ms

scripts.js

scripts.js

1931 ms

js_injector_1.js

js_injector_1.js

1959 ms

js_injector_2.js

js_injector_2.js

1955 ms

js_injector_6.js

js_injector_6.js

1984 ms

system.base.css

system.base.css

2178 ms

system.menus.css

system.menus.css

2176 ms

system.messages.css

system.messages.css

2417 ms

system.theme.css

system.theme.css

2440 ms

views_slideshow.css

views_slideshow.css

2446 ms

aggregator.css

aggregator.css

2464 ms

date.css

date.css

2661 ms

field.css

field.css

2671 ms

node.css

node.css

2904 ms

user.css

user.css

2927 ms

views.css

views.css

2934 ms

ckeditor.css

ckeditor.css

2957 ms

ctools.css

ctools.css

3138 ms

custompage.css

custompage.css

3169 ms

jquery.jgrowl.min.css

jquery.jgrowl.min.css

3390 ms

nicemessages_positions.css

nicemessages_positions.css

3399 ms

nicemessages_drupal.css

nicemessages_drupal.css

3416 ms

jquery-ui.css

jquery-ui.css

7 ms

jquery-ui.js

jquery-ui.js

9 ms

shadows.css

shadows.css

2967 ms

views_slideshow_controls_text.css

views_slideshow_controls_text.css

3153 ms

views_slideshow_cycle.css

views_slideshow_cycle.css

3169 ms

unsemantic-grid-responsive-tablet.css

unsemantic-grid-responsive-tablet.css

3864 ms

normalize.css

normalize.css

3158 ms

stylesheet.css

stylesheet.css

3178 ms

font-awesome.min.css

font-awesome.min.css

3182 ms

mediaquery.css

mediaquery.css

2886 ms

css_injector_1.css

css_injector_1.css

2931 ms

css_injector_2.css

css_injector_2.css

2950 ms

css_injector_3.css

css_injector_3.css

3130 ms

css_injector_5.css

css_injector_5.css

3665 ms

css_injector_6.css

css_injector_6.css

3160 ms

css_injector_9.css

css_injector_9.css

2955 ms

css_injector_10.css

css_injector_10.css

3144 ms

css_injector_11.css

css_injector_11.css

2978 ms

css_injector_12.css

css_injector_12.css

3117 ms

unsemantic-grid-desktop.css

unsemantic-grid-desktop.css

3415 ms

js_injector_5.js

js_injector_5.js

3165 ms

logo.png

logo.png

252 ms

menu-dot.gif

menu-dot.gif

482 ms

search-icon.gif

search-icon.gif

481 ms

sb-icon-step1.png

sb-icon-step1.png

487 ms

sb-icon-step2.png

sb-icon-step2.png

490 ms

sb-icon-step3.png

sb-icon-step3.png

502 ms

ent-icon-step1.png

ent-icon-step1.png

742 ms

ent-icon-step2.png

ent-icon-step2.png

1201 ms

ent-icon-step3.png

ent-icon-step3.png

979 ms

FlexiLong%5B2%5D_0_0.png

FlexiLong%5B2%5D_0_0.png

3158 ms

TIME_desktop_enterprise_0.jpg

TIME_desktop_enterprise_0.jpg

2733 ms

Homepage_banner_0.jpg

Homepage_banner_0.jpg

1696 ms

TIME_banner_personal_0.jpg

TIME_banner_personal_0.jpg

2168 ms

TIME_banner_small-business_1.jpg

TIME_banner_small-business_1.jpg

2668 ms

Carrier-mobile%20%281%29_0.png

Carrier-mobile%20%281%29_0.png

2917 ms

TIME_mobile_enterprise_0.jpg

TIME_mobile_enterprise_0.jpg

2947 ms

TIME_banners_Brand_personal_0.jpg

TIME_banners_Brand_personal_0.jpg

3389 ms

TIME_banners_Brand_home_0.png

TIME_banners_Brand_home_0.png

3642 ms

TIME_banner_small-business_0_0.jpg

TIME_banner_small-business_0_0.jpg

3977 ms

business-icon-map-grey.png

business-icon-map-grey.png

3395 ms

MEF_logo_footer.jpg

MEF_logo_footer.jpg

3432 ms

footer_gst.png

footer_gst.png

3655 ms

timefooterlogo.jpg

timefooterlogo.jpg

3873 ms

din-light-webfont.woff

din-light-webfont.woff

4071 ms

din-condensed-webfont.woff

din-condensed-webfont.woff

4122 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

4558 ms

arrow-plain.png

arrow-plain.png

4104 ms

navi.png

navi.png

4315 ms

dot.gif

dot.gif

4428 ms

highlight-bg.gif

highlight-bg.gif

4542 ms

Selfcare_Laptop.png

Selfcare_Laptop.png

4593 ms

support_homepage.png

support_homepage.png

5309 ms

arrow.png

arrow.png

4791 ms

Unresolved.png

Unresolved.png

4912 ms

gtm.js

gtm.js

72 ms

7659 ms

down-white.png

down-white.png

503 ms

din-bold-webfont.woff

din-bold-webfont.woff

5206 ms

analytics.js

analytics.js

20 ms

collect

collect

11 ms

collect

collect

67 ms

down-white.png

down-white.png

4490 ms

Accessibility Review

time.com.my accessibility score

62

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

time.com.my best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

time.com.my SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.

Social Sharing Optimization

time.com.my

Open Graph description is not detected on the main page of 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: