Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

canvas.ws

CANVAS | 遊びと学びのヒミツ基地

Page Load Speed

66.9 sec in total

First Response

4.7 sec

Resources Loaded

61.5 sec

Page Rendered

717 ms

About Website

Welcome to canvas.ws homepage info - get ready to check CANVAS best content for Japan right away, or after learning these important things about canvas.ws

CANVAS(キャンバス)は、こどもたちの創造・表現力をテーマにしたワークショップ・イベント、セミナーを多数、企画・開催しているNPOです。

Visit canvas.ws

Key Findings

We analyzed Canvas.ws page load time and found that the first response time was 4.7 sec and then it took 62.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

canvas.ws performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value28.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,220 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value28.0 s

0/100

10%

Network Requests Diagram

canvas.ws

4709 ms

style.css

705 ms

jquery.js

1083 ms

share.js

742 ms

jquery.bxslider.js

1080 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 93% of them (128 requests) were addressed to the original Canvas.ws, 1% (2 requests) were made to Ssl.google-analytics.com and 1% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Canvas.ws.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (17%)

Content Size

6.1 MB

After Optimization

5.1 MB

In fact, the total size of Canvas.ws main page is 6.1 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. 70% of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 574.2 kB

  • Original 681.3 kB
  • After minification 637.3 kB
  • After compression 107.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 574.2 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 111.9 kB

  • Original 5.0 MB
  • After minification 4.8 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. CANVAS images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 245.8 kB

  • Original 354.1 kB
  • After minification 294.4 kB
  • After compression 108.3 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 245.8 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 116.2 kB

  • Original 136.5 kB
  • After minification 104.5 kB
  • After compression 20.2 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. Canvas.ws needs all CSS files to be minified and compressed as it can save up to 116.2 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

135

After Optimization

102

The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CANVAS. 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 16 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

canvas.ws accessibility score

79

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.

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

canvas.ws 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

canvas.ws SEO score

82

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

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Canvas.ws can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Canvas.ws 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 data is detected on the main page of CANVAS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: