6 sec in total
1.5 sec
4.3 sec
152 ms
Welcome to anikasi.jp homepage info - get ready to check Anikasi best content for Japan right away, or after learning these important things about anikasi.jp
アニカシでは、アニソンや声優が歌っている歌の歌詞情報を掲載しています。アニメの名前や曲名で探すコトができます。
Visit anikasi.jpWe analyzed Anikasi.jp page load time and found that the first response time was 1.5 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
anikasi.jp performance score
1528 ms
682 ms
34 ms
342 ms
354 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 59% of them (48 requests) were addressed to the original Anikasi.jp, 9% (7 requests) were made to Pagead2.googlesyndication.com and 9% (7 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Anikasi.jp.
Page size can be reduced by 213.1 kB (6%)
3.7 MB
3.5 MB
In fact, the total size of Anikasi.jp main page is 3.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. 65% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 24.6 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 24.6 kB or 73% of the original size.
Potential reduce by 42.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. Anikasi images are well optimized though.
Potential reduce by 132.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 132.4 kB or 35% of the original size.
Potential reduce by 13.9 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. Anikasi.jp needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 67% of the original size.
Number of requests can be reduced by 28 (35%)
81
53
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Anikasi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
anikasi.jp
1528 ms
style.css
682 ms
jquery.min.js
34 ms
styles.css
342 ms
pagenavi-css.css
354 ms
jquery.js
1088 ms
jquery-migrate.min.js
547 ms
element.js
45 ms
adsbygoogle.js
6 ms
wp-emoji-release.min.js
366 ms
analytics.js
11 ms
1f3d8b007ca388958eddbd660e5503a4.jpg
393 ms
7f1a2d36c138f34071eadbb6540cd41e.jpg
563 ms
24fe3451ff3ccbc7db31243d342aa106.jpg
392 ms
22aab8ef05faef97ee3f8636957f4268.jpg
1003 ms
1d16e4c20356586ae7df7b6718f1c07d.jpg
711 ms
0222ba5ccc255b49118e9b1c40609921.jpg
730 ms
a9033de42b87ba641b83cb859e90996c.jpg
749 ms
710fc45e9f520330125eb4744672c590.jpg
753 ms
385a61bcaee0f75bf1f1c022d863fac9.jpg
708 ms
6440bd84f37cf37e43c5d505677ed7dc.jpg
879 ms
71031a49ec37b30292ad27657c60546c.jpg
1066 ms
4deaa1c88ce3b28c9e6b243c53bc8d6e.jpg
928 ms
1007f7d8860b60997313c6b593fab6e8.jpg
950 ms
d975b9361e41d816e421910e30e2cf19.jpg
936 ms
7f78493c1f34e0c5776da5a694382a62.jpg
1051 ms
65e06e348cf67fb75a71b313c1dbec6c.jpg
1292 ms
fcdeb8e9e6838937f38e7333e121ebe7.jpg
1120 ms
718f7cdc481bfdff1124db0edb4e7202.jpg
1154 ms
a3179e15390bd53ab112070713d7a9a9.jpg
1355 ms
a0364d0454c594e3b9a7add0bc42d3a6.jpg
1224 ms
dbf24f2ca7fd29e3398aef2d94c1f60a.jpg
1235 ms
e0c5fb48c372f50c13d1dd82850dd1bb.jpg
1320 ms
2b1c8464a0ea873d0a94b17cadc8b45e.jpg
1337 ms
898dd5fbe0ef9b8dbb6d54d123ad67f0.jpg
1402 ms
3f6b7a2460218eccbe236dc29ae1987c.jpg
1574 ms
cee17a13959fd8246b1d12c33e7e47ce.jpg
1475 ms
970a5fa0a9bdcdbdfc601ab2f7c1cff4.jpg
1517 ms
e17ea2265cf0026f9fc4174702de6732.jpg
1520 ms
73690676f381fb17e8d84feb51414e4c.jpg
1716 ms
879515cddac9f73df6af9afc01ace341.jpg
1593 ms
eb6d651817b51758fe0c6ab158c078dc.jpg
1669 ms
b05ef25eb368881c4c460e3912e4f8f2.jpg
1703 ms
6cb98f91d5f1cf3459fba72f4d13a3a5.jpg
1701 ms
Dimension-W.jpg
1754 ms
1aee3ef560720c216d1b03a9ee8f38e1.jpg
1765 ms
translateelement.css
64 ms
main.js
87 ms
82494ff18b63db8f7dbf294fa5c28485.jpg
1849 ms
linkid.js
8 ms
collect
2 ms
collect
68 ms
ca-pub-7960670313638823.js
118 ms
zrt_lookup.html
149 ms
show_ads_impl.js
108 ms
element_main.js
136 ms
ads
239 ms
osd.js
24 ms
translate_24dp.png
28 ms
l
52 ms
googlelogo_color_42x16dp.png
24 ms
ads
181 ms
googlelogo_color_68x28dp.png
2 ms
cleardot.gif
38 ms
te_ctrl3.gif
14 ms
loading.gif
24 ms
te_bk.gif
11 ms
e69e62d76d96c7cd28e23737c88b1def.jpg
1498 ms
f931ab166880f96b3b83b414e27aa250.jpg
1499 ms
7448670012403649797
73 ms
abg.js
29 ms
m_js_controller.js
49 ms
googlelogo_color_112x36dp.png
20 ms
1920686446550332889
51 ms
s
30 ms
x_button_blue2.png
31 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
4 ms
7e89ecd3ac82195979600e3684bb1697.jpg
1512 ms
jasrac.jpg
1220 ms
twitter-logo.png
1230 ms
activeview
13 ms
activeview
17 ms
anikasi.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Anikasi.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 Anikasi.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.
anikasi.jp
Open Graph description is not detected on the main page of Anikasi. 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: