8.9 sec in total
1.2 sec
7.4 sec
241 ms
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.jpWe analyzed Evex.jp page load time and found that the first response time was 1.2 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 85% of websites can load faster.
evex.jp performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value6.0 s
13/100
25%
Value8.9 s
15/100
10%
Value1,170 ms
22/100
30%
Value0
100/100
15%
Value7.5 s
48/100
10%
1181 ms
963 ms
573 ms
403 ms
22 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 69% of them (47 requests) were addressed to the original Evex.jp, 16% (11 requests) were made to Test.n-plus.biz and 4% (3 requests) were made to D3pj3vgx4ijpjx.cloudfront.net. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Evex.jp.
Page size can be reduced by 387.5 kB (8%)
4.9 MB
4.5 MB
In fact, the total size of Evex.jp main page is 4.9 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. 70% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 19.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 5.0 kB, which is 20% 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 19.0 kB or 76% of the original size.
Potential reduce by 208.8 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. Evex images are well optimized though.
Potential reduce by 124.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 124.5 kB or 62% of the original size.
Potential reduce by 35.3 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.
Number of requests can be reduced by 24 (46%)
52
28
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
evex.jp
1181 ms
common.css
963 ms
flexslider.css
573 ms
jquery.jscrollpane.css
403 ms
css
22 ms
modernizr-2.6.2.min.js
813 ms
jquery-1.10.1.min.js
1497 ms
plugin.js
576 ms
common.js
651 ms
jquery.flexslider-min.js
958 ms
jquery.mousewheel.js
591 ms
jquery.jscrollpane.min.js
977 ms
colorbox.css
825 ms
jquery.colorbox-min.js
1057 ms
php_date.js
979 ms
typesquare.js
211 ms
css
21 ms
compass
253 ms
ga.js
428 ms
pic01_def.jpg
2166 ms
pic02_def.jpg
2167 ms
pic03_def.jpg
2167 ms
pic04_def.jpg
2167 ms
pic05_def.jpg
2174 ms
pic06_def.jpg
2168 ms
pic07_def.jpg
2169 ms
pic08_def.jpg
2170 ms
pic09_def.jpg
2170 ms
pic10_def.jpg
2170 ms
pic11_def.jpg
2172 ms
icon_key.png
1763 ms
logo.png
1751 ms
head_txt01.png
1748 ms
arrow01_green.png
1743 ms
slide01.jpg
2958 ms
slide02.jpg
2241 ms
slide03.jpg
2479 ms
slide04.jpg
2884 ms
slide05.jpg
4473 ms
slide06.jpg
2590 ms
pagetop_def.gif
2422 ms
side_btn05.jpg
2616 ms
arrow01_whi.png
2680 ms
side_btn04_off.jpg
2793 ms
arrow01_whi_off.png
2814 ms
side_btn02.jpg
2887 ms
side_btn03.jpg
2991 ms
side_btn01.jpg
3016 ms
sidetitle01.gif
1334 ms
banner_hy_stex.gif
1375 ms
banner_nplus.gif
1422 ms
banner_nano.gif
1456 ms
banner_satex.gif
1474 ms
banner_fsys.gif
1554 ms
banner_fsj.gif
1575 ms
banner_ff.gif
1833 ms
__utm.gif
463 ms
187TYb8ysVvxar86IcDsZ_esZW2xOQ-xsNqO47m55DA.ttf
463 ms
twitter.php
784 ms
foot_logo.png
1155 ms
controls.png
1192 ms
border.png
1259 ms
gnavi_current_arrow.png
1281 ms
mkfont
151 ms
mkfont
131 ms
ab.woff
35 ms
slider_nav_prev.png
195 ms
slider_nav_next.png
194 ms
evex.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
evex.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
evex.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
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 matches the claimed 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.
evex.jp
Open Graph data is detected on the main page of Evex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: