Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

casey.jp

casey.jp

Page Load Speed

3.9 sec in total

First Response

481 ms

Resources Loaded

3.2 sec

Page Rendered

222 ms

casey.jp screenshot

About Website

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

Visit casey.jp

Key Findings

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

Performance Metrics

casey.jp performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.4 s

84/100

10%

Network Requests Diagram

casey.jp

481 ms

www.casey.jp

502 ms

514 ms

wp-emoji-release.min.js

557 ms

styles.css

473 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 58% of them (19 requests) were addressed to the original Casey.jp, 27% (9 requests) were made to Google.com and 9% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Casey.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.8 kB (48%)

Content Size

379.3 kB

After Optimization

196.6 kB

In fact, the total size of Casey.jp main page is 379.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. 25% of websites need less resources to load. Javascripts take 235.6 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 22.0 kB

  • Original 30.8 kB
  • After minification 30.0 kB
  • After compression 8.9 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 22.0 kB or 71% of the original size.

Image Optimization

-6%

Potential reduce by 3.4 kB

  • Original 60.0 kB
  • After minification 56.6 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. Casey images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 113.3 kB

  • Original 235.6 kB
  • After minification 233.0 kB
  • After compression 122.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 113.3 kB or 48% of the original size.

CSS Optimization

-83%

Potential reduce by 44.1 kB

  • Original 52.9 kB
  • After minification 39.8 kB
  • After compression 8.8 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. Casey.jp needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (54%)

Requests Now

28

After Optimization

13

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

Accessibility Review

casey.jp accessibility score

98

Accessibility Issues

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

casey.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

casey.jp SEO score

92

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 uses legible font sizes

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 Casey.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 Casey.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 Casey. 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: