Tools & Wizards About Us
inokom.com.my screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

inokom.com.my

Inokom Corporation Sdn. Bhd.

Page Load Speed

8.6 sec in total

First Response

1.7 sec

Resources Loaded

6.7 sec

Page Rendered

190 ms

inokom.com.my screenshot

About Website

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

A subsidiary of Sime Darby Motors

Visit inokom.com.my

Key Findings

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

Performance Metrics

inokom.com.my performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

www.inokom.com.my

1650 ms

wp-emoji-release.min.js

518 ms

pagenavi-css.css

505 ms

css

53 ms

style.css

1018 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 89% of them (33 requests) were addressed to the original Inokom.com.my, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Inokom.com.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 266.4 kB (23%)

Content Size

1.1 MB

After Optimization

874.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inokom.com.my main page is 1.1 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. 25% of websites need less resources to load. Images take 778.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 25.2 kB

  • Original 31.2 kB
  • After minification 29.3 kB
  • After compression 6.0 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 25.2 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 5.7 kB

  • Original 778.0 kB
  • After minification 772.4 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. Inokom images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 126.0 kB

  • Original 203.6 kB
  • After minification 194.0 kB
  • After compression 77.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 126.0 kB or 62% of the original size.

CSS Optimization

-85%

Potential reduce by 109.6 kB

  • Original 128.3 kB
  • After minification 104.9 kB
  • After compression 18.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. Inokom.com.my needs all CSS files to be minified and compressed as it can save up to 109.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (65%)

Requests Now

34

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inokom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.inokom.com.my

www.inokom.com.my

1650 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

518 ms

pagenavi-css.css

pagenavi-css.css

505 ms

css

css

53 ms

style.css

style.css

1018 ms

shortcodes.css

shortcodes.css

764 ms

shortcodes_responsive.css

shortcodes_responsive.css

520 ms

advanced-recent-posts-widget.css

advanced-recent-posts-widget.css

524 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

757 ms

page_templates.css

page_templates.css

783 ms

jquery.js

jquery.js

1554 ms

jquery-migrate.min.js

jquery-migrate.min.js

786 ms

external-tracking.min.js

external-tracking.min.js

1011 ms

jquery.min.js

jquery.min.js

54 ms

jquery.webticker.js

jquery.webticker.js

1030 ms

webticker.css

webticker.css

1089 ms

superfish.js

superfish.js

809 ms

jquery.fitvids.js

jquery.fitvids.js

1022 ms

modernizr-min.js

modernizr-min.js

1029 ms

custom.js

custom.js

1045 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

1073 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

1116 ms

et-ptemplates-frontend.js

et-ptemplates-frontend.js

1277 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1374 ms

ga.js

ga.js

40 ms

header-gradient.png

header-gradient.png

273 ms

logo.png

logo.png

529 ms

icon-email.png

icon-email.png

258 ms

icon-rss.png

icon-rss.png

260 ms

santa-fe-homepage.jpg

santa-fe-homepage.jpg

1063 ms

elantra02_1280x960.jpg

elantra02_1280x960.jpg

2553 ms

homefooter-gradient.png

homefooter-gradient.png

526 ms

lucida_sans-webfont.woff

lucida_sans-webfont.woff

494 ms

lucida_sans_demibold-webfont.woff

lucida_sans_demibold-webfont.woff

519 ms

__utm.gif

__utm.gif

13 ms

slider_left_arrow.png

slider_left_arrow.png

745 ms

slider_right_arrow.png

slider_right_arrow.png

743 ms

Accessibility Review

inokom.com.my accessibility score

57

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

inokom.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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

inokom.com.my SEO score

67

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 Inokom.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 Inokom.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

inokom.com.my

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