Tools & Wizards About Us
be-cube.jp screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

be-cube.jp

ビー・キューブ株式会社 [b3]

Page Load Speed

7 sec in total

First Response

1.2 sec

Resources Loaded

4.8 sec

Page Rendered

1.1 sec

be-cube.jp screenshot

About Website

Welcome to be-cube.jp homepage info - get ready to check Be Cube best content right away, or after learning these important things about be-cube.jp

クライアントのビジネスやサービスの可能性を最大限に引き出すマーケティングの実現を目指し、戦略立案・広告運用・データソリューションという多面的な視野から、さまざまな課題を解決する実効力をご提供いたします。

Visit be-cube.jp

Key Findings

We analyzed Be-cube.jp page load time and found that the first response time was 1.2 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

be-cube.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value380 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

be-cube.jp

1159 ms

style.css

815 ms

jquery.min.js

74 ms

jPrintArea.js

344 ms

magic.css

1197 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 91% of them (83 requests) were addressed to the original Be-cube.jp, 3% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Be-cube.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 463.3 kB (17%)

Content Size

2.7 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Be-cube.jp main page is 2.7 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. 60% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 66.9 kB

  • Original 80.6 kB
  • After minification 68.3 kB
  • After compression 13.7 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 12.3 kB, which is 15% 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 66.9 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 142.8 kB

  • Original 2.3 MB
  • After minification 2.2 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. Be Cube images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 78.8 kB

  • Original 115.5 kB
  • After minification 100.7 kB
  • After compression 36.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 78.8 kB or 68% of the original size.

CSS Optimization

-92%

Potential reduce by 174.7 kB

  • Original 190.1 kB
  • After minification 151.9 kB
  • After compression 15.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. Be-cube.jp needs all CSS files to be minified and compressed as it can save up to 174.7 kB or 92% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (22%)

Requests Now

90

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

be-cube.jp

be-cube.jp

1159 ms

style.css

style.css

815 ms

jquery.min.js

jquery.min.js

74 ms

jPrintArea.js

jPrintArea.js

344 ms

magic.css

magic.css

1197 ms

animation.js

animation.js

368 ms

parallax.js

parallax.js

365 ms

smooth.js

smooth.js

514 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

904 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

727 ms

accordion.js

accordion.js

683 ms

jquery.scrollTo-min.js

jquery.scrollTo-min.js

766 ms

scroll_anime.js

scroll_anime.js

869 ms

animation.css

animation.css

1448 ms

ajaxzip3.js

ajaxzip3.js

41 ms

jsapi

jsapi

54 ms

exvalidation.css

exvalidation.css

921 ms

exvalidation.js

exvalidation.js

973 ms

exchecker-ja.js

exchecker-ja.js

1019 ms

wow.min.js

wow.min.js

597 ms

docodoco

docodoco

528 ms

docodoco_ua_plugin.js

docodoco_ua_plugin.js

591 ms

logo.jpg

logo.jpg

163 ms

top_arrow.png

top_arrow.png

266 ms

btm_arrow.png

btm_arrow.png

267 ms

bg1.jpg

bg1.jpg

1172 ms

logo2.png

logo2.png

328 ms

btn1.png

btn1.png

267 ms

btn2.png

btn2.png

316 ms

btn3.png

btn3.png

348 ms

btn4.png

btn4.png

367 ms

more.png

more.png

369 ms

open_bg.png

open_bg.png

471 ms

bg2.jpg

bg2.jpg

1132 ms

service_icon.png

service_icon.png

523 ms

service_img1.png

service_img1.png

907 ms

service_img2.png

service_img2.png

551 ms

open_m_icon1.png

open_m_icon1.png

627 ms

gray_link.png

gray_link.png

696 ms

open_m_icon2.png

open_m_icon2.png

735 ms

open_m_icon3.png

open_m_icon3.png

783 ms

open_m_icon4.png

open_m_icon4.png

869 ms

bg3.jpg

bg3.jpg

1635 ms

consul_icon.png

consul_icon.png

940 ms

consul_img1.png

consul_img1.png

1553 ms

consul_w1.png

consul_w1.png

1089 ms

consul_w2.png

consul_w2.png

1097 ms

ca_cycle.png

ca_cycle.png

1273 ms

consul_bd.png

consul_bd.png

1253 ms

consul_img2.png

consul_img2.png

1293 ms

open_c_icon1.png

open_c_icon1.png

1336 ms

open_c_icon2.png

open_c_icon2.png

1410 ms

open_c_icon3.png

open_c_icon3.png

1455 ms

open_c_icon4.png

open_c_icon4.png

1456 ms

open_c2_img1.png

open_c2_img1.png

1506 ms

open_c2_img2.png

open_c2_img2.png

1567 ms

open_c2_img3.png

open_c2_img3.png

1639 ms

open_c3_img1.png

open_c3_img1.png

1491 ms

arrow.png

arrow.png

1523 ms

analytics.js

analytics.js

98 ms

open_c4_img1.png

open_c4_img1.png

1469 ms

bg4.jpg

bg4.jpg

2077 ms

linkid.js

linkid.js

7 ms

media_icon.png

media_icon.png

1513 ms

collect

collect

5 ms

collect

collect

56 ms

media_img.png

media_img.png

1866 ms

media_o_img4.png

media_o_img4.png

1505 ms

media_o_img1.png

media_o_img1.png

1509 ms

media_o_img2.png

media_o_img2.png

1543 ms

media_o_img3.png

media_o_img3.png

1590 ms

bg5.jpg

bg5.jpg

1901 ms

ec_icon.png

ec_icon.png

1505 ms

ec_img2.png

ec_img2.png

1529 ms

ec_img3.png

ec_img3.png

1495 ms

ec_img4.png

ec_img4.png

1501 ms

ec_img1.png

ec_img1.png

1862 ms

open_ec1_img1.png

open_ec1_img1.png

1504 ms

arrow2.png

arrow2.png

1492 ms

open_ec2_img1.png

open_ec2_img1.png

1460 ms

print_icon.png

print_icon.png

1510 ms

company_logo.png

company_logo.png

1410 ms

message_img1.png

message_img1.png

1449 ms

message_img2.png

message_img2.png

1409 ms

bg6.jpg

bg6.jpg

1388 ms

contact_btn.png

contact_btn.png

1362 ms

pagetop.png

pagetop.png

1384 ms

slider_left_list2.png

slider_left_list2.png

1413 ms

slider_right_list2.png

slider_right_list2.png

1393 ms

slider_left_list.png

slider_left_list.png

1325 ms

slider_right_list.png

slider_right_list.png

1315 ms

Accessibility Review

be-cube.jp accessibility score

81

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

Form elements do not have associated labels

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

be-cube.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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

be-cube.jp SEO score

90

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Be-cube.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Be-cube.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

be-cube.jp

Open Graph data is detected on the main page of Be Cube. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: