Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

bebit.co.jp

ビービット(beBit) | ユーザ視点からの価値創出を追求するエクスペリエンス・デザイン・パートナー

Page Load Speed

7.1 sec in total

First Response

522 ms

Resources Loaded

6.1 sec

Page Rendered

467 ms

bebit.co.jp screenshot

About Website

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

エクスペリエンスデザイン・パートナーのビービットは、コンサルティングと「USERGRAM」の提供を通じて、企業のユーザ理解によるUX・体験設計を支援します。

Visit bebit.co.jp

Key Findings

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

Performance Metrics

bebit.co.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value22.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,010 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.122

84/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

bebit.co.jp

522 ms

www.bebit.co.jp

1008 ms

styles.css

174 ms

jquery-1.11.1.min.js

511 ms

underscore-min.js

509 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 65% of them (76 requests) were addressed to the original Bebit.co.jp, 7% (8 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Bebit.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 205.8 kB (5%)

Content Size

4.5 MB

After Optimization

4.3 MB

In fact, the total size of Bebit.co.jp main page is 4.5 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. Only a small number of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 55.8 kB

  • Original 66.2 kB
  • After minification 60.3 kB
  • After compression 10.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. 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 55.8 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 99.4 kB

  • Original 4.2 MB
  • After minification 4.1 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. BeBit images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 19.7 kB

  • Original 223.8 kB
  • After minification 223.8 kB
  • After compression 204.1 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

-62%

Potential reduce by 30.9 kB

  • Original 49.6 kB
  • After minification 45.3 kB
  • After compression 18.7 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. Bebit.co.jp needs all CSS files to be minified and compressed as it can save up to 30.9 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (54%)

Requests Now

106

After Optimization

49

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

Accessibility Review

bebit.co.jp accessibility score

82

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

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

bebit.co.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

bebit.co.jp SEO score

92

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 Bebit.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 Bebit.co.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 data is detected on the main page of BeBit. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: