7.3 sec in total
514 ms
6.4 sec
313 ms
Visit cleo-inc.jp now to see the best up-to-date Cleo Inc content for Japan and also check out these interesting facts you probably never knew about cleo-inc.jp
映像関連ご依頼(映画/舞台/ドラマ/CF/企業VP制作の監督・俳優)は東京都目黒区の芸能プロダクション~株式会社CLEO(クレオ)までお気軽にお問い合わせください。俳優・映像制作等のご依頼はプロダクションサポートCLEOへ
Visit cleo-inc.jpWe analyzed Cleo-inc.jp page load time and found that the first response time was 514 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
cleo-inc.jp performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value12.7 s
0/100
25%
Value16.1 s
0/100
10%
Value2,170 ms
6/100
30%
Value0.022
100/100
15%
Value31.6 s
0/100
10%
514 ms
901 ms
338 ms
340 ms
341 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 39% of them (43 requests) were addressed to the original Cleo-inc.jp, 21% (23 requests) were made to Static.xx.fbcdn.net and 17% (18 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Cleo-inc.jp.
Page size can be reduced by 1.3 MB (28%)
4.8 MB
3.5 MB
In fact, the total size of Cleo-inc.jp main page is 4.8 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 4.1 MB which makes up the majority of the site volume.
Potential reduce by 29.9 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 29.9 kB or 68% of the original size.
Potential reduce by 841.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. Obviously, Cleo Inc needs image optimization as it can save up to 841.2 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 244.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 244.6 kB or 63% of the original size.
Potential reduce by 217.3 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. Cleo-inc.jp needs all CSS files to be minified and compressed as it can save up to 217.3 kB or 83% of the original size.
Number of requests can be reduced by 44 (42%)
105
61
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cleo Inc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
cleo-inc.jp
514 ms
www.cleo-inc.jp
901 ms
base.css
338 ms
top.css
340 ms
jquery.lightbox-0.5.css
341 ms
jquery-1.9.1.min.js
516 ms
rollover.js
390 ms
pagetop.js
389 ms
jquery.lightbox-0.5.js
674 ms
jsapi
52 ms
access.js
1212 ms
analytics.js
209 ms
WC1m9Ntf9fM
285 ms
tld6zricXPs
291 ms
bg.jpg
2069 ms
logo01.png
402 ms
btn_contact01.png
401 ms
gnav01_off.png
405 ms
gnav02_off.png
525 ms
gnav03_off.png
534 ms
gnav04_off.png
770 ms
gnav05_off.png
743 ms
gnav06_off.png
769 ms
gnav07_off.png
807 ms
visual_bg.jpg
1887 ms
visual_photo.jpg
1418 ms
semi-transparent_white.png
1294 ms
title_infomation.png
1297 ms
1457580550-396894_1.png
3138 ms
1435817472-836221_1.jpg
2467 ms
1436082734-055839_1.jpg
3301 ms
1436083418-759632_1.jpg
3749 ms
1436084240-694133_1.jpg
3383 ms
1436084297-613802_1.jpg
3813 ms
pageup.jpg
2857 ms
logo02.png
3196 ms
ftel01.png
3526 ms
ftel02.png
3586 ms
btn_contact02.jpg
3639 ms
sdk.js
26 ms
collect
59 ms
footer_bg.png
3559 ms
sitemap_bg.png
3702 ms
ga.js
32 ms
__utm.gif
20 ms
www-embed-player-vflfNyN_r.css
53 ms
www-embed-player.js
92 ms
base.js
129 ms
333 ms
xd_arbiter.php
28 ms
xd_arbiter.php
112 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
23 ms
ad_status.js
97 ms
81 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
86 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
86 ms
default+en.css
6 ms
default+en.I.js
22 ms
gnav01_on.png
3295 ms
gnav02_on.png
3455 ms
gnav03_on.png
3480 ms
gnav04_on.png
3520 ms
gnav05_on.png
3571 ms
gnav06_on.png
3644 ms
gnav07_on.png
3632 ms
page.php
289 ms
m83iJTM8ZQF.css
55 ms
vjfv3j-EdeX.css
59 ms
d6HEMKb7UAz.css
64 ms
OmIkD0koXXo.css
69 ms
gevUuEH7cch.css
61 ms
1kPfZUdGrka.js
64 ms
AeiIQ53iqZ6.js
92 ms
Qd7TTBR3F_S.js
68 ms
1dEEvSwLtg5.js
68 ms
jxc6Iy0B2Dy.js
111 ms
TzWCmQ2GDUt.js
110 ms
b1o_4KKMvfn.js
124 ms
1148843_162526153937387_133551688_n.jpg
168 ms
safe_image.php
178 ms
jWwyUJH0aOO.js
23 ms
safe_image.php
135 ms
561283_162527647270571_637973052_n.jpg
31 ms
12112133_114919485531478_9019877760586804095_n.jpg
40 ms
10439443_1399797373684281_7670447145137944629_n.jpg
29 ms
10670007_1512813085634009_8297440762097109669_n.jpg
101 ms
1451438_810523419038499_2410848488137737025_n.jpg
27 ms
1474482_224773334360128_1817131284_n.jpg
40 ms
12316410_1490245014615511_7462836541907153599_n.jpg
140 ms
12717295_1108764895824343_5719668836100016244_n.jpg
39 ms
11218880_489979464494278_8679737743671193285_n.jpg
55 ms
12311137_644672815635493_665429400290006099_n.jpg
141 ms
10649993_789947164408166_8912537487057002522_n.jpg
93 ms
1935331_459692087554124_5762712427618109407_n.jpg
110 ms
1797534_459692174220782_6143412229758162200_n.jpg
87 ms
10577174_459692260887440_2031058739951469313_n.jpg
102 ms
12806092_457569791099687_6747186964960685226_n.jpg
108 ms
12798900_457570001099666_2241908942327494613_n.jpg
435 ms
12803293_457546624435337_7420778098613253050_n.jpg
218 ms
wL6VQj7Ab77.png
16 ms
s7jcwEQH7Sx.png
22 ms
GtIpNnEyqq_.png
23 ms
bNvHN6v1NeH.png
15 ms
t-wz8gw1xG1.png
21 ms
6GqoI2ZyIrf.png
34 ms
R9GKCzjAnbk.js
7 ms
AWWjhOengNF.js
6 ms
YnSasnyq68i.js
4 ms
kQf_jlUv-kX.js
7 ms
cleo-inc.jp accessibility score
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
cleo-inc.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cleo-inc.jp SEO score
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cleo-inc.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 Cleo-inc.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.
cleo-inc.jp
Open Graph description is not detected on the main page of Cleo Inc. 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: