Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 0

    Best Practices

  • 84

    SEO

    Google-friendlier than
    53% of websites

evex.jp

EVと工作機械 – 電気自動車で活用される工作機械の需要と動向

Page Load Speed

1.5 sec in total

First Response

726 ms

Resources Loaded

727 ms

Page Rendered

0 ms

evex.jp screenshot

About Website

Visit evex.jp now to see the best up-to-date Evex content and also check out these interesting facts you probably never knew about evex.jp

工作機械市場の約30%と大きなシェアを占める「自動車業界」。 自動車にはおよそ2万点の部品が使われており、運動性能や燃費をあげるため精度の高い金属加工がかかせません。 しかし今、「CASE」とよばれる […]

Visit evex.jp

Key Findings

We analyzed Evex.jp page load time and found that the first response time was 726 ms and then it took 727 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

evex.jp performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

26/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

evex.jp

726 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Evex.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (726 ms) belongs to the original domain Evex.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 369.4 kB (8%)

Content Size

4.9 MB

After Optimization

4.5 MB

In fact, the total size of Evex.jp main page is 4.9 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-56%

Potential reduce by 837 B

  • Original 1.5 kB
  • After minification 1.5 kB
  • After compression 660 B

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 837 B or 56% of the original size.

Image Optimization

-5%

Potential reduce by 208.8 kB

  • Original 4.6 MB
  • After minification 4.4 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. Evex images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 124.5 kB

  • Original 201.7 kB
  • After minification 189.4 kB
  • After compression 77.3 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 124.5 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 35.3 kB

  • Original 42.3 kB
  • After minification 30.3 kB
  • After compression 7.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. Evex.jp needs all CSS files to be minified and compressed as it can save up to 35.3 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

evex.jp accessibility score

79

Accessibility Issues

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.

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

Links do not have a discernible name

SEO Factors

evex.jp SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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