Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

cue.mokuren.ne.jp

さくらのレンタルサーバ

Page Load Speed

2 sec in total

First Response

516 ms

Resources Loaded

1.3 sec

Page Rendered

122 ms

cue.mokuren.ne.jp screenshot

About Website

Click here to check amazing Cue Mokuren content for Japan. Otherwise, check out these important facts you probably never knew about cue.mokuren.ne.jp

Visit cue.mokuren.ne.jp

Key Findings

We analyzed Cue.mokuren.ne.jp page load time and found that the first response time was 516 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

cue.mokuren.ne.jp performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

cue.mokuren.ne.jp

516 ms

import.css

150 ms

default.js

294 ms

base.css

225 ms

layout.css

292 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that all of those requests were addressed to Cue.mokuren.ne.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (516 ms) belongs to the original domain Cue.mokuren.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.3 kB (75%)

Content Size

15.1 kB

After Optimization

3.8 kB

In fact, the total size of Cue.mokuren.ne.jp main page is 15.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. CSS take 8.5 kB which makes up the majority of the site volume.

HTML Optimization

-52%

Potential reduce by 1.4 kB

  • Original 2.7 kB
  • After minification 2.2 kB
  • After compression 1.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 443 B, which is 17% 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 1.4 kB or 52% of the original size.

JavaScript Optimization

-84%

Potential reduce by 3.3 kB

  • Original 4.0 kB
  • After minification 1.5 kB
  • After compression 652 B

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 3.3 kB or 84% of the original size.

CSS Optimization

-78%

Potential reduce by 6.6 kB

  • Original 8.5 kB
  • After minification 5.2 kB
  • After compression 1.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. Cue.mokuren.ne.jp needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (30%)

Requests Now

10

After Optimization

7

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

Accessibility Review

cue.mokuren.ne.jp accessibility score

100

Accessibility Issues

Best Practices

cue.mokuren.ne.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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

cue.mokuren.ne.jp SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cue.mokuren.ne.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 Cue.mokuren.ne.jp 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 Cue Mokuren. 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: