Tools & Wizards About Us
vec.gr.jp screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

vec.gr.jp

塩ビ工業・環境協会（VEC）トップページ

Page Load Speed

5.8 sec in total

First Response

506 ms

Resources Loaded

4.3 sec

Page Rendered

998 ms

vec.gr.jp screenshot

About Website

Click here to check amazing VEC content for Japan. Otherwise, check out these important facts you probably never knew about vec.gr.jp

塩化ビニル工業及び製品に関する環境、安全に係る諸問題の調査・研究を行い、塩化ビニルに関する正しい理解の普及を図るとともに、生産、技術、流通、消費等の調査・研究を行い、さらに、リサイクル推進の為の技術開発、調査研究を行い、塩化ビニル工業の健全な発展に寄与することを目的としています。

Visit vec.gr.jp

Key Findings

We analyzed Vec.gr.jp page load time and found that the first response time was 506 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

vec.gr.jp performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value470 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

vec.gr.jp

506 ms

www.vec.gr.jp

1050 ms

js

72 ms

html5reset-1.6.1.css

503 ms

common.css

509 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 79% of them (60 requests) were addressed to the original Vec.gr.jp, 7% (5 requests) were made to Google.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Vec.gr.jp.

Page Optimization Overview & Recommendations

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

Content Size

4.2 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vec.gr.jp main page is 4.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. 65% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 46.5 kB

  • Original 55.5 kB
  • After minification 41.8 kB
  • After compression 8.9 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 13.7 kB, which is 25% 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 46.5 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 205.8 kB

  • Original 3.8 MB
  • After minification 3.6 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. VEC images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 15.2 kB

  • Original 212.9 kB
  • After minification 206.6 kB
  • After compression 197.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

-62%

Potential reduce by 42.7 kB

  • Original 68.8 kB
  • After minification 52.9 kB
  • After compression 26.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. Vec.gr.jp needs all CSS files to be minified and compressed as it can save up to 42.7 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (45%)

Requests Now

71

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vec.gr.jp

vec.gr.jp

506 ms

www.vec.gr.jp

www.vec.gr.jp

1050 ms

js

js

72 ms

html5reset-1.6.1.css

html5reset-1.6.1.css

503 ms

common.css

common.css

509 ms

base_style.css

base_style.css

676 ms

index_style.css

index_style.css

680 ms

jquery.min.js

jquery.min.js

33 ms

css

css

49 ms

all.css

all.css

45 ms

cse.js

cse.js

57 ms

js

js

45 ms

js

js

83 ms

toglemenu.js

toglemenu.js

178 ms

currentnav.js

currentnav.js

338 ms

smoothScroll.js

smoothScroll.js

344 ms

pagetop.js

pagetop.js

401 ms

jquery.accordion.js

jquery.accordion.js

564 ms

tracking-pdf.js

tracking-pdf.js

563 ms

vec_logo.svg

vec_logo.svg

196 ms

pvcaward2023.svg

pvcaward2023.svg

197 ms

icon_english.svg

icon_english.svg

193 ms

icon_contact.svg

icon_contact.svg

191 ms

icon_info.svg

icon_info.svg

302 ms

icon_about.svg

icon_about.svg

303 ms

icon_environment.svg

icon_environment.svg

338 ms

icon_kenzai.svg

icon_kenzai.svg

340 ms

icon_recycle.svg

icon_recycle.svg

341 ms

icon_safety.svg

icon_safety.svg

342 ms

icon_library.svg

icon_library.svg

469 ms

icon_statistics.svg

icon_statistics.svg

472 ms

webmedia_add_02.jpg

webmedia_add_02.jpg

842 ms

webmedia_add_01.jpg

webmedia_add_01.jpg

841 ms

newsletter.png

newsletter.png

507 ms

pamphlet_01.jpg

pamphlet_01.jpg

673 ms

pamphlet_06.jpg

pamphlet_06.jpg

803 ms

pamphlet_02.jpg

pamphlet_02.jpg

805 ms

pamphlet_11.jpg

pamphlet_11.jpg

1012 ms

movie_new_01.png

movie_new_01.png

1349 ms

movie_new_02.png

movie_new_02.png

1140 ms

pvc_news.png

pvc_news.png

1140 ms

icon_info_blue.svg

icon_info_blue.svg

1007 ms

icon_about_blue.svg

icon_about_blue.svg

1009 ms

icon_environment_blue.svg

icon_environment_blue.svg

1177 ms

icon_kenzai_blue.svg

icon_kenzai_blue.svg

1179 ms

icon_recycle_blue.svg

icon_recycle_blue.svg

1180 ms

icon_safety_blue.svg

icon_safety_blue.svg

1309 ms

icon_library_blue.svg

icon_library_blue.svg

1307 ms

icon_statistics_blue.svg

icon_statistics_blue.svg

1344 ms

movie_01.jpg

movie_01.jpg

1513 ms

museum.jpg

museum.jpg

1514 ms

eternal_link01.jpg

eternal_link01.jpg

1458 ms

fa-solid-900.woff

fa-solid-900.woff

18 ms

fa-regular-400.woff

fa-regular-400.woff

32 ms

eternal_link02.jpg

eternal_link02.jpg

1456 ms

cse_element__ja.js

cse_element__ja.js

42 ms

default+ja.css

default+ja.css

95 ms

default.css

default.css

97 ms

eternal_link03.jpg

eternal_link03.jpg

1331 ms

eternal_link04.jpg

eternal_link04.jpg

1330 ms

mainv_01.jpg

mainv_01.jpg

1627 ms

mainv_02.jpg

mainv_02.jpg

1625 ms

mainv_03.jpg

mainv_03.jpg

1661 ms

pxidypY1o9NHyXh3WvSbGSggdOeMaEluqGao.ttf

pxidypY1o9NHyXh3WvSbGSggdOeMaEluqGao.ttf

62 ms

mainv_04.jpg

mainv_04.jpg

2166 ms

async-ads.js

async-ads.js

39 ms

branding.png

branding.png

28 ms

clear.png

clear.png

24 ms

mainv_05.jpg

mainv_05.jpg

1555 ms

mainv_06.jpg

mainv_06.jpg

1387 ms

mainv_07.jpg

mainv_07.jpg

1519 ms

mainv_08.jpg

mainv_08.jpg

1815 ms

sec01_03.jpg

sec01_03.jpg

1647 ms

sec01_02.jpg

sec01_02.jpg

1683 ms

sec01_01.jpg

sec01_01.jpg

1556 ms

icon_newwin.svg

icon_newwin.svg

1555 ms

Accessibility Review

vec.gr.jp accessibility score

85

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

Links do not have a discernible name

Best Practices

vec.gr.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

vec.gr.jp SEO score

91

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vec.gr.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 Vec.gr.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

vec.gr.jp

Open Graph data is detected on the main page of VEC. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: