Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

bell-face.com

【公式】ベルフェイス - 金融シェアNo.1 電話面談システム

Page Load Speed

3.9 sec in total

First Response

334 ms

Resources Loaded

3.3 sec

Page Rendered

244 ms

bell-face.com screenshot

About Website

Click here to check amazing Bell Face content for Japan. Otherwise, check out these important facts you probably never knew about bell-face.com

金融シェアNo.1 電話面談システム「ベルフェイス」の接続ナンバー発行ページです。担当者から電話で案内をうけた後、サイト上の「接続ナンバーを発行」ボタンをクリックし、4桁の番号を伝えるだけですぐにオンライン商談を始めることができます。

Visit bell-face.com

Key Findings

We analyzed Bell-face.com page load time and found that the first response time was 334 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

bell-face.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value36.4 s

0/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value33.6 s

0/100

10%

Network Requests Diagram

bell-face.com

334 ms

bell-face.com

852 ms

first-page.css

151 ms

font-awesome.min.css

65 ms

jquery.min.js

108 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 28% of them (8 requests) were addressed to the original Bell-face.com, 21% (6 requests) were made to User.bell-face.com and 7% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Bell-face.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 226.6 kB (35%)

Content Size

646.1 kB

After Optimization

419.5 kB

In fact, the total size of Bell-face.com main page is 646.1 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. 25% of websites need less resources to load. Javascripts take 339.1 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 12.3 kB

  • Original 17.5 kB
  • After minification 16.4 kB
  • After compression 5.2 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 12.3 kB or 70% of the original size.

Image Optimization

-2%

Potential reduce by 4.4 kB

  • Original 256.8 kB
  • After minification 252.4 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. Bell Face images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 185.6 kB

  • Original 339.1 kB
  • After minification 339.1 kB
  • After compression 153.5 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 185.6 kB or 55% of the original size.

CSS Optimization

-74%

Potential reduce by 24.3 kB

  • Original 32.8 kB
  • After minification 32.2 kB
  • After compression 8.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. Bell-face.com needs all CSS files to be minified and compressed as it can save up to 24.3 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (50%)

Requests Now

26

After Optimization

13

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

Accessibility Review

bell-face.com accessibility score

74

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

Links do not have a discernible name

Best Practices

bell-face.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

bell-face.com 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

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

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

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 Bell-face.com 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 Bell-face.com 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 description is not detected on the main page of Bell Face. 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: