6.3 sec in total
193 ms
6 sec
177 ms
Welcome to my-aime.net homepage info - get ready to check My Aime best content for Japan right away, or after learning these important things about my-aime.net
Aimeサービスサイトでアーケードゲームがもっと楽しくなる!Aimeカードの登録や登録内容の変更、Aime対応タイトルの確認ができます。登録無料。PCでもスマートフォンでも利用できます
Visit my-aime.netWe analyzed My-aime.net page load time and found that the first response time was 193 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
my-aime.net performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value9.7 s
0/100
25%
Value7.8 s
23/100
10%
Value330 ms
75/100
30%
Value0.108
88/100
15%
Value10.4 s
24/100
10%
193 ms
177 ms
352 ms
881 ms
726 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 97% of them (70 requests) were addressed to the original My-aime.net, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain My-aime.net.
Page size can be reduced by 144.0 kB (19%)
762.9 kB
618.9 kB
In fact, the total size of My-aime.net main page is 762.9 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. 20% of websites need less resources to load. Images take 613.6 kB which makes up the majority of the site volume.
Potential reduce by 9.8 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 9.8 kB or 71% of the original size.
Potential reduce by 48.0 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. My Aime images are well optimized though.
Potential reduce by 38.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 38.7 kB or 48% of the original size.
Potential reduce by 47.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. My-aime.net needs all CSS files to be minified and compressed as it can save up to 47.4 kB or 85% of the original size.
Number of requests can be reduced by 9 (13%)
71
62
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Aime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for CSS and as a result speed up the page load time.
193 ms
common-import.css
177 ms
home.css
352 ms
jquery.js
881 ms
jquery.slider.js
726 ms
reset.css
580 ms
set.css
587 ms
layout.css
703 ms
module.css
711 ms
navigation.css
730 ms
class.css
767 ms
form.css
777 ms
mypage.css
878 ms
analytics.js
46 ms
background.gif
181 ms
aime.gif
193 ms
salesmessage.gif
194 ms
globalnav.gif
361 ms
gnav_news.gif
182 ms
gnav_about.gif
179 ms
gnav_site.gif
353 ms
gnav_faq.gif
351 ms
gnav_service.gif
357 ms
gnav_mypage.gif
378 ms
mainarea.jpg
381 ms
btn_slidebanner.gif
527 ms
top_banner002.jpg
872 ms
top_banner003.jpg
1589 ms
top_banner004.jpg
1430 ms
top_banner005.jpg
1310 ms
top_banner006.jpg
1511 ms
btn_slidebanner.png
700 ms
bnr_sengoku.jpg
1048 ms
bnr_wccf.jpg
1045 ms
bnr_maimai.jpg
1221 ms
bnr_crossbeats.jpg
1224 ms
bnr_ggrev.jpg
1395 ms
bnr_dfci.jpg
1397 ms
bnr_unist.jpg
1496 ms
bnr_coj.jpg
1570 ms
bnr_sh3.jpg
1573 ms
bnr_chuni.jpg
3167 ms
bnr_wonder.jpg
1683 ms
bnr_bafs.jpg
2706 ms
bnr_mj5.jpg
1745 ms
bnr_3kingdoms.jpg
1748 ms
bnr_ggxrd.jpg
2510 ms
bnr_doa5.jpg
1870 ms
bnr_divaacft.jpg
1920 ms
bnr_puyoq.jpg
1913 ms
collect
23 ms
bnr_horukatoruka.jpg
1891 ms
bnr_ggxx.jpg
1924 ms
bnr_uni.jpg
1924 ms
bnr_ladyluck.jpg
2067 ms
bnr_bingodrop.jpg
2088 ms
bnr_paradice.jpg
2101 ms
bnr_sb.jpg
2095 ms
bnr_apm.jpg
2099 ms
sega.gif
2276 ms
h3_news.gif
2250 ms
link_arrow.gif
2249 ms
link.gif
2166 ms
lnav_block.gif
2100 ms
lnav_segaidlogin.gif
1931 ms
localnav_btn.gif
1774 ms
lnav_beginner.gif
1821 ms
lnav_segaidmember.gif
1678 ms
h3_service.gif
1749 ms
blank.gif
1668 ms
pagetop.gif
1612 ms
copyright.gif
1646 ms
my-aime.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
my-aime.net 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
General
Impact
Issue
Detected JavaScript libraries
my-aime.net 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
Document doesn't have a valid hreflang
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My-aime.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that My-aime.net 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.
my-aime.net
Open Graph description is not detected on the main page of My Aime. 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: