Access ageha.com. ageHa [東京・新木場にある日本最大級のエンターテイメント・スペース]

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.133

81/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

207 ms

coin-slider-styles.css

167 ms

base.css.php

501 ms

responsive.css

333 ms

jquery.min.js

8 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 29% of them (30 requests) were addressed to the original Ageha.com, 18% (19 requests) were made to D38fgd7fmrcuct.cloudfront.net and 12% (13 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Zaiko.io.

Content Size

1.5 MB

After Optimization

1.4 MB

In fact, the total size of Ageha.com main page is 1.5 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 992.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 47.5 kB

Original 57.3 kB
After minification 53.2 kB
After compression 9.8 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 47.5 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 24.5 kB

Original 992.3 kB
After minification 967.8 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. AgeHa images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 46.3 kB

Original 356.3 kB
After minification 356.2 kB
After compression 310.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 46.3 kB or 13% of the original size.

CSS Optimization

-2%

Potential reduce by 1.6 kB

Original 65.2 kB
After minification 65.2 kB
After compression 63.6 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. Ageha.com has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

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

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

<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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

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

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ageha.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ageha.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

ageha.com

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

ageHa [東京・新木場にある日本最大級のエンターテイメント・スペース]

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

coin-slider-styles.css

base.css.php

responsive.css

jquery.min.js

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

coin-slider-styles.css

base.css.php

responsive.css

jquery.min.js

coin-slider.min.js

oauth.js

sha1.js

twitter.js

common.js

shadowbox.css

shadowbox.js

jquery.lazyload.min.js

jplayer.blue.monday.css

jquery.jplayer.min.js

conversion.js

s_retargeting.js

oct.js

s_retargeting.js

1_44vq1jvoktpruscb3707x.gif

1_44vq1kj1g6wpb6el0sqm9.gif

1_44tnjon5w4c1dh7d2firq.png

1_44snjqsavmff1byt2ph93.png

1_3yo2ic5uivben5d052gu0.png

1_42kc3yh9p2tpg2g7t8cpr.png

1_42kc2xu86luxmduf03vtu.png

1_3vro523aq3nbim0deowyn.png

1_3vtpko3uld8r7o5mnfiio.png

1_44tnjsd0n92p2wqh2j05y.jpg

1_45ew55v4ok6wqdq9chteq.jpg

1_4578ivr2ckhk17d7rm9ex.jpg

1_44sn7alkpr0mgrw477vpi.jpg

icon_top.png

all.js.php

1_3goww2f6o6b4xc2cpiio9.png

logo_plain.png

marquee_mask-new.png

arrow-l.png

arrow-r.png

Proxima_Nova_Regular.otf

Proxima_Nova_Bold.otf

ageha_icons.png

icon_iflyer.png

icon_instagram.png

icon_twitter.png