7.3 sec in total
1.3 sec
5.6 sec
326 ms
Visit ilca.co.jp now to see the best up-to-date ILCA content for Japan and also check out these interesting facts you probably never knew about ilca.co.jp
映画・TV・アニメ・ゲームなどの映像制作会社、株式会社イルカ。
Visit ilca.co.jpWe analyzed Ilca.co.jp page load time and found that the first response time was 1.3 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ilca.co.jp performance score
name
value
score
weighting
Value3.7 s
28/100
10%
Value7.1 s
5/100
25%
Value9.3 s
12/100
10%
Value2,350 ms
5/100
30%
Value0.905
3/100
15%
Value8.8 s
35/100
10%
1343 ms
540 ms
411 ms
570 ms
419 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 37% of them (51 requests) were addressed to the original Ilca.co.jp, 23% (32 requests) were made to Pbs.twimg.com and 22% (30 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Ilca.co.jp.
Page size can be reduced by 1.0 MB (14%)
7.5 MB
6.5 MB
In fact, the total size of Ilca.co.jp main page is 7.5 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. 70% of websites need less resources to load. Images take 7.0 MB which makes up the majority of the site volume.
Potential reduce by 30.2 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 5.8 kB, which is 16% 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 30.2 kB or 82% of the original size.
Potential reduce by 628.7 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. ILCA images are well optimized though.
Potential reduce by 307.6 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 307.6 kB or 72% of the original size.
Potential reduce by 50.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. Ilca.co.jp needs all CSS files to be minified and compressed as it can save up to 50.6 kB or 83% of the original size.
Number of requests can be reduced by 55 (40%)
137
82
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ILCA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
ilca.co.jp
1343 ms
style.css
540 ms
import.css
411 ms
layout_r.css
570 ms
styles.css
419 ms
styles.css
427 ms
jquery.js
945 ms
jquery-migrate.min.js
572 ms
jquery.min.js
30 ms
plugins.js
1446 ms
main.js
429 ms
jquery.form.min.js
519 ms
scripts.js
560 ms
scripts.js
562 ms
wp-embed.min.js
600 ms
reset.css
435 ms
layout.css
488 ms
element.css
489 ms
wp-emoji-release.min.js
519 ms
img_transparent.png
166 ms
yam_line.png
350 ms
banner_ook.png
372 ms
santa_web_banner.png
313 ms
banner_ilcapapper05_n.png
649 ms
subMenu_interview1.png
609 ms
subMenu_recruitCareer1-310x100.png
526 ms
wgs_lineVer3_1.png
1025 ms
wgs_lineVer3_2.png
1154 ms
banner_OsrLine.png
877 ms
all.js
268 ms
top_logo.png
873 ms
widgets.js
83 ms
hedder_sNav_line.gif
860 ms
gNav.gif
861 ms
img_loading.gif
900 ms
img_arrow-right.png
968 ms
works_mbg-312x176.png
1141 ms
TTCO_detail-312x176.png
1448 ms
works_tmcn-312x176.png
1446 ms
ook_detail-312x176.png
1663 ms
DGG_detail-312x176.png
1349 ms
mor_detail-312x176.png
1320 ms
yam3_works_detail-312x176.png
1493 ms
DRL-312x176.png
1960 ms
linq-312x176.png
1665 ms
img_arrow-left.png
1617 ms
footer_b_up.gif
1588 ms
footer_nav_bg.gif
1662 ms
footer_copyright_bg.gif
1675 ms
68 ms
xd_arbiter.php
228 ms
xd_arbiter.php
562 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
128 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
152 ms
DRF_HP01ver5.png
2609 ms
bon_dvd3_3-960x410.png
2107 ms
yam_mainvisual.png
1825 ms
santa_line2.png
1951 ms
top_banner_SF.png
2044 ms
like.php
71 ms
like_box.php
224 ms
wy1X4hBW7e7.js
538 ms
LVx-xkvaJ0b.png
481 ms
syndication
85 ms
509945176425373696
267 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
47 ms
S3hqe5oSdDY.css
289 ms
qcAl38Qnod_.css
290 ms
9jqESJmDeZC.css
289 ms
yD8wnvAdP_C.css
306 ms
5aFaALjvOu-.css
450 ms
S7Te03cm5pT.css
302 ms
K0vBTMbW63q.css
317 ms
q68gy-v_YMF.js
475 ms
ehA1CqzHyzE.js
513 ms
0wM5s1Khldu.js
466 ms
1bNoFZUdlYZ.js
467 ms
njO1TPvGzoR.js
469 ms
1QuX41zDRrx.js
507 ms
Oagsvfb4VWi.js
538 ms
LTv6ZK-5zxz.js
673 ms
1FCa-btixu2.js
507 ms
DVtj8v6ogQI.js
583 ms
IjqSyiwKeaX.js
587 ms
n6VgtouijQL.js
585 ms
nu-qg3EqU-e.js
585 ms
1f631.png
28 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
32 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
147 ms
z2DELoF5_normal.png
172 ms
wt3UM2aI_normal.jpg
291 ms
5apucmzm_normal.png
295 ms
OaOBsfl6_normal.jpg
371 ms
FXQogu-h_normal.jpg
386 ms
7hte46On_normal.jpg
385 ms
Xfj-TkGp_normal.jpg
386 ms
WuOu9Yso_normal.jpg
414 ms
_sR-5ky2_normal.jpg
401 ms
04a5e950a3b5f18a02a1c92221f85fee_normal.jpeg
413 ms
gAQNHTqD_normal.jpg
433 ms
1c4cf693a8bf9b262f60783b3932b285_normal.jpeg
425 ms
CdckhLSUYAAN61m.jpg:small
395 ms
Cdb_r8HVIAEc_JZ.jpg:small
463 ms
CdbnUmGUkAETfj-.jpg:small
469 ms
Cc3xaNuUAAAQGcg.jpg:small
437 ms
Cc3d1uQUYAA1J8E.jpg:small
460 ms
CcTaW4YUAAA230h.jpg:small
634 ms
CcMMB9sUYAANjns.jpg:small
628 ms
CcHP0qkUMAMxSAv.jpg:small
628 ms
Cb5JH_EUkAATokO.jpg:small
632 ms
CcJLiELUEAEQLqi.jpg:small
628 ms
Cb-IrCdWwAAmYZ2.jpg:small
629 ms
CcUytagUYAEz6xM.jpg:small
633 ms
CcUytaoUMAEfpID.jpg:small
634 ms
CcUytaoUAAAYuQz.jpg:small
700 ms
CcQyWb9UYAA7yZs.jpg:small
701 ms
CcQyWhiUEAAl-kg.jpg:small
702 ms
CcQyWvaUMAARHFV.jpg:small
809 ms
CcIuoNcVIAENCIp.jpg:small
702 ms
CcIuoMhUcAQrjqv.jpg:small
730 ms
CcIuoLzUYAEOke7.jpg:small
723 ms
7391_985336278203557_8260349716243596436_n.jpg
366 ms
safe_image.php
374 ms
safe_image.php
627 ms
safe_image.php
671 ms
safe_image.php
620 ms
10411297_771292596274594_4171532243234429244_n.png
422 ms
12688337_1008074449263073_3274712908295642376_n.jpg
490 ms
wL6VQj7Ab77.png
151 ms
s7jcwEQH7Sx.png
151 ms
bNvHN6v1NeH.png
149 ms
b53Ajb4ihCP.gif
150 ms
QDwYpIaRyfG.png
149 ms
K00K-UgnsKu.png
148 ms
81 ms
jot.html
28 ms
I6-MnjEovm5.js
68 ms
pQrUxxo5oQp.js
136 ms
ilca.co.jp 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
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.
ilca.co.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
General
Impact
Issue
Detected JavaScript libraries
ilca.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ilca.co.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Ilca.co.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.
ilca.co.jp
Open Graph description is not detected on the main page of ILCA. 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: