Tools & Wizards About Us
being.co.jp screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

being.co.jp

Being Music Fantasy

Page Load Speed

1.1 sec in total

First Response

494 ms

Resources Loaded

651 ms

Page Rendered

0 ms

being.co.jp screenshot

About Website

Visit being.co.jp now to see the best up-to-date Being content for Japan and also check out these interesting facts you probably never knew about being.co.jp

Visit being.co.jp

Key Findings

We analyzed Being.co.jp page load time and found that the first response time was 494 ms and then it took 651 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

being.co.jp performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.769

5/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

being.co.jp

494 ms

shim.gif

152 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Being.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (494 ms) belongs to the original domain Being.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 319 B (49%)

Content Size

647 B

After Optimization

328 B

  • HTML

In fact, the total size of Being.co.jp main page is 647 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 647 B which makes up the majority of the site volume.

HTML Optimization

-49%

Potential reduce by 319 B

  • Original 647 B
  • After minification 545 B
  • After compression 328 B

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 102 B, which is 16% 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 319 B or 49% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Network Requests Diagram

being.co.jp

being.co.jp

494 ms

shim.gif

shim.gif

152 ms

Accessibility Review

being.co.jp accessibility score

47

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.

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

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

being.co.jp best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

being.co.jp SEO score

58

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Being.co.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Being.co.jp main page’s claimed encoding is . 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

being.co.jp

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