7.2 sec in total
683 ms
6.2 sec
247 ms
Welcome to otomate.jp homepage info - get ready to check Otomate best content for Japan right away, or after learning these important things about otomate.jp
「オトメイト」はアイディアファクトリーグループの女性向けブランドの名称です。
Visit otomate.jpWe analyzed Otomate.jp page load time and found that the first response time was 683 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
otomate.jp performance score
name
value
score
weighting
Value11.4 s
0/100
10%
Value13.8 s
0/100
25%
Value16.2 s
0/100
10%
Value460 ms
61/100
30%
Value0.147
77/100
15%
Value26.7 s
0/100
10%
683 ms
173 ms
795 ms
319 ms
326 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 92% of them (87 requests) were addressed to the original Otomate.jp, 6% (6 requests) were made to Ideaf.co.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Ideaf.co.jp.
Page size can be reduced by 224.4 kB (7%)
3.4 MB
3.1 MB
In fact, the total size of Otomate.jp main page is 3.4 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. 45% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 17.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 4.0 kB, which is 18% 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 17.7 kB or 81% of the original size.
Potential reduce by 68.2 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. Otomate images are well optimized though.
Potential reduce by 111.5 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 111.5 kB or 66% of the original size.
Potential reduce by 27.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. Otomate.jp needs all CSS files to be minified and compressed as it can save up to 27.1 kB or 82% of the original size.
Number of requests can be reduced by 5 (5%)
94
89
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otomate. 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 as a result speed up the page load time.
otomate.jp
683 ms
base.css
173 ms
jquery-1.8.2.min.js
795 ms
jquery.easing.1.3.js
319 ms
all.js
326 ms
news.json
2126 ms
news.js
769 ms
topslider.css
335 ms
top.css
337 ms
topslider.js
814 ms
analytics.js
5 ms
collect
12 ms
bg_x.gif
173 ms
head.jpg
172 ms
oto_logo.gif
171 ms
loading.jpg
318 ms
circle.png
159 ms
btm.png
162 ms
game.jpg
316 ms
goods.jpg
324 ms
tv_radio.jpg
338 ms
fair_event.jpg
337 ms
news_backnum.gif
338 ms
banner01.jpg
629 ms
banner02.jpg
476 ms
4gamer.jpg
483 ms
banner05.jpg
504 ms
otomatelabel.jpg
508 ms
ichi.png
507 ms
st_logo.png
635 ms
rejet.png
644 ms
red.png
671 ms
otome_fes2.png
677 ms
spica.png
679 ms
if.png
786 ms
df.png
793 ms
ascii.png
804 ms
otomate_recruit.jpg
838 ms
recruit.jpg
845 ms
account.jpg
849 ms
ban_otoreco.jpg
1098 ms
new-arrival.jpg
950 ms
otomate_store.jpg
964 ms
shop.jpg
1172 ms
mobileportal.jpg
1014 ms
oto_mobile.jpg
1018 ms
sephirot.jpg
1267 ms
oto_ch.jpg
1285 ms
appli.gif
171 ms
game.gif
185 ms
news.gif
172 ms
topslider.php
1032 ms
hakuoki_sogo.jpg
1057 ms
dls_portal.jpg
1091 ms
hakuoki_visa.jpg
1174 ms
eposcard.jpg
1357 ms
footer.gif
1049 ms
dllp_thum.png
206 ms
dllp.jpg
696 ms
wof_r_thum.png
239 ms
wof_r.jpg
801 ms
bc_vita_thum.png
323 ms
bc_vita.jpg
834 ms
nil-admirari_thum.png
400 ms
nil-admirari.jpg
824 ms
period-cube_thum.png
494 ms
period-cube.jpg
1043 ms
kyoukai_thum.png
665 ms
kyoukai.jpg
1521 ms
7scarlet_thum.png
854 ms
7scarlet.jpg
1145 ms
verite_thum.png
992 ms
verite.jpg
1305 ms
collar_malice_thum.png
1012 ms
collar_malice.jpg
1502 ms
suran_thum.png
1170 ms
suran.jpg
1524 ms
shinkai_thum.png
1313 ms
shinkai.jpg
1492 ms
psyemo_thum.png
1462 ms
psyemo.jpg
1652 ms
beast_princess_thum.png
1620 ms
beast_princess.jpg
1657 ms
aa-nisus_thum.png
1670 ms
aa-nisus.jpg
1697 ms
norn9_act-tune_thum.png
1683 ms
norn9_act-tune.jpg
1933 ms
ff_thum.png
1778 ms
ff.jpg
1775 ms
bws_wus_thum.png
1768 ms
bws_wus.jpg
1724 ms
dlle_thum.png
1722 ms
dlle.jpg
1948 ms
tierblade_thum.png
1753 ms
tierblade.jpg
1713 ms
otomate.jp accessibility score
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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
otomate.jp 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
Missing source maps for large first-party JavaScript
otomate.jp SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otomate.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 Otomate.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.
otomate.jp
Open Graph description is not detected on the main page of Otomate. 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: