Tools & Wizards About Us

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

frecious.jp

【天然水】ウォーターサーバー・宅配水のフレシャス＜公式＞

Page Load Speed

14.3 sec in total

First Response

514 ms

Resources Loaded

13.1 sec

Page Rendered

645 ms

About Website

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

【天然水ウォーターサーバー・宅配水のフレシャス公式サイト】コーヒー機能付きウォーターサーバーや一人暮らし向け卓上モデル等、デザイン性・機能性共に人気のウォーターサーバーをラインナップ。配送料全国無料0円!限定キャンペーン実施中!

Visit frecious.jp

Key Findings

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

Performance Metrics

frecious.jp performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value1.242

1/100

15%

TTI (Time to Interactive)

Value25.0 s

0/100

10%

Network Requests Diagram

frecious.jp

514 ms

www.frecious.jp

1052 ms

import.css

320 ms

base3.css

335 ms

rollover.js

338 ms

Our browser made a total of 238 requests to load all elements on the main page. We found that 66% of them (156 requests) were addressed to the original Frecious.jp, 3% (8 requests) were made to Google.com and 3% (7 requests) were made to Bypass.ad-stir.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Frecious.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 574.1 kB (35%)

Content Size

1.6 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 77.3 kB

  • Original 95.6 kB
  • After minification 84.4 kB
  • After compression 18.4 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 11.2 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 77.3 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 19.5 kB

  • Original 847.5 kB
  • After minification 828.1 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. Frecious images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 351.3 kB

  • Original 529.6 kB
  • After minification 470.0 kB
  • After compression 178.3 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 351.3 kB or 66% of the original size.

CSS Optimization

-87%

Potential reduce by 126.1 kB

  • Original 145.3 kB
  • After minification 117.0 kB
  • After compression 19.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. Frecious.jp needs all CSS files to be minified and compressed as it can save up to 126.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 97 (46%)

Requests Now

210

After Optimization

113

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

frecious.jp accessibility score

95

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

frecious.jp best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

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

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frecious.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 Frecious.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

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