Access flypeach.com. 【公式】Peach ピーチ

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,740 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.388

26/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

flypeach.com

351 ms

home.aspx

25 ms

default.css

17 ms

module.css

22 ms

module.css

20 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 90% of them (91 requests) were addressed to the original Flypeach.com, 4% (4 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (385 ms) belongs to the original domain Flypeach.com.

Content Size

3.7 MB

After Optimization

3.4 MB

In fact, the total size of Flypeach.com main page is 3.7 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 63.4 kB

Original 105.6 kB
After minification 100.0 kB
After compression 42.2 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 63.4 kB or 60% of the original size.

Image Optimization

-3%

Potential reduce by 98.2 kB

Original 3.4 MB
After minification 3.3 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. Fly Peach images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 171.0 kB

Original 220.7 kB
After minification 204.8 kB
After compression 49.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 171.0 kB or 77% of the original size.

CSS Optimization

-75%

Potential reduce by 4.9 kB

Original 6.5 kB
After minification 6.1 kB
After compression 1.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. Flypeach.com needs all CSS files to be minified and compressed as it can save up to 4.9 kB or 75% of the original size.

Requests Now

After Optimization

The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fly Peach. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 15 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 input fields do not have accessible names

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 keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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

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

Search Engine Optimization Advices

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

High

Links are not crawlable

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

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flypeach.com 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 English language. Our system also found out that Flypeach.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

flypeach.com

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

【公式】Peach ピーチ | Peach Aviation株式会社

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

flypeach.com

home.aspx

default.css

module.css

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

flypeach.com

home.aspx

default.css

module.css

module.css

module.css

skin.css

ibe-transparent.css

portal.css

module.css

ComboBox.Default.css

jquery.min.js

jquery-ui.min.js

superfish.css

redirect.js

superfish.css

superfish.css

WebResource.axd

Telerik.Web.UI.WebResource.axd

jquery.hoverIntent.min.js

dnn.jquery.js

dnncore.js

ControlPanel.debug.js

opennewwindow.js

Region.js

jsDatePick_ltr.min.css

widgetvars.js

TabBasedB2C.js

jsDatePick.jquery.min.1.3.js

jquery.anntransformer.min.js

initWidgets.js

widgets.js

hoverIntent.js

peach-logo.png

f_logo.png

t_logo.png

y_logo.png

sp_bt_1.jpg

sp_bt_2.jpg

tbn_summerschedule2016_20160219_en.png

tbn_nrtoka_launch_20151201_en.jpg

tbn_hndtpe_launch_20151127_en.jpg

tbn_kixkmi_onsale_20150417_en.png