Tools & Wizards About Us
viax.co.jp screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% 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

  • 100

    SEO

    Google-friendlier than
    94% of websites

viax.co.jp

図書館運営・DM発送・制作・印刷・Web制作の総合代理店　ヴィアックス

Page Load Speed

7.8 sec in total

First Response

556 ms

Resources Loaded

7 sec

Page Rendered

246 ms

viax.co.jp screenshot

About Website

Click here to check amazing Viax content for Japan. Otherwise, check out these important facts you probably never knew about viax.co.jp

株式会社ヴィアックスは、ダイレクトマーケティング、図書館運営、DM発送・制作・印刷・Web制作に関する総合代理店です。DM制作・印刷・発送・管理までワンストップでの提供が可能。即日お見積いたします。

Visit viax.co.jp

Key Findings

We analyzed Viax.co.jp page load time and found that the first response time was 556 ms and then it took 7.2 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

viax.co.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.315

37/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

viax.co.jp

556 ms

www.viax.co.jp

1462 ms

common.css

376 ms

meanmenu.css

491 ms

flexslider.css

495 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 97% of them (69 requests) were addressed to the original Viax.co.jp, 1% (1 request) were made to Maps.google.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Viax.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 514.7 kB (12%)

Content Size

4.2 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 18.0 kB

  • Original 24.0 kB
  • After minification 20.6 kB
  • After compression 6.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 3.4 kB, which is 14% 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 18.0 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 79.7 kB

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

JavaScript Optimization

-53%

Potential reduce by 139.0 kB

  • Original 262.4 kB
  • After minification 229.7 kB
  • After compression 123.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 139.0 kB or 53% of the original size.

CSS Optimization

-89%

Potential reduce by 278.0 kB

  • Original 311.6 kB
  • After minification 256.8 kB
  • After compression 33.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. Viax.co.jp needs all CSS files to be minified and compressed as it can save up to 278.0 kB or 89% of the original size.

Requests Breakdown

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

Requests Now

69

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

viax.co.jp

viax.co.jp

556 ms

www.viax.co.jp

www.viax.co.jp

1462 ms

common.css

common.css

376 ms

meanmenu.css

meanmenu.css

491 ms

flexslider.css

flexslider.css

495 ms

wp-content.css

wp-content.css

528 ms

jquery.js

jquery.js

1236 ms

jquery.meanmenu.js

jquery.meanmenu.js

563 ms

heightLine.js

heightLine.js

564 ms

jquery.flexslider.js

jquery.flexslider.js

978 ms

pc-footer.js

pc-footer.js

657 ms

accordion.js

accordion.js

702 ms

common.js

common.js

751 ms

js

js

68 ms

pagenavi-css.css

pagenavi-css.css

751 ms

js

js

68 ms

mapstyle.js

mapstyle.js

638 ms

wp-embed.min.js

wp-embed.min.js

695 ms

base.css

base.css

566 ms

style.css

style.css

1511 ms

print.css

print.css

941 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

190 ms

backshadow.png

backshadow.png

166 ms

slideimg01_sp.jpg

slideimg01_sp.jpg

1466 ms

slideimg02_sp.jpg

slideimg02_sp.jpg

1411 ms

newsicon.png

newsicon.png

189 ms

img_01.jpg

img_01.jpg

701 ms

open.png

open.png

330 ms

img_02.jpg

img_02.jpg

375 ms

img_03.jpg

img_03.jpg

751 ms

img16_sp.jpg

img16_sp.jpg

986 ms

img15_sp.jpg

img15_sp.jpg

564 ms

img14_sp.jpg

img14_sp.jpg

754 ms

img13_sp.jpg

img13_sp.jpg

1051 ms

img09_sp.jpg

img09_sp.jpg

1125 ms

img04_sp.jpg

img04_sp.jpg

944 ms

img10_sp.jpg

img10_sp.jpg

1134 ms

img12_sp.jpg

img12_sp.jpg

1315 ms

img20_sp.jpg

img20_sp.jpg

1403 ms

img08_sp.jpg

img08_sp.jpg

1313 ms

img18_sp.jpg

img18_sp.jpg

1323 ms

img19_sp.jpg

img19_sp.jpg

1688 ms

img22_sp.jpg

img22_sp.jpg

1480 ms

img11_sp.jpg

img11_sp.jpg

1512 ms

img21_sp.jpg

img21_sp.jpg

1578 ms

listicon.png

listicon.png

1586 ms

listicon3.png

listicon3.png

1627 ms

eruboshi.png

eruboshi.png

1644 ms

pm.png

pm.png

1701 ms

isa_2.png

isa_2.png

1753 ms

arrow.png

arrow.png

1762 ms

logo.png

logo.png

1677 ms

slideimg01_pc.jpg

slideimg01_pc.jpg

2680 ms

slideimg02_pc.jpg

slideimg02_pc.jpg

2884 ms

img16_pc.jpg

img16_pc.jpg

1776 ms

img15_pc.jpg

img15_pc.jpg

1814 ms

img14_pc.jpg

img14_pc.jpg

1825 ms

img13_pc.jpg

img13_pc.jpg

1793 ms

img09_pc.jpg

img09_pc.jpg

1896 ms

img04_pc.jpg

img04_pc.jpg

1920 ms

img10_pc.jpg

img10_pc.jpg

1790 ms

img12_pc.jpg

img12_pc.jpg

1746 ms

img20_pc.jpg

img20_pc.jpg

1711 ms

img08_pc.jpg

img08_pc.jpg

1583 ms

img18_pc.jpg

img18_pc.jpg

1547 ms

img19_pc.jpg

img19_pc.jpg

1529 ms

img22_pc.jpg

img22_pc.jpg

1521 ms

img11_pc.jpg

img11_pc.jpg

1474 ms

img21_pc.jpg

img21_pc.jpg

1396 ms

slideicon1.png

slideicon1.png

190 ms

slideicon2.png

slideicon2.png

166 ms

Accessibility Review

viax.co.jp accessibility score

72

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

viax.co.jp SEO score

100

Search Engine Optimization Advices

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

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

viax.co.jp

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