Tools & Wizards About Us
ecbb.jp screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

ecbb.jp

WEBビジネス構築パッケージ・アプリ開発｜ECBB

Page Load Speed

5.4 sec in total

First Response

582 ms

Resources Loaded

4.6 sec

Page Rendered

245 ms

ecbb.jp screenshot

About Website

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

ECサイト構築、WEBビジネス構築パッケージ・アプリ開発（iPhone, iPad, Android等）のECBB。ECサイト構築、ネットビジネス成功に必要なエッセンスを次々とシステムパッケージ化して提供。業界トップ実績。成功体験の共有。

Visit ecbb.jp

Key Findings

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

Performance Metrics

ecbb.jp performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.136

80/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

ecbb.jp

582 ms

ecbb.jp

1021 ms

default.css

371 ms

jquery.min.js

31 ms

jquery.datasort.js

550 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 54% of them (42 requests) were addressed to the original Ecbb.jp, 27% (21 requests) were made to Static.xx.fbcdn.net and 6% (5 requests) were made to Makers.ecbb.jp. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Ecbb.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.8 kB (20%)

Content Size

2.2 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 21.1 kB

  • Original 27.1 kB
  • After minification 22.4 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 4.7 kB, which is 17% 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 21.1 kB or 78% of the original size.

Image Optimization

-17%

Potential reduce by 343.0 kB

  • Original 2.0 MB
  • After minification 1.7 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. Obviously, ECBB needs image optimization as it can save up to 343.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-47%

Potential reduce by 37.6 kB

  • Original 79.9 kB
  • After minification 77.0 kB
  • After compression 42.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 37.6 kB or 47% of the original size.

CSS Optimization

-86%

Potential reduce by 46.0 kB

  • Original 53.7 kB
  • After minification 40.7 kB
  • After compression 7.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. Ecbb.jp needs all CSS files to be minified and compressed as it can save up to 46.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (43%)

Requests Now

76

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ecbb.jp

ecbb.jp

582 ms

ecbb.jp

ecbb.jp

1021 ms

default.css

default.css

371 ms

jquery.min.js

jquery.min.js

31 ms

jquery.datasort.js

jquery.datasort.js

550 ms

datasort2.js

datasort2.js

556 ms

js

js

64 ms

jquery.cookie.js

jquery.cookie.js

578 ms

facebook.css

facebook.css

213 ms

bnr_bottom_sp.jpg

bnr_bottom_sp.jpg

1709 ms

likebox.php

likebox.php

268 ms

top_visual.jpg

top_visual.jpg

408 ms

logo.jpg

logo.jpg

234 ms

tab_contact.jpg

tab_contact.jpg

225 ms

top_tagline.jpg

top_tagline.jpg

234 ms

top_slogan.jpg

top_slogan.jpg

395 ms

hp_maker.jpg

hp_maker.jpg

414 ms

spacer.gif

spacer.gif

415 ms

bnr_partner.jpg

bnr_partner.jpg

577 ms

bg_partner.jpg

bg_partner.jpg

580 ms

btn_partner.jpg

btn_partner.jpg

600 ms

top_bnr_life.jpg

top_bnr_life.jpg

2145 ms

top_bnr_palmo.jpg

top_bnr_palmo.jpg

2334 ms

top_bnr_smartphone.jpg

top_bnr_smartphone.jpg

993 ms

btn_sp_ec.jpg

btn_sp_ec.jpg

758 ms

btn_sp_cms.jpg

btn_sp_cms.jpg

765 ms

top_uservoice_bnr.jpg

top_uservoice_bnr.jpg

983 ms

top_bnr_resistance.jpg

top_bnr_resistance.jpg

1123 ms

top_ec_camp_bnr_s.jpg

top_ec_camp_bnr_s.jpg

950 ms

pro_head.jpg

pro_head.jpg

1135 ms

pro_bg.jpg

pro_bg.jpg

1174 ms

ec_icon.gif

ec_icon.gif

1186 ms

spacer.gif

spacer.gif

1306 ms

pro_more.jpg

pro_more.jpg

1321 ms

icon_pe.gif

icon_pe.gif

1367 ms

affi_icon.gif

affi_icon.gif

1379 ms

pro_icon.jpg

pro_icon.jpg

1488 ms

icon_cms.gif

icon_cms.gif

1506 ms

ml_icon.gif

ml_icon.gif

1558 ms

top_contact.jpg

top_contact.jpg

1572 ms

bnr_mall.jpg

bnr_mall.jpg

1671 ms

bnr_pi.jpg

bnr_pi.jpg

1691 ms

bnr_hikaku.jpg

bnr_hikaku.jpg

1751 ms

bnr_rs.jpg

bnr_rs.jpg

1765 ms

bnr_vision.jpg

bnr_vision.jpg

1853 ms

bottom_top.jpg

bottom_top.jpg

1876 ms

bnr_bottom_sp_gid.jpg

bnr_bottom_sp_gid.jpg

1303 ms

bnr_bottom_sp_foldable.jpg

bnr_bottom_sp_foldable.jpg

1892 ms

bnr_bottom_sp_kindle.jpg

bnr_bottom_sp_kindle.jpg

2084 ms

bnr_bottom_twogo.jpg

bnr_bottom_twogo.jpg

1555 ms

analytics.js

analytics.js

16 ms

js

js

60 ms

collect

collect

12 ms

collect

collect

142 ms

ga-audiences

ga-audiences

157 ms

gzCy-hx--rE.css

gzCy-hx--rE.css

30 ms

lhzi7nlXu3o.css

lhzi7nlXu3o.css

35 ms

uDSuoOQ7RZ1.css

uDSuoOQ7RZ1.css

36 ms

RsWZ-myCkRn.js

RsWZ-myCkRn.js

42 ms

71nLmDRGsWE.js

71nLmDRGsWE.js

39 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

39 ms

5hjr18zii08.js

5hjr18zii08.js

41 ms

zYzGplAqD4J.js

zYzGplAqD4J.js

39 ms

p55HfXW__mM.js

p55HfXW__mM.js

40 ms

btW70syVT6v.js

btW70syVT6v.js

41 ms

ywjcIatsjHa.js

ywjcIatsjHa.js

72 ms

4RIW-HrYocA.js

4RIW-HrYocA.js

86 ms

4Za9TE_Wiy4.js

4Za9TE_Wiy4.js

81 ms

OSjeAdWp3LG.js

OSjeAdWp3LG.js

83 ms

CkL1MBePXJW.js

CkL1MBePXJW.js

82 ms

8SEqTYRL4HT.js

8SEqTYRL4HT.js

81 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

84 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

83 ms

306079984_493238272811996_160006166655910656_n.jpg

306079984_493238272811996_160006166655910656_n.jpg

44 ms

305315859_493238276145329_1253467307851417807_n.jpg

305315859_493238276145329_1253467307851417807_n.jpg

51 ms

0T4g9t4AXAk.js

0T4g9t4AXAk.js

22 ms

7mzhNKqWkDi.js

7mzhNKqWkDi.js

25 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

24 ms

Accessibility Review

ecbb.jp accessibility score

65

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ecbb.jp best practices score

58

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

Browser errors were logged to the console

SEO Factors

ecbb.jp SEO score

67

Search Engine Optimization Advices

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

ecbb.jp

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