Report Summary

  • 97

    Performance

    Renders faster than
    95% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

bex.jp

DOMAIN ERROR

Page Load Speed

4.1 sec in total

First Response

495 ms

Resources Loaded

3.4 sec

Page Rendered

291 ms

bex.jp screenshot

About Website

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

Visit bex.jp

Key Findings

We analyzed Bex.jp page load time and found that the first response time was 495 ms and then it took 3.6 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

bex.jp performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.2 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value3.6 s

92/100

10%

Network Requests Diagram

bex.jp

495 ms

style.css

323 ms

jquery.min.js

1328 ms

jquery.fittext.js

368 ms

tokyo_tower.jpg

2526 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 56% of them (5 requests) were addressed to the original Bex.jp, 33% (3 requests) were made to Google-analytics.com and 11% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Bex.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.5 kB (12%)

Content Size

877.5 kB

After Optimization

776.0 kB

In fact, the total size of Bex.jp main page is 877.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 719.7 kB which makes up the majority of the site volume.

HTML Optimization

-55%

Potential reduce by 1.3 kB

  • Original 2.3 kB
  • After minification 2.1 kB
  • After compression 1.1 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 245 B, which is 11% 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 1.3 kB or 55% of the original size.

Image Optimization

-0%

Potential reduce by 863 B

  • Original 719.7 kB
  • After minification 718.9 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. Bex images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 97.8 kB

  • Original 153.1 kB
  • After minification 151.2 kB
  • After compression 55.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 97.8 kB or 64% of the original size.

CSS Optimization

-67%

Potential reduce by 1.5 kB

  • Original 2.3 kB
  • After minification 1.9 kB
  • After compression 766 B

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. Bex.jp needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 67% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bex. According to our analytics all requests are already optimized.

Accessibility Review

bex.jp accessibility score

68

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.

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 valid value for its [lang] attribute.

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

bex.jp best practices score

83

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

SEO Factors

bex.jp SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

High

robots.txt is not valid

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

    JP

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bex.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed language. Our system also found out that Bex.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 description is not detected on the main page of Bex. 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: