Tools & Wizards About Us
vecc.co.jp screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

vecc.co.jp

打刻式マーキング装置（刻印機）の開発・設計・販売・サービス｜ベクトル株式会社

Page Load Speed

8.3 sec in total

First Response

619 ms

Resources Loaded

7.5 sec

Page Rendered

189 ms

vecc.co.jp screenshot

About Website

Welcome to vecc.co.jp homepage info - get ready to check Vecc best content right away, or after learning these important things about vecc.co.jp

マーキング装置の生産管理からトレーサビリティへ。お客様より高い支持を頂いているベクトルは、お客間のニーズに合わせ装置・周辺機器問わず幅広い開発を手掛けています。

Visit vecc.co.jp

Key Findings

We analyzed Vecc.co.jp page load time and found that the first response time was 619 ms 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.

Performance Metrics

vecc.co.jp performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

vecc.co.jp

619 ms

index.shtml

895 ms

bace.css

554 ms

top.css

383 ms

superfish.css

385 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Vecc.co.jp, 85% (33 requests) were made to Vecc.jp and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.4 sec) relates to the external source Vecc.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.2 kB (10%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vecc.co.jp 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. 15% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 13.9 kB

  • Original 17.5 kB
  • After minification 16.4 kB
  • After compression 3.7 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 13.9 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 36.3 kB

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

JavaScript Optimization

-65%

Potential reduce by 48.4 kB

  • Original 74.0 kB
  • After minification 66.0 kB
  • After compression 25.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 48.4 kB or 65% of the original size.

CSS Optimization

-77%

Potential reduce by 11.7 kB

  • Original 15.1 kB
  • After minification 12.0 kB
  • After compression 3.5 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. Vecc.co.jp needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (14%)

Requests Now

36

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vecc.co.jp

vecc.co.jp

619 ms

index.shtml

index.shtml

895 ms

bace.css

bace.css

554 ms

top.css

top.css

383 ms

superfish.css

superfish.css

385 ms

jquery.min.js

jquery.min.js

78 ms

jquery-jqir.js

jquery-jqir.js

371 ms

yuga.js

yuga.js

717 ms

superfish.js

superfish.js

878 ms

javas_top.js

javas_top.js

733 ms

analytics.js

analytics.js

78 ms

top_bana_all.jpg

top_bana_all.jpg

2829 ms

top_bana_01on.jpg

top_bana_01on.jpg

1339 ms

top_bana_02on.jpg

top_bana_02on.jpg

1829 ms

top_bana_03on.jpg

top_bana_03on.jpg

2742 ms

top_bana_04on.jpg

top_bana_04on.jpg

3345 ms

top_bana_05on.jpg

top_bana_05on.jpg

3100 ms

top_bana_06on.jpg

top_bana_06on.jpg

2761 ms

background.jpg

background.jpg

2184 ms

top_catch.jpg

top_catch.jpg

4490 ms

header_cursol.png

header_cursol.png

3108 ms

nav_back.png

nav_back.png

3117 ms

nav_all.png

nav_all.png

3718 ms

h4_back.jpg

h4_back.jpg

3458 ms

go_history.png

go_history.png

3463 ms

top_bana_new_on.jpg

top_bana_new_on.jpg

4586 ms

form_cursol.png

form_cursol.png

3700 ms

download_on.png

download_on.png

4193 ms

testmarking_on.png

testmarking_on.png

4383 ms

receipt_on.png

receipt_on.png

4413 ms

footer_back.jpg

footer_back.jpg

4263 ms

logo.png

logo.png

4727 ms

download.png

download.png

4979 ms

testmarking.png

testmarking.png

5261 ms

receipt.png

receipt.png

5124 ms

top_bana_new.jpg

top_bana_new.jpg

5375 ms

collect

collect

3 ms

collect

collect

58 ms

ga-audiences

ga-audiences

35 ms

Accessibility Review

vecc.co.jp accessibility score

50

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

vecc.co.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

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

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vecc.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vecc.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

vecc.co.jp

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