Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

recipe.cuoca.com

レシピトップ | お菓子作り・パン作りの材料と道具の専門店 | cuocaクオカ

Page Load Speed

4.9 sec in total

First Response

461 ms

Resources Loaded

4 sec

Page Rendered

366 ms

recipe.cuoca.com screenshot

About Website

Visit recipe.cuoca.com now to see the best up-to-date Recipe Cuoca content for Japan and also check out these interesting facts you probably never knew about recipe.cuoca.com

お菓子・パン作りの材料と道具の専門店クオカのオリジナルレシピ集。30分でできる簡単レシピからこだわりぬいて作る本格レシピ、家族と一緒に作れる楽しいレシピまで、専門店ならではの絶品パン・スイーツレシピが満載!

Visit recipe.cuoca.com

Key Findings

We analyzed Recipe.cuoca.com page load time and found that the first response time was 461 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

recipe.cuoca.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value1,540 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.205

60/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

recipe.cuoca.com

461 ms

index.php

603 ms

headerfooter.css

370 ms

layout.css

375 ms

style.css

762 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 52% of them (47 requests) were addressed to the original Recipe.cuoca.com, 25% (23 requests) were made to Img.cuoca.com and 5% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Recipe.cuoca.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 290.0 kB (30%)

Content Size

980.2 kB

After Optimization

690.2 kB

In fact, the total size of Recipe.cuoca.com main page is 980.2 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 588.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 29.1 kB

  • Original 38.1 kB
  • After minification 33.3 kB
  • After compression 9.0 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 4.8 kB, which is 12% 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 29.1 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 15.3 kB

  • Original 588.2 kB
  • After minification 572.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. Recipe Cuoca images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 138.4 kB

  • Original 226.6 kB
  • After minification 207.0 kB
  • After compression 88.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 138.4 kB or 61% of the original size.

CSS Optimization

-84%

Potential reduce by 107.2 kB

  • Original 127.4 kB
  • After minification 103.4 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. Recipe.cuoca.com needs all CSS files to be minified and compressed as it can save up to 107.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (53%)

Requests Now

85

After Optimization

40

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

Accessibility Review

recipe.cuoca.com accessibility score

77

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

recipe.cuoca.com best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

recipe.cuoca.com SEO score

92

Search Engine Optimization Advices

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

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Recipe.cuoca.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Recipe.cuoca.com 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 Recipe Cuoca. 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: