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

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

a-m-i.co.jp

朝日メディアインターナショナル株式会社

Page Load Speed

6.7 sec in total

First Response

886 ms

Resources Loaded

4.1 sec

Page Rendered

1.7 sec

a-m-i.co.jp screenshot

About Website

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

出版業界を中心に書籍・雑誌のデザイン・組版・印刷の制作業務を行っております。装丁、本文デザイン、エディトリアルデザイン、組版制作、図版制作、画像処理、印刷、電子書籍など、一連の制作をすべて請け負います。フリーランスDTPオペレーター募集中

Visit a-m-i.co.jp

Key Findings

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

Performance Metrics

a-m-i.co.jp performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.085

93/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

a-m-i.co.jp

886 ms

style.css

686 ms

reset.css

352 ms

css2

42 ms

slick.css

23 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 77% of them (67 requests) were addressed to the original A-m-i.co.jp, 13% (11 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain A-m-i.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 269.3 kB (3%)

Content Size

9.9 MB

After Optimization

9.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of A-m-i.co.jp main page is 9.9 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 9.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 48.3 kB

  • Original 55.0 kB
  • After minification 30.0 kB
  • After compression 6.7 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 25.0 kB, which is 45% 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 48.3 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 133.9 kB

  • Original 9.6 MB
  • After minification 9.5 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 M I images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 4.8 kB

  • Original 84.2 kB
  • After minification 84.2 kB
  • After compression 79.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-88%

Potential reduce by 82.4 kB

  • Original 93.8 kB
  • After minification 93.2 kB
  • After compression 11.4 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-m-i.co.jp needs all CSS files to be minified and compressed as it can save up to 82.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (19%)

Requests Now

75

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A M 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 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

a-m-i.co.jp

a-m-i.co.jp

886 ms

style.css

style.css

686 ms

reset.css

reset.css

352 ms

css2

css2

42 ms

slick.css

slick.css

23 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

24 ms

slick.min.js

slick.min.js

26 ms

main.js

main.js

354 ms

embed

embed

305 ms

logo.svg

logo.svg

199 ms

logo_blue.svg

logo_blue.svg

197 ms

search.svg

search.svg

200 ms

magnifier.svg

magnifier.svg

198 ms

facebook_bg.svg

facebook_bg.svg

374 ms

twitter_bg.svg

twitter_bg.svg

376 ms

prev.svg

prev.svg

378 ms

next.svg

next.svg

374 ms

t

t

1086 ms

new_img1.svg

new_img1.svg

379 ms

t

t

912 ms

t

t

1252 ms

t

t

1254 ms

t

t

1083 ms

t

t

1255 ms

t

t

1090 ms

t

t

1441 ms

t

t

1276 ms

t

t

1275 ms

line_up.svg

line_up.svg

1428 ms

check_blue.svg

check_blue.svg

1435 ms

t

t

1613 ms

t

t

1456 ms

t

t

1463 ms

t

t

1782 ms

t

t

1787 ms

t

t

1622 ms

t

t

1637 ms

t

t

1650 ms

t

t

1967 ms

t

t

1805 ms

t

t

1815 ms

t

t

1835 ms

t

t

1972 ms

t

t

1975 ms

t

t

1881 ms

VdGEAYIAV6gnpUpoWwNkYvrugw9RuPWG.ttf

VdGEAYIAV6gnpUpoWwNkYvrugw9RuPWG.ttf

45 ms

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM1y55sK.ttf

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM1y55sK.ttf

406 ms

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM0q5psK.ttf

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM0q5psK.ttf

410 ms

VdGCAYIAV6gnpUpoWwNkYvrugw9RuM3ixLs.ttf

VdGCAYIAV6gnpUpoWwNkYvrugw9RuM3ixLs.ttf

471 ms

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM064ZsK.ttf

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM064ZsK.ttf

407 ms

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM0m4psK.ttf

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM0m4psK.ttf

359 ms

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM0C45sK.ttf

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM0C45sK.ttf

312 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDL7E.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDL7E.ttf

358 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODL7E.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODL7E.ttf

360 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EL7E.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EL7E.ttf

360 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EL7E.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EL7E.ttf

410 ms

t

t

1800 ms

t

t

1825 ms

t

t

1955 ms

t

t

1960 ms

js

js

26 ms

search.js

search.js

4 ms

geometry.js

geometry.js

7 ms

main.js

main.js

11 ms

t

t

1793 ms

t

t

1803 ms

t

t

1799 ms

t

t

1822 ms

t

t

1955 ms

card_img1.png

card_img1.png

1597 ms

card_img2.png

card_img2.png

1285 ms

card_img3b.png

card_img3b.png

1266 ms

card_img4.png

card_img4.png

1281 ms

card_img5.png

card_img5.png

1163 ms

card_img6.png

card_img6.png

1264 ms

card_img7.png

card_img7.png

1269 ms

icon_1.svg

icon_1.svg

1268 ms

icon_2.svg

icon_2.svg

1270 ms

icon_3.svg

icon_3.svg

1159 ms

icon_4.svg

icon_4.svg

1244 ms

icon_5.svg

icon_5.svg

1252 ms

icon_6.svg

icon_6.svg

1238 ms

icon_7.svg

icon_7.svg

1254 ms

icon_8.svg

icon_8.svg

1105 ms

icon_9.svg

icon_9.svg

1146 ms

facebook.svg

facebook.svg

1223 ms

twitter.svg

twitter.svg

1217 ms

Accessibility Review

a-m-i.co.jp accessibility score

72

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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.

Best Practices

a-m-i.co.jp best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

a-m-i.co.jp SEO score

100

Search Engine Optimization Advices

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A-m-i.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 A-m-i.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-m-i.co.jp

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