Tools & Wizards About Us
vixen.co.jp screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

vixen.co.jp

ビクセン Vixen | 天体望遠鏡、双眼鏡を扱う総合光学機器メーカー

Page Load Speed

6.5 sec in total

First Response

339 ms

Resources Loaded

5.6 sec

Page Rendered

566 ms

vixen.co.jp screenshot

About Website

Visit vixen.co.jp now to see the best up-to-date Vixen content for Japan and also check out these interesting facts you probably never knew about vixen.co.jp

総合光学機器メーカーの株式会社 ビクセン 公式サイト。天体望遠鏡、双眼鏡、単眼鏡、フィールドスコープ、顕微鏡、ルーペ、コンパスなど、様々な光学機器製品のご紹介と選び方、使い方、楽しみ方などをご提案しています。

Visit vixen.co.jp

Key Findings

We analyzed Vixen.co.jp page load time and found that the first response time was 339 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

vixen.co.jp performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.2 s

0/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.335

34/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

vixen.co.jp

339 ms

www.vixen.co.jp

1587 ms

gtm.js

77 ms

style.min.css

986 ms

js

64 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 87% of them (46 requests) were addressed to the original Vixen.co.jp, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Vixen.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 890.2 kB (22%)

Content Size

4.0 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vixen.co.jp main page is 4.0 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. 40% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 119.2 kB

  • Original 150.8 kB
  • After minification 118.8 kB
  • After compression 31.6 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 32.0 kB, which is 21% 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 119.2 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 104.8 kB

  • Original 3.0 MB
  • After minification 2.9 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. Vixen images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 383.8 kB

  • Original 557.2 kB
  • After minification 549.7 kB
  • After compression 173.4 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 383.8 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 282.4 kB

  • Original 321.1 kB
  • After minification 268.0 kB
  • After compression 38.7 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. Vixen.co.jp needs all CSS files to be minified and compressed as it can save up to 282.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (37%)

Requests Now

51

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vixen.co.jp

vixen.co.jp

339 ms

www.vixen.co.jp

www.vixen.co.jp

1587 ms

gtm.js

gtm.js

77 ms

style.min.css

style.min.css

986 ms

js

js

64 ms

analytics.js

analytics.js

18 ms

collect

collect

13 ms

collect

collect

94 ms

wpp.css

wpp.css

868 ms

lib.css

lib.css

1194 ms

top.css

top.css

1363 ms

mtssb-front.css

mtssb-front.css

870 ms

wpp.min.js

wpp.min.js

986 ms

vixen_SUB.css

vixen_SUB.css

1155 ms

ga-audiences

ga-audiences

78 ms

lib.js

lib.js

1533 ms

common.js

common.js

871 ms

top.js

top.js

823 ms

slider01.jpg

slider01.jpg

660 ms

slider01.jpg

slider01.jpg

1485 ms

slider01.jpg

slider01.jpg

588 ms

slider01.jpg

slider01.jpg

332 ms

slider01.jpg

slider01.jpg

330 ms

slider01.png

slider01.png

589 ms

catch-1.png

catch-1.png

663 ms

catch-2.png

catch-2.png

648 ms

catch.png

catch.png

655 ms

catch-1.png

catch-1.png

663 ms

catch.png

catch.png

815 ms

catch-5.png

catch-5.png

820 ms

catch-4.png

catch-4.png

823 ms

blank.jpg

blank.jpg

828 ms

vixen_online.jpg

vixen_online.jpg

827 ms

vixen_online_sp.jpg

vixen_online_sp.jpg

980 ms

showroom.jpg

showroom.jpg

983 ms

showroom_sp.jpg

showroom_sp.jpg

986 ms

howto.jpg

howto.jpg

991 ms

howto_sp.jpg

howto_sp.jpg

992 ms

banner_dinamic01.jpg

banner_dinamic01.jpg

1147 ms

banner_dinamic01.jpg

banner_dinamic01.jpg

1146 ms

banner_dinamic01.jpg

banner_dinamic01.jpg

1152 ms

banner_dinamic04.jpg

banner_dinamic04.jpg

1156 ms

bg_hero_01.png

bg_hero_01.png

1113 ms

ico_arrow_02_no.png

ico_arrow_02_no.png

1266 ms

ico_arrow_right_02.svg

ico_arrow_right_02.svg

1268 ms

bg_top_01.jpg

bg_top_01.jpg

1439 ms

arrow_pagetop.svg

arrow_pagetop.svg

1278 ms

ico_arrow_01.svg

ico_arrow_01.svg

1277 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

98 ms

ico_prev_01.png

ico_prev_01.png

893 ms

ico_next_01.png

ico_next_01.png

896 ms

ico-arrow-cal-up.png

ico-arrow-cal-up.png

904 ms

ico-arrow-cal-down.png

ico-arrow-cal-down.png

905 ms

Accessibility Review

vixen.co.jp accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

vixen.co.jp best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

vixen.co.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

    JA

  • Encoding

    UTF-8

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

vixen.co.jp

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