Tools & Wizards About Us
proton.co.jp screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

proton.co.jp

PROTON　Satria Neo （プロトン サトリアネオ）

Page Load Speed

5 sec in total

First Response

924 ms

Resources Loaded

3.8 sec

Page Rendered

297 ms

proton.co.jp screenshot

About Website

Welcome to proton.co.jp homepage info - get ready to check PROTON best content for Japan right away, or after learning these important things about proton.co.jp

私どもプロトンは、モータースポーツを愛するマレーシア最大の自動車メーカーです。日本国内に希少となってしまったコストパフォーマンスに優れるコンパクトスポーツというジャンルを、もう一度盛り上げたいと思い、サトリアネオの日本正規販売を開始致しました。

Visit proton.co.jp

Key Findings

We analyzed Proton.co.jp page load time and found that the first response time was 924 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

proton.co.jp performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

proton.co.jp

924 ms

common.css

340 ms

default.js

506 ms

swfobject.js

522 ms

jquery-1.5.1.min.js

1056 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 96% of them (54 requests) were addressed to the original Proton.co.jp, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Proton.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.7 kB (7%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Proton.co.jp main page is 1.7 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. 30% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 11.3 kB

  • Original 15.8 kB
  • After minification 15.1 kB
  • After compression 4.5 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 11.3 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 6.4 kB

  • Original 1.5 MB
  • After minification 1.5 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. PROTON images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 89.6 kB

  • Original 148.2 kB
  • After minification 143.5 kB
  • After compression 58.6 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 89.6 kB or 60% of the original size.

CSS Optimization

-82%

Potential reduce by 18.4 kB

  • Original 22.5 kB
  • After minification 15.3 kB
  • After compression 4.1 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. Proton.co.jp needs all CSS files to be minified and compressed as it can save up to 18.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (24%)

Requests Now

54

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

proton.co.jp

proton.co.jp

924 ms

common.css

common.css

340 ms

default.js

default.js

506 ms

swfobject.js

swfobject.js

522 ms

jquery-1.5.1.min.js

jquery-1.5.1.min.js

1056 ms

ticker.js

ticker.js

379 ms

jquery.bxSlider.min.js

jquery.bxSlider.min.js

841 ms

dropdown.js

dropdown.js

549 ms

layout.css

layout.css

231 ms

font_px.css

font_px.css

337 ms

spacer.css

spacer.css

357 ms

Header.css

Header.css

187 ms

Gnavi.css

Gnavi.css

191 ms

Container.css

Container.css

274 ms

Footer.css

Footer.css

301 ms

ga.js

ga.js

62 ms

body_back01.jpg

body_back01.jpg

186 ms

header_back01.jpg

header_back01.jpg

176 ms

logo.png

logo.png

379 ms

gnavi01_foff.jpg

gnavi01_foff.jpg

173 ms

gnavi02_foff.jpg

gnavi02_foff.jpg

179 ms

dropdown.gif

dropdown.gif

171 ms

gnavi03a_foff.jpg

gnavi03a_foff.jpg

337 ms

gnavi04_foff.jpg

gnavi04_foff.jpg

338 ms

gnavi05a_foff.jpg

gnavi05a_foff.jpg

344 ms

banner07.jpg

banner07.jpg

1055 ms

banner08.jpg

banner08.jpg

1476 ms

banner09.jpg

banner09.jpg

1346 ms

banner05.jpg

banner05.jpg

1009 ms

banner06.jpg

banner06.jpg

864 ms

news_back.jpg

news_back.jpg

561 ms

top_tit_news.jpg

top_tit_news.jpg

751 ms

impressions_back.jpg

impressions_back.jpg

941 ms

top_tit_impressions.jpg

top_tit_impressions.jpg

1038 ms

top_img01.jpg

top_img01.jpg

1697 ms

footer_back01.jpg

footer_back01.jpg

1177 ms

footer_back01.jpg

footer_back01.jpg

1211 ms

fnavi01_off.jpg

fnavi01_off.jpg

1227 ms

fnavi03_off.jpg

fnavi03_off.jpg

1344 ms

fnavi04_off.jpg

fnavi04_off.jpg

1385 ms

fnavi_recycle_off.jpg

fnavi_recycle_off.jpg

1402 ms

fnavi06_off.jpg

fnavi06_off.jpg

1510 ms

fnavi07_off.jpg

fnavi07_off.jpg

1511 ms

footer_copy.jpg

footer_copy.jpg

1558 ms

__utm.gif

__utm.gif

15 ms

gnavi01_fon.jpg

gnavi01_fon.jpg

187 ms

gnavi02_fon.jpg

gnavi02_fon.jpg

176 ms

gnavi03a_fon.jpg

gnavi03a_fon.jpg

190 ms

gnavi04_fon.jpg

gnavi04_fon.jpg

173 ms

gnavi05a_fon.jpg

gnavi05a_fon.jpg

180 ms

fnavi01_on.jpg

fnavi01_on.jpg

173 ms

fnavi03_on.jpg

fnavi03_on.jpg

342 ms

fnavi04_on.jpg

fnavi04_on.jpg

341 ms

fnavi_recycle_on.jpg

fnavi_recycle_on.jpg

347 ms

fnavi06_on.jpg

fnavi06_on.jpg

354 ms

fnavi07_on.jpg

fnavi07_on.jpg

369 ms

Accessibility Review

proton.co.jp accessibility score

72

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

Image elements do not have [alt] attributes

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

proton.co.jp best practices score

58

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

SEO Factors

proton.co.jp 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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proton.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Proton.co.jp 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

proton.co.jp

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