Tools & Wizards About Us
finess.jp screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

finess.jp

サジーのフィネス | 豊潤サジー通販 | サジーベリー通販

Page Load Speed

9.8 sec in total

First Response

571 ms

Resources Loaded

8.4 sec

Page Rendered

804 ms

finess.jp screenshot

About Website

Click here to check amazing Finess content for Japan. Otherwise, check out these important facts you probably never knew about finess.jp

豊潤サジーは、美容と健康に優れたサジーベリーをピューレ状にしたサジージュースです。自然の力を活かした理想的なドリンクで、あなたの毎日をサポート。

Visit finess.jp

Key Findings

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

Performance Metrics

finess.jp performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value18.6 s

0/100

10%

TBT (Total Blocking Time)

Value8,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.967

2/100

15%

TTI (Time to Interactive)

Value49.7 s

0/100

10%

Network Requests Diagram

finess.jp

571 ms

finess.jp

1302 ms

wp-emoji-release.min.js

491 ms

style.min.css

491 ms

block.css

507 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 84% of them (53 requests) were addressed to the original Finess.jp, 6% (4 requests) were made to Use.fontawesome.com and 6% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Finess.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.8 kB (20%)

Content Size

567.6 kB

After Optimization

456.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Finess.jp main page is 567.6 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. 40% of websites need less resources to load. Images take 274.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 69.2 kB

  • Original 82.0 kB
  • After minification 75.0 kB
  • After compression 12.8 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 69.2 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 2.7 kB

  • Original 274.6 kB
  • After minification 271.9 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. Finess images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 9.8 kB

  • Original 93.5 kB
  • After minification 93.4 kB
  • After compression 83.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-25%

Potential reduce by 29.0 kB

  • Original 117.4 kB
  • After minification 117.4 kB
  • After compression 88.4 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. Finess.jp needs all CSS files to be minified and compressed as it can save up to 29.0 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (58%)

Requests Now

36

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

finess.jp

finess.jp

571 ms

finess.jp

finess.jp

1302 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

491 ms

style.min.css

style.min.css

491 ms

block.css

block.css

507 ms

style.css

style.css

565 ms

xo-event-calendar.css

xo-event-calendar.css

565 ms

style.css

style.css

742 ms

style.min.css

style.min.css

1265 ms

style.min.css

style.min.css

1269 ms

style.min.css

style.min.css

1093 ms

style.min.css

style.min.css

1109 ms

style.min.css

style.min.css

1154 ms

blocks.style.build.css

blocks.style.build.css

1524 ms

ajax.js

ajax.js

1582 ms

jquery.min.js

jquery.min.js

1808 ms

jquery-migrate.min.js

jquery-migrate.min.js

1671 ms

jquery.min.js

jquery.min.js

39 ms

all.css

all.css

50 ms

slick.css

slick.css

35 ms

slick-theme.css

slick-theme.css

37 ms

slick.min.js

slick.min.js

47 ms

script.js

script.js

1750 ms

gutentor.js

gutentor.js

1940 ms

wp-embed.min.js

wp-embed.min.js

2085 ms

logo_header.png

logo_header.png

398 ms

top_fv.webp

top_fv.webp

1511 ms

top_fv_pc.webp

top_fv_pc.webp

2044 ms

campaign_banner.webp

campaign_banner.webp

1160 ms

saji_1000.webp

saji_1000.webp

874 ms

b_saj_900.webp

b_saj_900.webp

1209 ms

b_saj_300.webp

b_saj_300.webp

903 ms

saji_stick.webp

saji_stick.webp

1734 ms

syogamitsu.webp

syogamitsu.webp

1575 ms

yuzumitsu.webp

yuzumitsu.webp

1931 ms

rakusankin.webp

rakusankin.webp

1987 ms

yousan-supple.webp

yousan-supple.webp

2534 ms

sajinaset.webp

sajinaset.webp

2325 ms

sajina-booster.webp

sajina-booster.webp

2243 ms

sajina-serum.webp

sajina-serum.webp

2519 ms

sajina-soap.webp

sajina-soap.webp

2552 ms

sajina-bodysoap.webp

sajina-bodysoap.webp

2817 ms

drink.webp

drink.webp

3421 ms

subscription.webp

subscription.webp

3102 ms

column.webp

column.webp

3855 ms

arrow.webp

arrow.webp

3083 ms

saji_association.webp

saji_association.webp

3664 ms

bnr_900ml.png

bnr_900ml.png

4003 ms

bnr_300ml.png

bnr_300ml.png

3895 ms

bnr_course.png

bnr_course.png

3665 ms

bnr_drink.jpg

bnr_drink.jpg

4009 ms

bnr_recipe.jpg

bnr_recipe.jpg

4154 ms

bnr_ingredient.jpg

bnr_ingredient.jpg

4228 ms

bnr_about_saji.jpg

bnr_about_saji.jpg

4368 ms

bnr_labo01.png

bnr_labo01.png

4385 ms

bnr_labo02.png

bnr_labo02.png

4574 ms

nav-prev.svg

nav-prev.svg

4589 ms

nav-next.svg

nav-next.svg

4659 ms

fa-solid-900.woff

fa-solid-900.woff

29 ms

fa-regular-400.woff

fa-regular-400.woff

25 ms

fa-brands-400.woff

fa-brands-400.woff

28 ms

ajax-loader.gif

ajax-loader.gif

16 ms

slick.woff

slick.woff

2 ms

Accessibility Review

finess.jp accessibility score

85

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

finess.jp 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

finess.jp SEO score

93

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

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 Finess.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 Finess.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

finess.jp

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