Tools & Wizards About Us
mykomatsu.komatsu screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    38% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

mykomatsu.komatsu

My Komatsu – Remote Fleet Management and Komatsu Parts Ordering

Page Load Speed

9.5 sec in total

First Response

1.7 sec

Resources Loaded

7.4 sec

Page Rendered

271 ms

mykomatsu.komatsu screenshot

About Website

Visit mykomatsu.komatsu now to see the best up-to-date My Komatsu content and also check out these interesting facts you probably never knew about mykomatsu.komatsu

My Komatsu, the online solution for remote fleet management, helps you order Komatsu parts quickly and easily, in order to increase machine uptime.

Visit mykomatsu.komatsu

Key Findings

We analyzed Mykomatsu.komatsu page load time and found that the first response time was 1.7 sec and then it took 7.7 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

mykomatsu.komatsu performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value14.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value44.2 s

0/100

25%

SI (Speed Index)

Value19.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.082

94/100

15%

TTI (Time to Interactive)

Value33.1 s

0/100

10%

Network Requests Diagram

mykomatsu.komatsu

1748 ms

gtm.js

144 ms

css

250 ms

modernizr

242 ms

js

1740 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 55% of them (44 requests) were addressed to the original Mykomatsu.komatsu, 14% (11 requests) were made to Komatsu.com and 6% (5 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Mykomatsu.komatsu.

Page Optimization Overview & Recommendations

Page size can be reduced by 344.1 kB (4%)

Content Size

9.2 MB

After Optimization

8.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mykomatsu.komatsu main page is 9.2 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. Only a small number of websites need less resources to load. Images take 8.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 73.9 kB

  • Original 89.9 kB
  • After minification 74.5 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 15.4 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 73.9 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 255.2 kB

  • Original 8.9 MB
  • After minification 8.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. My Komatsu images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 11.6 kB

  • Original 153.3 kB
  • After minification 153.3 kB
  • After compression 141.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 3.4 kB

  • Original 49.0 kB
  • After minification 49.0 kB
  • After compression 45.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. Mykomatsu.komatsu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (51%)

Requests Now

67

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mykomatsu.komatsu

mykomatsu.komatsu

1748 ms

gtm.js

gtm.js

144 ms

css

css

250 ms

modernizr

modernizr

242 ms

js

js

1740 ms

js

js

2584 ms

owl.carousel.min.css

owl.carousel.min.css

1467 ms

owl.carousel.min.js

owl.carousel.min.js

1466 ms

timeout-dialog.css

timeout-dialog.css

1458 ms

botchat.css

botchat.css

1464 ms

hubs

hubs

1615 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

1637 ms

timeout-dialog.js

timeout-dialog.js

1627 ms

browsercompatibility.jsv=10.10.22

browsercompatibility.jsv=10.10.22

1464 ms

ecommerceScript.js

ecommerceScript.js

1634 ms

ecommerceGuestScript.js

ecommerceGuestScript.js

1634 ms

BotApp.js

BotApp.js

1623 ms

analytics.js

analytics.js

1264 ms

collect

collect

998 ms

komatsu-locator

komatsu-locator

315 ms

MyKomatsuLogo.png

MyKomatsuLogo.png

163 ms

cart-blue.svg

cart-blue.svg

161 ms

locatore.svg

locatore.svg

156 ms

Banner%20Devices.png

Banner%20Devices.png

315 ms

Banner%20FleetMngmt.png

Banner%20FleetMngmt.png

323 ms

Banner%20Parts%20Machine.png

Banner%20Parts%20Machine.png

159 ms

banner-1.png

banner-1.png

164 ms

banner-2.png

banner-2.png

180 ms

banner-3.png

banner-3.png

312 ms

KOM0327%20Landing%20Page%20Parts%20Banner.png

KOM0327%20Landing%20Page%20Parts%20Banner.png

318 ms

excavator.png

excavator.png

182 ms

bulldozer.png

bulldozer.png

181 ms

wheel_loader.png

wheel_loader.png

160 ms

articulated_truck.png

articulated_truck.png

223 ms

rigid_truck_(mechanical).png

rigid_truck_(mechanical).png

246 ms

rigid_truck_(electric_drive).png

rigid_truck_(electric_drive).png

246 ms

motor_grader.png

motor_grader.png

246 ms

utility_products.png

utility_products.png

242 ms

crusher.png

crusher.png

241 ms

ai.0.js

ai.0.js

230 ms

icomoon.ttf

icomoon.ttf

135 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

132 ms

1019 ms

DejaVuSans.ttf

DejaVuSans.ttf

55 ms

DejaVuSans.ttf

DejaVuSans.ttf

53 ms

DejaVuSans-Bold.ttf

DejaVuSans-Bold.ttf

55 ms

or.png

or.png

15 ms

print.css

print.css

24 ms

conversations

conversations

125 ms

gtm.js

gtm.js

56 ms

main.css

main.css

32 ms

webrotate.css

webrotate.css

88 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

211 ms

imagerotator.js

imagerotator.js

243 ms

js

js

108 ms

main.bundle-min.js

main.bundle-min.js

105 ms

19f685a7014943989db3b3fb0cc598bf

19f685a7014943989db3b3fb0cc598bf

422 ms

js

js

235 ms

hotjar-2640255.js

hotjar-2640255.js

233 ms

collect

collect

209 ms

NotoSans-Regular.ttf

NotoSans-Regular.ttf

208 ms

NotoSans-Medium.woff

NotoSans-Medium.woff

205 ms

NotoSans-Light.woff

NotoSans-Light.woff

207 ms

NotoSans-Bold.woff

NotoSans-Bold.woff

207 ms

iframe_api

iframe_api

223 ms

gen_204

gen_204

108 ms

otSDKStub.js

otSDKStub.js

106 ms

modules.bcd9ade6b0bb9bdd0789.js

modules.bcd9ade6b0bb9bdd0789.js

92 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

53 ms

www-widgetapi.js

www-widgetapi.js

48 ms

be79d321-ce54-423d-8f8a-59f843d8e7d4.json

be79d321-ce54-423d-8f8a-59f843d8e7d4.json

37 ms

location

location

62 ms

pd.js

pd.js

54 ms

negotiate

negotiate

30 ms

otBannerSdk.js

otBannerSdk.js

12 ms

analytics

analytics

202 ms

en.json

en.json

100 ms

track

track

29 ms

start

start

12 ms

otPcTab.json

otPcTab.json

30 ms

Accessibility Review

mykomatsu.komatsu accessibility score

61

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 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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

mykomatsu.komatsu best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

mykomatsu.komatsu SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

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 Mykomatsu.komatsu 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 Mykomatsu.komatsu 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

mykomatsu.komatsu

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