Tools & Wizards About Us
bellcurve.jp screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

bellcurve.jp

BellCurve（ベルカーブ）─統計解析ソフト・アンケート集計ソフト

Page Load Speed

5.4 sec in total

First Response

605 ms

Resources Loaded

4.6 sec

Page Rendered

157 ms

bellcurve.jp screenshot

About Website

Welcome to bellcurve.jp homepage info - get ready to check Bell Curve best content for Japan right away, or after learning these important things about bellcurve.jp

Excelに統計解析の機能を追加する統計解析アドインソフト「エクセル統計」、アンケート集計ソフト「秀吉Dplus」のホームページです。株式会社 社会情報サービスのベルカーブが運営しています。

Visit bellcurve.jp

Key Findings

We analyzed Bellcurve.jp page load time and found that the first response time was 605 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

bellcurve.jp performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

bellcurve.jp

605 ms

bellcurve.jp

1116 ms

base_top.css

436 ms

ie7.css

523 ms

jquery.bxslider.css

525 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 84% of them (21 requests) were addressed to the original Bellcurve.jp, 8% (2 requests) were made to Seal.globalsign.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Ssif1.globalsign.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.6 kB (32%)

Content Size

406.7 kB

After Optimization

275.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 38.0 kB

  • Original 42.9 kB
  • After minification 15.3 kB
  • After compression 5.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 27.7 kB, which is 64% 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 38.0 kB or 88% of the original size.

Image Optimization

-27%

Potential reduce by 82.9 kB

  • Original 307.5 kB
  • After minification 224.7 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. Obviously, Bell Curve needs image optimization as it can save up to 82.9 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 5.7 kB

  • Original 44.7 kB
  • After minification 44.3 kB
  • After compression 38.9 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 5.7 kB or 13% of the original size.

CSS Optimization

-44%

Potential reduce by 5.0 kB

  • Original 11.5 kB
  • After minification 11.5 kB
  • After compression 6.5 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. Bellcurve.jp needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (23%)

Requests Now

22

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bellcurve.jp

bellcurve.jp

605 ms

bellcurve.jp

bellcurve.jp

1116 ms

base_top.css

base_top.css

436 ms

ie7.css

ie7.css

523 ms

jquery.bxslider.css

jquery.bxslider.css

525 ms

js

js

66 ms

gmogs_image_115-57_ja.js

gmogs_image_115-57_ja.js

656 ms

jquery.js

jquery.js

596 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

438 ms

qaTab.js

qaTab.js

481 ms

bellcurve200.png

bellcurve200.png

175 ms

cam20240510_mobile.png

cam20240510_mobile.png

644 ms

cam20240510_slider.png

cam20240510_slider.png

778 ms

top_ex20170606.png

top_ex20170606.png

562 ms

top_hd20170606.png

top_hd20170606.png

357 ms

top_statistics230516.png

top_statistics230516.png

695 ms

exone_st150.png

exone_st150.png

486 ms

hd_st150.png

hd_st150.png

519 ms

12390091_100_JP.png

12390091_100_JP.png

687 ms

ssri_logo40.png

ssri_logo40.png

692 ms

gs_noscript_115-57_ja.gif

gs_noscript_115-57_ja.gif

550 ms

icomoon.ttf

icomoon.ttf

709 ms

siteSeal.do

siteSeal.do

2253 ms

bx_loader.gif

bx_loader.gif

464 ms

controls.png

controls.png

535 ms

Accessibility Review

bellcurve.jp accessibility score

92

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

Best Practices

bellcurve.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

bellcurve.jp SEO score

86

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 Bellcurve.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 Bellcurve.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

bellcurve.jp

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