Access try-a.co.jp. TRY-A / AYATO TRIATHLON SCHOOL / TRY-A+ 公式サイト

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value28.4 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.524

15/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

try-a.co.jp

1505 ms

wrap_style.css

187 ms

common.css

358 ms

flexslider.css

357 ms

jquery.js

541 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 86% of them (80 requests) were addressed to the original Try-a.co.jp, 8% (7 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Try-a.co.jp.

Content Size

7.3 MB

After Optimization

6.7 MB

In fact, the total size of Try-a.co.jp main page is 7.3 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. Only a small number of websites need less resources to load. Images take 7.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 33.0 kB

Original 40.5 kB
After minification 34.4 kB
After compression 7.5 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 6.1 kB, which is 15% 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 33.0 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 460.0 kB

Original 7.0 MB
After minification 6.6 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. TRY A images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 27.2 kB

Original 158.0 kB
After minification 157.1 kB
After compression 130.7 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 27.2 kB or 17% of the original size.

CSS Optimization

-46%

Potential reduce by 9.6 kB

Original 20.8 kB
After minification 20.8 kB
After compression 11.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. Try-a.co.jp needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 46% of the original size.

Requests Now

After Optimization

The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TRY A. 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 from 4 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 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

Definition list items are not wrapped in <dl> 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 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

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 uses 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 Try-a.co.jp 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 Try-a.co.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

try-a.co.jp

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

TRY-A / AYATO TRIATHLON SCHOOL / TRY-A+ 公式サイト

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

try-a.co.jp

wrap_style.css

common.css

flexslider.css

jquery.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

try-a.co.jp

wrap_style.css

common.css

flexslider.css

jquery.js

ie.js

common.js

jquery.flexslider.js

jquery.bxslider.min.js

js

googlemap_plus.js

header_navi.js

footer_navi.js

js

js

wp-embed.min.js

notosansjapanese.css

wp-emoji-release.min.js

banner_pc_20231214.jpg

banner_sp_20231214.jpg

08.jpg

sp08.jpg

try-a_banner_2022_04_pc.jpg

try-a_banner_2022_04_sp.jpg

07.jpg

sp07.jpg

06.jpg

sp06.jpg

09.jpg

sp09.jpg

pc_try_A+.jpg

sp_try_A+.jpg

03.jpg

sp03.jpg

01.jpg

sp01.jpg

muryou_pc.svg

muryou_sp.svg

icon_header_trya_down.png

logo_ayato01.png

logo_plus01.png

title_news.jpg

news_logo_trya.jpg