Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

office-yakult.jp

オフィスでヤクルト ー ヤクルトは“健康経営”をサポートします

Page Load Speed

4.8 sec in total

First Response

528 ms

Resources Loaded

4 sec

Page Rendered

290 ms

office-yakult.jp screenshot

About Website

Welcome to office-yakult.jp homepage info - get ready to check Office Yakult best content right away, or after learning these important things about office-yakult.jp

オフィスでヤクルトは、ヤクルト製品を通じて、職場の皆さまが、毎日健康でお仕事ができるようにサポートする、法人向けサービスです。

Visit office-yakult.jp

Key Findings

We analyzed Office-yakult.jp page load time and found that the first response time was 528 ms and then it took 4.3 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

office-yakult.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.536

14/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

office-yakult.jp

528 ms

import.css

155 ms

jquery.js

764 ms

common.js

307 ms

default.css

154 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 77% of them (60 requests) were addressed to the original Office-yakult.jp, 4% (3 requests) were made to Sync.fout.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Office-yakult.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.4 kB (19%)

Content Size

704.2 kB

After Optimization

571.8 kB

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

HTML Optimization

-68%

Potential reduce by 8.5 kB

  • Original 12.5 kB
  • After minification 12.0 kB
  • After compression 4.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. 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 8.5 kB or 68% of the original size.

Image Optimization

-5%

Potential reduce by 24.5 kB

  • Original 529.0 kB
  • After minification 504.5 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. Office Yakult images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 66.2 kB

  • Original 124.2 kB
  • After minification 122.8 kB
  • After compression 58.0 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 66.2 kB or 53% of the original size.

CSS Optimization

-86%

Potential reduce by 33.2 kB

  • Original 38.5 kB
  • After minification 23.2 kB
  • After compression 5.3 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. Office-yakult.jp needs all CSS files to be minified and compressed as it can save up to 33.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (36%)

Requests Now

75

After Optimization

48

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

Accessibility Review

office-yakult.jp accessibility score

69

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

office-yakult.jp best practices score

83

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

SEO Factors

office-yakult.jp SEO score

83

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 Office-yakult.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 Office-yakult.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 Office Yakult. 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: