18.8 sec in total
558 ms
17.2 sec
1 sec
Click here to check amazing Project Index content for Japan. Otherwise, check out these important facts you probably never knew about project-index.net
劇場版「とある魔術の禁書目録<インデックス>」、2013年2月23日公開! 科学と魔術、そして、歌と奇蹟が交差するとき、エンデュミオンを舞台に物語が始まる――。
Visit project-index.netWe analyzed Project-index.net page load time and found that the first response time was 558 ms and then it took 18.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
project-index.net performance score
558 ms
868 ms
330 ms
331 ms
346 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 81% of them (72 requests) were addressed to the original Project-index.net, 3% (3 requests) were made to Spdmg.i-mobile.co.jp and 2% (2 requests) were made to Spcnv.i-mobile.co.jp. The less responsive or slowest element that took the longest time to load (11.7 sec) belongs to the original domain Project-index.net.
Page size can be reduced by 181.1 kB (11%)
1.6 MB
1.4 MB
In fact, the total size of Project-index.net main page is 1.6 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. 25% of websites need less resources to load. Images take 1.4 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. 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 17.7 kB or 75% of the original size.
Potential reduce by 26.9 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. Project Index images are well optimized though.
Potential reduce by 9.9 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 9.9 kB or 14% of the original size.
Potential reduce by 126.5 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. Project-index.net needs all CSS files to be minified and compressed as it can save up to 126.5 kB or 90% of the original size.
Number of requests can be reduced by 46 (55%)
84
38
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Project Index. 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 26 to 1 for CSS and as a result speed up the page load time.
project-index.net
558 ms
www.project-index.net
868 ms
jquery.jscrollpane.css
330 ms
colorbox.css
331 ms
set.css
346 ms
dez_pt.css
346 ms
unit.css
354 ms
fss.css
654 ms
common.js
854 ms
user.js
694 ms
jquery-1.8.2.min.js
1641 ms
jquery.jscrollpane.min.js
1104 ms
jquery.mousewheel.js
721 ms
jquery.backstretch.min.js
987 ms
jquery.colorbox-min.js
1216 ms
conversion.js
18 ms
adv.js
210 ms
common.css
704 ms
font.css
1044 ms
float_fix.css
982 ms
user.css
1073 ms
style_parts.css
1085 ms
base_area.css
1220 ms
sub_area.css
1517 ms
2c_l.css
1392 ms
usa_004.css
1405 ms
bnu_004_t.css
1452 ms
usa_006.css
1561 ms
nwu_001_t.css
1814 ms
usa_001.css
1740 ms
g_navi_v.css
2217 ms
usa_007.css
1797 ms
bnu_001_t.css
1886 ms
usa_003.css
1938 ms
style_parts.css
1879 ms
top_catch.png
802 ms
pv_bt.png
664 ms
00000009.gif
492 ms
key_v_full.png
8253 ms
news_bg.png
394 ms
t_news_ti.png
521 ms
t_more_bt.png
715 ms
new_ic01.gif
852 ms
ico_info.gif
849 ms
ico_event.gif
1008 ms
side_bg.png
2204 ms
gnavi_bg.png
1447 ms
t_logo.png
2070 ms
c_logo.png
1927 ms
gnavi_01c.png
1352 ms
gnavi_02c.png
2016 ms
gnavi_03c.png
2090 ms
gnavi_04c.png
2451 ms
gnavi_05c.png
2542 ms
gnavi_14c.png
2588 ms
gnavi_06c.png
2837 ms
gnavi_07c.png
2927 ms
gnavi_17c.png
2944 ms
gnavi_08c.png
3059 ms
gnavi_09c.png
3307 ms
gnavi_10c.png
3325 ms
gnavi_11c.png
3428 ms
gnavi_15c.png
3476 ms
gnavi_16c.png
3591 ms
gnavi_13c.png
3965 ms
00000010.jpg
4014 ms
00000001.gif
3933 ms
wb_logo.png
3999 ms
widgets.js
57 ms
ga.js
49 ms
108 ms
dg_gateway.js
207 ms
adv_inner.js
65 ms
__utm.gif
20 ms
37 ms
bl_track.js
368 ms
60 ms
adv.aspx
508 ms
top_bg.jpg
11708 ms
overlay.png
3911 ms
border.png
3933 ms
15 ms
controls.png
3972 ms
bl_track.cgi
357 ms
dgcore.js
6 ms
adSiteVisit.js
7 ms
tr_adv.ashx
172 ms
fsm.css
185 ms
fsl.css
371 ms
project-index.net SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Project-index.net 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 Project-index.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.
project-index.net
Open Graph description is not detected on the main page of Project Index. 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: