Tools & Wizards About Us
vanda.co.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 0

    Best Practices

  • 74

    SEO

    Google-friendlier than
    32% of websites

vanda.co.jp

株式会社 玉光堂

Page Load Speed

13.5 sec in total

First Response

2 sec

Resources Loaded

11.1 sec

Page Rendered

379 ms

vanda.co.jp screenshot

About Website

Welcome to vanda.co.jp homepage info - get ready to check Vanda best content for Japan right away, or after learning these important things about vanda.co.jp

Vanda.co.jp:CD DVD アニメ 映画 J-POP ROCK MUSIC ・・ 音楽と映像の総合ショップ です。ポイントや割引などお得なサービス実施中

Visit vanda.co.jp

Key Findings

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

Performance Metrics

vanda.co.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

vanda.co.jp

2027 ms

i.css

866 ms

whatsnew.css

376 ms

search.css

378 ms

custom.css

405 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 448.9 kB (14%)

Content Size

3.2 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 50.1 kB

  • Original 60.4 kB
  • After minification 44.9 kB
  • After compression 10.3 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 15.5 kB, which is 26% 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 50.1 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 293.2 kB

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

JavaScript Optimization

-59%

Potential reduce by 76.7 kB

  • Original 130.9 kB
  • After minification 127.2 kB
  • After compression 54.2 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 76.7 kB or 59% of the original size.

CSS Optimization

-85%

Potential reduce by 28.9 kB

  • Original 34.1 kB
  • After minification 24.3 kB
  • After compression 5.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. Vanda.co.jp needs all CSS files to be minified and compressed as it can save up to 28.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (20%)

Requests Now

85

After Optimization

68

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vanda.co.jp

vanda.co.jp

2027 ms

i.css

i.css

866 ms

whatsnew.css

whatsnew.css

376 ms

search.css

search.css

378 ms

custom.css

custom.css

405 ms

jquery.js

jquery.js

1401 ms

yuiauto.jgz

yuiauto.jgz

763 ms

jquery.cookie.js

jquery.cookie.js

562 ms

jquery-ui.js

jquery-ui.js

965 ms

qcart081106.js

qcart081106.js

789 ms

jtip.js

jtip.js

927 ms

search.js

search.js

767 ms

logo3.gif

logo3.gif

190 ms

cart_top_01.png

cart_top_01.png

193 ms

cart_bottom01.png

cart_bottom01.png

185 ms

osusume.gif

osusume.gif

186 ms

tableftF.gif

tableftF.gif

176 ms

tabrightF.gif

tabrightF.gif

202 ms

musi.gif

musi.gif

346 ms

cart.png

cart.png

367 ms

SME_AICL-2989.jpg

SME_AICL-2989.jpg

1046 ms

K_KICS-3312.jpg

K_KICS-3312.jpg

1215 ms

SME_SECL-1800.jpg

SME_SECL-1800.jpg

1606 ms

topic.png

topic.png

400 ms

P_UPCH-7087.jpg

P_UPCH-7087.jpg

1096 ms

V_VICL-64415.jpg

V_VICL-64415.jpg

2482 ms

V_VIZL-909.jpg

V_VIZL-909.jpg

894 ms

SME_SECL-1814.jpg

SME_SECL-1814.jpg

1707 ms

PC_HKCN-50457.jpg

PC_HKCN-50457.jpg

2056 ms

VAP_VPCC-81806.jpg

VAP_VPCC-81806.jpg

1606 ms

SME_MHCL-30248.jpg

SME_MHCL-30248.jpg

2286 ms

WP_WPCL-11871.jpg

WP_WPCL-11871.jpg

5898 ms

SME_SICP-30902.jpg

SME_SICP-30902.jpg

3703 ms

WP_WPCR-17045.jpg

WP_WPCR-17045.jpg

2464 ms

WP_WPCR-17015.jpg

WP_WPCR-17015.jpg

3131 ms

WP_WPCR-16383.jpg

WP_WPCR-16383.jpg

2824 ms

WP_WPCR-16444.jpg

WP_WPCR-16444.jpg

3257 ms

WP_WPZL-31130.jpg

WP_WPZL-31130.jpg

4312 ms

P_UICY-76429.jpg

P_UICY-76429.jpg

4203 ms

WP_WPCR-15876.jpg

WP_WPCR-15876.jpg

4472 ms

WP_WPCR-16394.jpg

WP_WPCR-16394.jpg

4597 ms

WP_WPCR-16395.jpg

WP_WPCR-16395.jpg

5588 ms

WP_WPCR-16396.jpg

WP_WPCR-16396.jpg

5259 ms

P_UICY-76517.jpg

P_UICY-76517.jpg

5656 ms

WP_WPCR-15758.jpg

WP_WPCR-15758.jpg

4711 ms

WP_WPCR-15606.jpg

WP_WPCR-15606.jpg

5156 ms

P_UICY-76514.jpg

P_UICY-76514.jpg

5598 ms

P_TYCT-69027.jpg

P_TYCT-69027.jpg

5546 ms

ga.js

ga.js

40 ms

340 ms

bivalves.js

bivalves.js

368 ms

__utm.gif

__utm.gif

12 ms

WP_WPCL-11926.jpg

WP_WPCL-11926.jpg

6276 ms

C_COCP-38613.jpg

C_COCP-38613.jpg

6019 ms

ADI_AVCD-38976.jpg

ADI_AVCD-38976.jpg

6517 ms

ADI_AVCD-38930.jpg

ADI_AVCD-38930.jpg

5649 ms

VAP_TFCC-86473.jpg

VAP_TFCC-86473.jpg

6380 ms

C_COZP-933.jpg

C_COZP-933.jpg

6009 ms

ADI_AVCD-38965.jpg

ADI_AVCD-38965.jpg

5758 ms

BV_VWAS-5331.jpg

BV_VWAS-5331.jpg

6131 ms

PC_PCBG-52252.jpg

PC_PCBG-52252.jpg

6275 ms

AMS_ASBY-5757.jpg

AMS_ASBY-5757.jpg

6085 ms

BV_VWDZ-8164.jpg

BV_VWDZ-8164.jpg

5821 ms

PLC_PHNE-119914.jpg

PLC_PHNE-119914.jpg

5639 ms

TCE_TCED-2191.jpg

TCE_TCED-2191.jpg

5764 ms

SME_ANZB-11047.jpg

SME_ANZB-11047.jpg

5529 ms

muryou.gif

muryou.gif

5290 ms

manavivamuryou180.gif

manavivamuryou180.gif

5227 ms

mise.png

mise.png

5005 ms

rank.jpg

rank.jpg

4976 ms

original1.jpg

original1.jpg

4679 ms

banner_cpn20a.jpg

banner_cpn20a.jpg

4883 ms

banner_cpn8a.jpg

banner_cpn8a.jpg

4352 ms

banner_cpn7a.jpg

banner_cpn7a.jpg

4305 ms

cpn2.jpg

cpn2.jpg

4088 ms

dore34.jpg

dore34.jpg

3649 ms

BBJ_sitelogo.png

BBJ_sitelogo.png

3155 ms

CD.png

CD.png

3120 ms

ina4.gif

ina4.gif

3076 ms

CDS.png

CDS.png

2947 ms

DVD.png

DVD.png

2831 ms

PLC_GNBF-3523.jpg

PLC_GNBF-3523.jpg

2389 ms

ssl.gif

ssl.gif

2690 ms

kessai.gif

kessai.gif

2052 ms

shadow.gif

shadow.gif

2137 ms

comment.png

comment.png

2135 ms

sitemap.png

sitemap.png

2068 ms

Accessibility Review

vanda.co.jp accessibility score

76

Accessibility Issues

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

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.

SEO Factors

vanda.co.jp SEO score

74

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

Links do not have descriptive text

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

vanda.co.jp

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