Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

cutboard.com

Jv^`l^IWiēŔ^sYŔ^Jbg{[h^CNWFbg

Page Load Speed

2.7 sec in total

First Response

590 ms

Resources Loaded

2 sec

Page Rendered

106 ms

cutboard.com screenshot

About Website

Click here to check amazing Cutboard content for Japan. Otherwise, check out these important facts you probably never knew about cutboard.com

kBs̃Jbg{[hcyɂꂢȃJbeBOV[As[{[hE`lEJv܂B

Visit cutboard.com

Key Findings

We analyzed Cutboard.com page load time and found that the first response time was 590 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

cutboard.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

34/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.418

23/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

cutboard.com

590 ms

633 ms

main.css

192 ms

analytics.js

5 ms

sd2.gif

193 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 81% of them (13 requests) were addressed to the original Cutboard.com, 13% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (633 ms) belongs to the original domain Cutboard.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.7 kB (60%)

Content Size

57.7 kB

After Optimization

23.0 kB

In fact, the total size of Cutboard.com main page is 57.7 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. Only 5% of websites need less resources to load. Javascripts take 52.9 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 1.9 kB

  • Original 3.6 kB
  • After minification 3.4 kB
  • After compression 1.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. 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 1.9 kB or 54% of the original size.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

CSS Optimization

-64%

Potential reduce by 784 B

  • Original 1.2 kB
  • After minification 989 B
  • After compression 437 B

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. Cutboard.com needs all CSS files to be minified and compressed as it can save up to 784 B or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (50%)

Requests Now

14

After Optimization

7

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

Accessibility Review

cutboard.com accessibility score

95

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.

Best Practices

cutboard.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

cutboard.com SEO score

83

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    SY

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cutboard.com can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed Japanese language. Our system also found out that Cutboard.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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