Access favorite-one.co.jp. Favorite(フェイバリット)公式オンラインサイト |

favorite-one.co.jp screenshot

7

Performance

Renders faster than
22% of other websites
74

Accessibility

Visual factors better than
that of 41% of websites
67

Best Practices

More advanced features
available than in
24% of websites
83

SEO

Google-friendlier than
46% of websites

First Response

709 ms

Resources Loaded

5.2 sec

Page Rendered

370 ms

favorite-one.co.jp screenshot

About Website

Click here to check amazing Favorite One content for Japan. Otherwise, check out these important facts you probably never knew about favorite-one.co.jp

Favorite-イラストがお気に入りの一着に。- イラストワンピースユニセックス和装中華アニメコラボオリジナル「Favorite(フェイバリット)公式オンラインサイト」

Visit favorite-one.co.jp

Key Findings

We analyzed Favorite-one.co.jp page load time and found that the first response time was 709 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value2,960 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.404

25/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

favorite-one.co.jp

709 ms

m_sys_common.css

334 ms

import.css

356 ms

script.js

362 ms

check_history.css

309 ms

Our browser made a total of 253 requests to load all elements on the main page. We found that 6% of them (14 requests) were addressed to the original Favorite-one.co.jp, 39% (98 requests) were made to Image.rakuten.co.jp and 30% (75 requests) were made to Gigaplus.makeshop.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Gigaplus.makeshop.jp.

Content Size

17.7 MB

After Optimization

16.7 MB

In fact, the total size of Favorite-one.co.jp main page is 17.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 17.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 22.5 kB

Original 29.8 kB
After minification 29.2 kB
After compression 7.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 22.5 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 593.5 kB

Original 17.1 MB
After minification 16.6 MB

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. Favorite One images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 316.8 kB

Original 444.4 kB
After minification 382.0 kB
After compression 127.6 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 316.8 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 71.9 kB

Original 90.0 kB
After minification 67.1 kB
After compression 18.0 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. Favorite-one.co.jp needs all CSS files to be minified and compressed as it can save up to 71.9 kB or 80% of the original size.

Requests Now

244

After Optimization

191

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Favorite-one.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 Favorite-one.co.jp main page’s claimed encoding is euc-jp. 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

favorite-one.co.jp

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