Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

support.casio.jp

お客様サポート | CASIO

Page Load Speed

6.1 sec in total

First Response

372 ms

Resources Loaded

5.5 sec

Page Rendered

222 ms

support.casio.jp screenshot

About Website

Welcome to support.casio.jp homepage info - get ready to check Support CASIO best content for Japan right away, or after learning these important things about support.casio.jp

CASIO(カシオ)製品のサポートページです。製品に関するFAQ(よくあるご質問)、ソフトウェアダウンロード、各種お問い合わせ、修理のお申し込み、取扱説明書などのサポート情報をご覧いただけます。

Visit support.casio.jp

Key Findings

We analyzed Support.casio.jp page load time and found that the first response time was 372 ms and then it took 5.8 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

support.casio.jp performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value77.7 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value9,520 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.666

8/100

15%

TTI (Time to Interactive)

Value97.5 s

0/100

10%

Network Requests Diagram

support.casio.jp

372 ms

872 ms

stylesheet.php

424 ms

stylesheet.php

844 ms

stylesheet.php

1499 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Support.casio.jp, 82% (95 requests) were made to Casio.jp and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Casio.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 230.0 kB (31%)

Content Size

733.3 kB

After Optimization

503.4 kB

In fact, the total size of Support.casio.jp main page is 733.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 404.1 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 21.0 kB

  • Original 28.2 kB
  • After minification 25.1 kB
  • After compression 7.2 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.1 kB, which is 11% 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 21.0 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 6.4 kB

  • Original 404.1 kB
  • After minification 397.7 kB

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. Support CASIO images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 202.6 kB

  • Original 301.0 kB
  • After minification 278.4 kB
  • After compression 98.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 202.6 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (38%)

Requests Now

112

After Optimization

69

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

Accessibility Review

support.casio.jp accessibility score

74

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 have valid values

High

ARIA IDs are not unique

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.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

support.casio.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

High

Missing source maps for large first-party JavaScript

SEO Factors

support.casio.jp SEO score

83

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

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

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 Support.casio.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 Support.casio.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

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