7.9 sec in total
951 ms
6.8 sec
178 ms
Visit a-aia.com now to see the best up-to-date A Aia content for Japan and also check out these interesting facts you probably never knew about a-aia.com
新幹線・JR特急列車きっぷ予約サイト。みどりの窓口に並はず買ったきっぷはご自宅や職場へお届け。
Visit a-aia.comWe analyzed A-aia.com page load time and found that the first response time was 951 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
a-aia.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.2 s
11/100
25%
Value7.3 s
28/100
10%
Value120 ms
97/100
30%
Value0
100/100
15%
Value7.0 s
53/100
10%
951 ms
330 ms
1243 ms
665 ms
348 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 97% of them (58 requests) were addressed to the original A-aia.com, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain A-aia.com.
Page size can be reduced by 191.8 kB (36%)
531.1 kB
339.3 kB
In fact, the total size of A-aia.com main page is 531.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 269.2 kB which makes up the majority of the site volume.
Potential reduce by 22.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 22.2 kB or 79% of the original size.
Potential reduce by 10.3 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. A Aia images are well optimized though.
Potential reduce by 118.2 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 118.2 kB or 64% of the original size.
Potential reduce by 41.1 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. A-aia.com needs all CSS files to be minified and compressed as it can save up to 41.1 kB or 83% of the original size.
Number of requests can be reduced by 18 (31%)
59
41
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A Aia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
a-aia.com
951 ms
styles.css
330 ms
jquery-1.7.2.min.js
1243 ms
common.js
665 ms
smoothscroll.js
348 ms
slidedown.js
350 ms
jquery.carouFredSel-2.5.5.js
1038 ms
jquery.validate.min.js
876 ms
script.js
687 ms
common.css
391 ms
module.css
665 ms
contents.css
1270 ms
js.css
756 ms
prints.css
917 ms
header_bg.jpg
723 ms
logo_alpha.jpg
349 ms
hnavi01_alpha.jpg
360 ms
hnavi02_alpha.jpg
369 ms
login-btn.png
366 ms
gnavi_bg.gif
370 ms
gnavi01_over.jpg
688 ms
gnavi02_over.jpg
697 ms
subnavi_bg.png
715 ms
gnavi03_over.jpg
726 ms
gnavi04_over.jpg
728 ms
gnavi05_over.jpg
1043 ms
gnavi06_over.jpg
1050 ms
gnavi07_over.jpg
1046 ms
main_img_01.jpg
2486 ms
main_img_02.jpg
2801 ms
main_img_03.jpg
2763 ms
main_img_04.jpg
2976 ms
main_img_05.jpg
3027 ms
h3_img02.jpg
1584 ms
h3_img01.jpg
2170 ms
h3_ttl_mokuteki.jpg
3007 ms
h3_ttl_syupatu.jpg
3266 ms
mini_banner_01.jpg
3265 ms
mini_banner_02.jpg
3330 ms
mini_banner_03.jpg
3533 ms
mini_banner_04.jpg
3504 ms
mini_banner_05.jpg
3560 ms
h3_img03.jpg
3631 ms
register_btn.gif
3644 ms
sdie_ttl01.gif
3668 ms
search_alpha.gif
3852 ms
sdie_ttl03.gif
3845 ms
img_tel.jpg
4073 ms
f_logo.png
3955 ms
news
4019 ms
ga.js
25 ms
__utm.gif
11 ms
f_imgtext.png
3650 ms
copyright.png
3844 ms
mainimg_bg.gif
3841 ms
nav_bg.gif
3965 ms
sidebox_bg.gif
3983 ms
icon02.gif
3676 ms
footer_bg.jpg
3757 ms
sdie_ttl02.gif
513 ms
a-aia.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
ARIA
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.
Impact
Issue
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
a-aia.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
a-aia.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A-aia.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 A-aia.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.
a-aia.com
Open Graph description is not detected on the main page of A Aia. 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: