Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ageha.com

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

Page Load Speed

2 sec in total

First Response

767 ms

Resources Loaded

770 ms

Page Rendered

460 ms

ageha.com screenshot

About Website

Visit ageha.com now to see the best up-to-date AgeHa content for Japan and also check out these interesting facts you probably never knew about ageha.com

東京・新木場にある日本最大級のエンターテイメント・スペース ageHa @STUDIO COAST。イベントスケジュールや最先端な情報が満載。

Visit ageha.com

Key Findings

We analyzed Ageha.com page load time and found that the first response time was 767 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

ageha.com performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value70.7 s

0/100

25%

SI (Speed Index)

Value19.7 s

0/100

10%

TBT (Total Blocking Time)

Value9,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.818

4/100

15%

TTI (Time to Interactive)

Value71.2 s

0/100

10%

Network Requests Diagram

ageha.com

767 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Ageha.com and no external sources were called. The less responsive or slowest element that took the longest time to load (767 ms) belongs to the original domain Ageha.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 144 B (34%)

Content Size

420 B

After Optimization

276 B

In fact, the total size of Ageha.com main page is 420 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 420 B which makes up the majority of the site volume.

HTML Optimization

-34%

Potential reduce by 144 B

  • Original 420 B
  • After minification 417 B
  • After compression 276 B

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 144 B or 34% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

ageha.com accessibility score

65

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 [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

ageha.com 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

High

Page has valid source maps

SEO Factors

ageha.com SEO score

83

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

    EN

  • 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 English 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

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: