Tools & Wizards About Us
rikuro.co.jp screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

rikuro.co.jp

大阪銘菓「焼きたてチーズケーキ」・りくろーおじさんの店

Page Load Speed

5.7 sec in total

First Response

535 ms

Resources Loaded

4.9 sec

Page Rendered

221 ms

rikuro.co.jp screenshot

About Website

Welcome to rikuro.co.jp homepage info - get ready to check Rikuro best content for Japan right away, or after learning these important things about rikuro.co.jp

りくろーおじさんはチーズケーキ・パーティーケーキ・ニコニコりくろーる・アップルパイなどの販売を行っています。

Visit rikuro.co.jp

Key Findings

We analyzed Rikuro.co.jp page load time and found that the first response time was 535 ms and then it took 5.2 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

rikuro.co.jp performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.262

47/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

rikuro.co.jp

535 ms

www.rikuro.co.jp

951 ms

js

66 ms

jquery-1.8.3.min.js

43 ms

reset.css

188 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 85% of them (45 requests) were addressed to the original Rikuro.co.jp, 4% (2 requests) were made to Connect.facebook.net and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Rikuro.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.7 kB (5%)

Content Size

869.3 kB

After Optimization

823.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rikuro.co.jp main page is 869.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 783.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.9 kB

  • Original 35.2 kB
  • After minification 33.1 kB
  • After compression 8.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. 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 26.9 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 7.1 kB

  • Original 783.9 kB
  • After minification 776.8 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. Rikuro images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 5.5 kB

  • Original 31.3 kB
  • After minification 31.2 kB
  • After compression 25.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 5.5 kB or 17% of the original size.

CSS Optimization

-33%

Potential reduce by 6.2 kB

  • Original 18.8 kB
  • After minification 18.8 kB
  • After compression 12.6 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. Rikuro.co.jp needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (47%)

Requests Now

47

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rikuro.co.jp

rikuro.co.jp

535 ms

www.rikuro.co.jp

www.rikuro.co.jp

951 ms

js

js

66 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

43 ms

reset.css

reset.css

188 ms

layout.css

layout.css

368 ms

common.css

common.css

516 ms

style.css

style.css

518 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

533 ms

nivo-slider.css

nivo-slider.css

536 ms

default.css

default.css

544 ms

colorbox.css

colorbox.css

548 ms

jquery.colorbox.js

jquery.colorbox.js

686 ms

mobile.js

mobile.js

689 ms

main_bgimg.jpg

main_bgimg.jpg

363 ms

header_lang_en.png

header_lang_en.png

173 ms

header_logo.png

header_logo.png

174 ms

loading.gif

loading.gif

182 ms

2024rikuyoyakub3.jpg

2024rikuyoyakub3.jpg

530 ms

online_b_itudemo.jpg

online_b_itudemo.jpg

575 ms

20242rikuteracceb.jpg

20242rikuteracceb.jpg

683 ms

appletop.jpg

appletop.jpg

1028 ms

index_top_chou.jpg

index_top_chou.jpg

903 ms

index_caption_icon1.png

index_caption_icon1.png

544 ms

arw01.png

arw01.png

707 ms

prin_b.jpg

prin_b.jpg

725 ms

index_list_mark.png

index_list_mark.png

753 ms

maki_b.jpg

maki_b.jpg

855 ms

index_caption_icon2.png

index_caption_icon2.png

884 ms

index_shop2022.png

index_shop2022.png

343 ms

index_caption_icon3.png

index_caption_icon3.png

910 ms

index_caption_icon5.png

index_caption_icon5.png

931 ms

index_caption_icon4.png

index_caption_icon4.png

1026 ms

index_reserv_icon.png

index_reserv_icon.png

344 ms

index_delivery_icon.png

index_delivery_icon.png

356 ms

pagetop_icon.png

pagetop_icon.png

1061 ms

footer_logo2.png

footer_logo2.png

1083 ms

footer_copyrights.png

footer_copyrights.png

1091 ms

sdk.js

sdk.js

19 ms

index_reserv_bgimg.jpg

index_reserv_bgimg.jpg

1081 ms

index_delivery_bgimg.jpg

index_delivery_bgimg.jpg

1168 ms

red_bgimg.jpg

red_bgimg.jpg

1170 ms

footer_icon.png

footer_icon.png

1210 ms

ga.js

ga.js

48 ms

sdk.js

sdk.js

9 ms

40 ms

__utm.gif

__utm.gif

12 ms

collect

collect

27 ms

index_shop2022.png

index_shop2022.png

1283 ms

index_reserv_icon.png

index_reserv_icon.png

929 ms

index_delivery_icon.png

index_delivery_icon.png

932 ms

mobile.css

mobile.css

183 ms

arrows.png

arrows.png

182 ms

Accessibility Review

rikuro.co.jp accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

rikuro.co.jp best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

rikuro.co.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

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

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 Rikuro.co.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 Rikuro.co.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

rikuro.co.jp

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