Access cross-bee.com. 株式会社クロス・ビー – スポーツビジネスグローバルクリエーター

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.347

32/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

cross-bee.com

513 ms

cross-bee.com

676 ms

www.cross-bee.com

1371 ms

gtm.js

47 ms

common.css

341 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 86% of them (73 requests) were addressed to the original Cross-bee.com, 6% (5 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Cross-bee.com.

Content Size

2.8 MB

After Optimization

2.5 MB

In fact, the total size of Cross-bee.com main page is 2.8 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 36.7 kB

Original 45.0 kB
After minification 43.9 kB
After compression 8.3 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 36.7 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 12.2 kB

Original 2.4 MB
After minification 2.4 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. Cross Bee images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 154.6 kB

Original 233.6 kB
After minification 232.3 kB
After compression 79.0 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 154.6 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 115.5 kB

Original 137.7 kB
After minification 130.7 kB
After compression 22.2 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. Cross-bee.com needs all CSS files to be minified and compressed as it can save up to 115.5 kB or 84% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

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.

High

Image elements do not have [alt] attributes

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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/).

High

Document doesn't use 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 Cross-bee.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 Cross-bee.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

cross-bee.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

株式会社クロス・ビー – スポーツビジネスグローバルクリエーター

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

cross-bee.com

cross-bee.com

www.cross-bee.com

gtm.js

common.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

cross-bee.com

cross-bee.com

www.cross-bee.com

gtm.js

common.css

jquery-1.11.1.min.js

jquery-ui.min.js

obj.js

common.js

detail.js

slick.css

slick-theme.css

slick.min.js

index.css

index.js

style.min.css

styles.css

style.css

index.js

index.js

css

common_initialize.css

common_class.css

common_layout.css

common_header.css

common_footer.css

logo.svg

sns_l.svg

sns_f.svg

sns_t.svg

sns_i.svg

sns_n.svg

search.svg

bnr1_pc.jpg

bnr2_pc.jpg

bnr3_pc.jpg

bnr4_pc.jpg

icon_1.svg

1221crossbee00002-768x512.jpg

GettyImages-1397132647-768x512.jpg

566c4c5f48ddc4f8fbeca9740959bf7c_HP-768x512.jpg

GettyImages-1331362842-768x512.jpg

igawa.jpg