Tools & Wizards About Us
my.aicom.ne.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

my.aicom.ne.jp

亜太電信株式会社

Page Load Speed

6 sec in total

First Response

593 ms

Resources Loaded

4.8 sec

Page Rendered

634 ms

my.aicom.ne.jp screenshot

About Website

Visit my.aicom.ne.jp now to see the best up-to-date My Aicom content for Japan and also check out these interesting facts you probably never knew about my.aicom.ne.jp

亜太電信株式会社は、プリペイド式格安スマホ・格安SIM、WIFIルーターなどのモバイル通信サービスや、格安国内、国際電話カード、通話カードを提供する会社です。個人様も法人様もご利用いただけます。docomo SIM、softbank SIMを提供、月額料金は格安です。PREPAID MOBILE、PREPAID SIM CARD、WiFi Router、low-cost data only SIM...

Visit my.aicom.ne.jp

Key Findings

We analyzed My.aicom.ne.jp page load time and found that the first response time was 593 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

my.aicom.ne.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.899

3/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

my.aicom.ne.jp

593 ms

my.aicom.ne.jp

665 ms

www.aicom.ne.jp

900 ms

bootstrap.min.css

330 ms

buspo-icons.css

494 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original My.aicom.ne.jp, 94% (59 requests) were made to Aicom.ne.jp and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Aicom.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 289.0 kB (10%)

Content Size

2.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of My.aicom.ne.jp main page is 2.8 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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 19.9 kB

  • Original 24.9 kB
  • After minification 17.5 kB
  • After compression 5.0 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 7.4 kB, which is 30% 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 19.9 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 221.6 kB

  • Original 2.5 MB
  • After minification 2.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. My Aicom images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 25.6 kB

  • Original 152.9 kB
  • After minification 152.9 kB
  • After compression 127.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 25.6 kB or 17% of the original size.

CSS Optimization

-29%

Potential reduce by 22.0 kB

  • Original 75.2 kB
  • After minification 75.2 kB
  • After compression 53.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. My.aicom.ne.jp needs all CSS files to be minified and compressed as it can save up to 22.0 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (41%)

Requests Now

58

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

my.aicom.ne.jp

my.aicom.ne.jp

593 ms

my.aicom.ne.jp

my.aicom.ne.jp

665 ms

www.aicom.ne.jp

www.aicom.ne.jp

900 ms

bootstrap.min.css

bootstrap.min.css

330 ms

buspo-icons.css

buspo-icons.css

494 ms

font-awesome.min.css

font-awesome.min.css

495 ms

magnific-popup.css

magnific-popup.css

494 ms

owl.carousel.min.css

owl.carousel.min.css

507 ms

animate.css

animate.css

510 ms

swiper-bundle.min.css

swiper-bundle.min.css

523 ms

main.css

main.css

822 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

659 ms

popper.min.js

popper.min.js

660 ms

bootstrap.min.js

bootstrap.min.js

900 ms

scrollUp.min.js

scrollUp.min.js

678 ms

magnific-popup.min.js

magnific-popup.min.js

698 ms

waypoints.min.js

waypoints.min.js

898 ms

jquery.counterup.min.js

jquery.counterup.min.js

898 ms

owl.carousel.min.js

owl.carousel.min.js

899 ms

wow.min.js

wow.min.js

900 ms

swiper-bundle.min.js

swiper-bundle.min.js

1150 ms

bootstrap-input-spinner.js

bootstrap-input-spinner.js

988 ms

lightbox.min.css

lightbox.min.css

990 ms

lightbox.min.js

lightbox.min.js

1013 ms

toast.css

toast.css

1018 ms

toast.js

toast.js

1047 ms

script.js

script.js

1153 ms

common.js

common.js

1154 ms

js

js

68 ms

logo.png

logo.png

349 ms

logo_mobile3.png

logo_mobile3.png

350 ms

all_banner_global_wifi_ata_3.jpg

all_banner_global_wifi_ata_3.jpg

1251 ms

simcard-banner.jpg

simcard-banner.jpg

801 ms

prepaidmobile-banner.jpg

prepaidmobile-banner.jpg

801 ms

cards-banner_2.jpg

cards-banner_2.jpg

805 ms

sumaho-banner.jpg

sumaho-banner.jpg

847 ms

index_index_left.png

index_index_left.png

855 ms

index_index_right.png

index_index_right.png

966 ms

simcard-left.png

simcard-left.png

1129 ms

simcard-right.jpg

simcard-right.jpg

1134 ms

payway_smartpit_logo.png

payway_smartpit_logo.png

1016 ms

aicom_smartpit_card_2.png

aicom_smartpit_card_2.png

1026 ms

card01.gif

card01.gif

1130 ms

card02.gif

card02.gif

1188 ms

card03.gif

card03.gif

1197 ms

card04.gif

card04.gif

1295 ms

prepaidmobile-left.png

prepaidmobile-left.png

1457 ms

prepaidmobile-right1.jpg

prepaidmobile-right1.jpg

1299 ms

ito-banner.jpg

ito-banner.jpg

1526 ms

facebook_logo_qrcode.png

facebook_logo_qrcode.png

1366 ms

twitter_logo_qrcode.png

twitter_logo_qrcode.png

1425 ms

youtube_logo_qrcode.png

youtube_logo_qrcode.png

1405 ms

instagram_logo.png

instagram_logo.png

1410 ms

line_logo_qrcode.png

line_logo_qrcode.png

1482 ms

wechat_logo_qrcode.png

wechat_logo_qrcode.png

1544 ms

line_qrcode.png

line_qrcode.png

1565 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1558 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

1 ms

wechat_qrcode.png

wechat_qrcode.png

1486 ms

prev.png

prev.png

1375 ms

next.png

next.png

1385 ms

loading.gif

loading.gif

1454 ms

close.png

close.png

1462 ms

Accessibility Review

my.aicom.ne.jp accessibility score

90

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

my.aicom.ne.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

High

Page has valid source maps

SEO Factors

my.aicom.ne.jp SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

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 My.aicom.ne.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 My.aicom.ne.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

my.aicom.ne.jp

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