10 sec in total
710 ms
8.4 sec
906 ms
Welcome to pre.aliceorder.com homepage info - get ready to check Pre Aliceorder best content for Japan right away, or after learning these important things about pre.aliceorder.com
アリスオーダー 運営サイト
Visit pre.aliceorder.comWe analyzed Pre.aliceorder.com page load time and found that the first response time was 710 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pre.aliceorder.com performance score
710 ms
132 ms
458 ms
129 ms
646 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pre.aliceorder.com, 33% (35 requests) were made to Pre.cache.aliceorder.com and 21% (22 requests) were made to Jp.square-enix.com. The less responsive or slowest element that took the longest time to load (6.9 sec) relates to the external source Pre.cache.aliceorder.com.
Page size can be reduced by 865.2 kB (5%)
17.7 MB
16.8 MB
In fact, the total size of Pre.aliceorder.com main page is 17.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 16.7 MB which makes up the majority of the site volume.
Potential reduce by 26.5 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 26.5 kB or 76% of the original size.
Potential reduce by 182.8 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. Pre Aliceorder images are well optimized though.
Potential reduce by 482.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 482.4 kB or 66% of the original size.
Potential reduce by 173.6 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. Pre.aliceorder.com needs all CSS files to be minified and compressed as it can save up to 173.6 kB or 87% of the original size.
Number of requests can be reduced by 29 (28%)
102
73
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pre Aliceorder. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
pre.aliceorder.com
710 ms
reset.css
132 ms
template_rsp.css
458 ms
gcse.js
129 ms
jquery-1.10.2.min.js
646 ms
html5.js
477 ms
sqexHeader-black_rsp.js
449 ms
sp_aliceorderpre.js
528 ms
application-66c37ddd37a47bd076a182dace545fb0.css
443 ms
application-ade9b4ea90541a00c365c599b8a05bd4.js
2700 ms
oct.js
163 ms
html5media.min.js
135 ms
cse.js
60 ms
cse.js
81 ms
jsapi
124 ms
bg_gold_lt-e3a044ccd2b9219779392e821ab1521f.png
134 ms
bg_gold_rt-3b25d5cc2bde737733ead7a9c4f1f765.png
192 ms
bg_gold_lb-8b5e44e89404339787043380c73ac96d.png
130 ms
bg_gold_rb-143c9cc6b07284ef3ce18d9d07572371.png
203 ms
achieve01-d395c093549b2f422904a64f6590322f.png
168 ms
num1-ec10ae0bc1a5ffe37af1537392039b1e.png
207 ms
num3-479c480428360dc65466b3438bff916d.png
202 ms
num8-2220718880cee8aaa3492229e9b7bb70.png
254 ms
num2-1cd5b8d1646825d5a06e1c4c24583695.png
294 ms
num7-88af9129dae8678319600673668ed981.png
299 ms
prize_0100000-06aa99ba55b1a3db74d35a9755252d73.png
531 ms
achieve02_top-21f145149de241b0b66d0d3cca160c0d.png
312 ms
twitter_icon-63a3be6d72b1bc86f15707e4080e45c6.png
345 ms
achieve02_bottom-454cf5ddf1613686c8a7aabcf1dc88c2.png
482 ms
follow_table_c-5143e10ed43352336a55bf6e3a5ddaa4.png
497 ms
prize_0100000-19c82a4e72b5263cff1c6249dbd767c4.png
510 ms
follow_table_c-4f0de8effe11691e3f6d237010c8e73b.png
463 ms
banner_present-050d5b416dc6a75de86a2135d427be79.png
640 ms
banner_present-d100c972e3226ce82bcc96ceb1c0c23a.png
678 ms
loading-279c503df6d767389ba470f623139011.gif
598 ms
banner_campaign-9b0f587a2beff18cfb24e4fc86a8d51b.png
676 ms
banner01-6f2defe4d3f206d636ce2453f7a8367d.png
632 ms
banner02-da2955ba587a0f7fedc6d0cb937f58df.png
740 ms
logo-black.gif
73 ms
logo_ipn_b.gif
375 ms
gtm.js
40 ms
bg_black_alpha-f00d7010e32a714fb782077396393980.png
811 ms
bg_line_bottom-15fc2b868f8b9d6a2bfd6d7c9b6efea2.png
751 ms
bg_line-629a954e78e64d3842d884dfe729b294.png
781 ms
logocatch-d7f5c8e8ff9ffa8fc57ecf858311c23b.png
814 ms
h2_title-31204263f047fe80772e5c251f6d5dd8.png
840 ms
h3_title-14e5c6e711b3be2e37ad22a9a8fff2c7.png
850 ms
achieve-459046e1ec22df5a616fffca7f32bf9f.png
952 ms
widgets.js
77 ms
attention-864dbee529095e31c0b14dd867c510c9.png
891 ms
btn_twitter-4972281f215654bd0b7be98cb67cf96c.png
897 ms
background-300dd3f7ed934a6e22bcf4b3f1c035bf.png
6919 ms
default+ja.css
32 ms
minimalist.css
57 ms
default+ja.I.js
90 ms
minimalist.css
30 ms
adsct
228 ms
adsct
140 ms
gcsearch_css_black.js
404 ms
gcsearch.js
473 ms
share
452 ms
button.71000885400e222c3c0eec823f8f93f0.js
230 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
264 ms
sp_iphone_k.gif
432 ms
sp_android_k.gif
620 ms
share_k.gif
148 ms
sp_share_fb_k.gif
629 ms
sp_share_tw_k.gif
782 ms
sp_share_mx_k2.gif
834 ms
sp_share_gp.png
895 ms
share_line.png
1007 ms
syndication
406 ms
656087118381355009
522 ms
656087118381355009
685 ms
follow_button.fd774b599f565016d763dd860cb31c79.ja.html
106 ms
gcsearch_black.css
676 ms
jquery-1.7.2.min.js
1293 ms
async-ads.js
423 ms
small-logo.png
253 ms
nav_logo114.png
204 ms
gcse.gif
903 ms
gcse_icon_k.png
384 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
100 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
176 ms
P9JlnFqT_normal.png
768 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
72 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
70 ms
CfhNZIZUMAA9k8G.jpg
1116 ms
CfhDBHZUAAAvMNn.jpg
1119 ms
CfNUFh3UIAAEprT.jpg
1116 ms
CfNT9iLVAAEE_d4.jpg
1117 ms
CfMDm2KUAAAfEHP.jpg
1115 ms
CfMDfOBUYAAuR8o.jpg
1118 ms
CfMBeTnUkAAvZId.jpg
1119 ms
Ce9qjMFUsAEquNd.jpg
1122 ms
btn_logo_22.png
460 ms
CfhNZIZUMAA9k8G.jpg:large
373 ms
CfhDBHZUAAAvMNn.jpg:large
373 ms
CfNUFh3UIAAEprT.jpg:large
828 ms
CfNT9iLVAAEE_d4.jpg:large
373 ms
CfMDm2KUAAAfEHP.jpg:large
372 ms
CfMDfOBUYAAuR8o.jpg:large
824 ms
CfMBeTnUkAAvZId.jpg:large
824 ms
Ce9qjMFUsAEquNd.jpg:large
826 ms
jot.html
86 ms
pre.aliceorder.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pre.aliceorder.com 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 Pre.aliceorder.com 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.
pre.aliceorder.com
Open Graph data is detected on the main page of Pre Aliceorder. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: