Tools & Wizards About Us
a-i-a.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

a-i-a.co.jp

コスパの高いノベルティで常に先を行く販促戦略｜AIA株式会社

Page Load Speed

5.2 sec in total

First Response

772 ms

Resources Loaded

4.2 sec

Page Rendered

216 ms

a-i-a.co.jp screenshot

About Website

Click here to check amazing A I content. Otherwise, check out these important facts you probably never knew about a-i-a.co.jp

ノベルティの制作・販売促進戦略を立案しているAIA株式会社です。半歩先を行く革新的なアイディアで、高いコストパフォーマンスのノベルティや販促品の制作をしてます。ノベルティでのセールスプロモーションの企画立案まで提案致します。お気軽にご相談下さい。

Visit a-i-a.co.jp

Key Findings

We analyzed A-i-a.co.jp page load time and found that the first response time was 772 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

a-i-a.co.jp performance score

0

Network Requests Diagram

a-i-a.co.jp

772 ms

reset.css

332 ms

module.css

496 ms

common.css

340 ms

index.css

343 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 96% of them (27 requests) were addressed to the original A-i-a.co.jp, 4% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain A-i-a.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.3 kB (1%)

Content Size

3.1 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of A-i-a.co.jp main page is 3.1 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 10% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 6.1 kB

  • Original 8.2 kB
  • After minification 6.3 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 1.9 kB, which is 23% 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 6.1 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 16.4 kB

  • Original 3.1 MB
  • After minification 3.0 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. A I images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 5.5 kB

  • Original 8.2 kB
  • After minification 7.1 kB
  • After compression 2.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 5.5 kB or 68% of the original size.

CSS Optimization

-76%

Potential reduce by 13.2 kB

  • Original 17.4 kB
  • After minification 12.5 kB
  • After compression 4.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. A-i-a.co.jp needs all CSS files to be minified and compressed as it can save up to 13.2 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (35%)

Requests Now

26

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

a-i-a.co.jp

a-i-a.co.jp

772 ms

reset.css

reset.css

332 ms

module.css

module.css

496 ms

common.css

common.css

340 ms

index.css

index.css

343 ms

logo.png

logo.png

367 ms

index.php

index.php

241 ms

jquery.min.js

jquery.min.js

71 ms

opacity-rollover2.1.js

opacity-rollover2.1.js

347 ms

jquery.bgSwitcher-min.js

jquery.bgSwitcher-min.js

348 ms

fade.js

fade.js

349 ms

common.js

common.js

370 ms

jcarousellite_1.0.1.js

jcarousellite_1.0.1.js

777 ms

side_btn.png

side_btn.png

1465 ms

logo_aia.png

logo_aia.png

641 ms

style.css

style.css

426 ms

bg_header.png

bg_header.png

173 ms

navigation.png

navigation.png

470 ms

shadow.png

shadow.png

345 ms

bg_news.png

bg_news.png

479 ms

bg_ftr.png

bg_ftr.png

505 ms

bg_line.png

bg_line.png

514 ms

pagetop.png

pagetop.png

808 ms

img_mainvisual01.jpg

img_mainvisual01.jpg

2605 ms

img_mainvisual02.jpg

img_mainvisual02.jpg

2158 ms

img_mainvisual03.jpg

img_mainvisual03.jpg

2064 ms

img_mainvisual04.jpg

img_mainvisual04.jpg

2476 ms

img_mainvisual05.jpg

img_mainvisual05.jpg

1963 ms

SEO Factors

a-i-a.co.jp SEO score

0

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 A-i-a.co.jp 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 A-i-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

a-i-a.co.jp

Open Graph data is detected on the main page of A I. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: