1.1 sec in total
126 ms
855 ms
144 ms
Welcome to captainhouse.com homepage info - get ready to check CAPTAIN HOUSE best content right away, or after learning these important things about captainhouse.com
CAPTAIN HOUSE inc. YeYe、kuh、trademark、√thummらが所属するレコード会社です。音楽プロダクション、音楽出版管理業務の他、プロダクト・レーベル「TONiKHA」の運営も行っています。
Visit captainhouse.comWe analyzed Captainhouse.com page load time and found that the first response time was 126 ms and then it took 999 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
captainhouse.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value6.9 s
6/100
25%
Value6.1 s
44/100
10%
Value1,040 ms
26/100
30%
Value0.026
100/100
15%
Value13.5 s
11/100
10%
126 ms
71 ms
35 ms
37 ms
44 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 82% of them (50 requests) were addressed to the original Captainhouse.com, 8% (5 requests) were made to Youtube.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (589 ms) belongs to the original domain Captainhouse.com.
Page size can be reduced by 97.1 kB (10%)
1.0 MB
910.6 kB
In fact, the total size of Captainhouse.com main page is 1.0 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 653.6 kB which makes up the majority of the site volume.
Potential reduce by 14.1 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.3 kB, which is 31% 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 14.1 kB or 82% of the original size.
Potential reduce by 2.4 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. CAPTAIN HOUSE images are well optimized though.
Potential reduce by 67.2 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 67.2 kB or 26% of the original size.
Potential reduce by 13.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. Captainhouse.com needs all CSS files to be minified and compressed as it can save up to 13.5 kB or 18% of the original size.
Number of requests can be reduced by 31 (55%)
56
25
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CAPTAIN HOUSE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
captainhouse.com
126 ms
jquery.js
71 ms
common.js
35 ms
smoothScroll.js
37 ms
base.css
44 ms
common.css
84 ms
bsn.Crossfader.js
54 ms
addthis_widget.js
11 ms
mt-run-periodic-tasks.cgi
589 ms
bg_header.gif
22 ms
logo.gif
22 ms
navi01.gif
25 ms
navi02.gif
28 ms
navi03.gif
28 ms
navi04.gif
21 ms
navi05.gif
40 ms
navi06.gif
40 ms
navi07.gif
41 ms
bg_main.png
45 ms
top_musikanatomia.jpg
192 ms
main_shadow.jpg
55 ms
arrow_r.gif
57 ms
ttl_news.gif
57 ms
arrow_news.png
60 ms
ttl_live.gif
66 ms
ttl_nocontents.gif
82 ms
bg_shadow.jpg
74 ms
img_live.jpg
73 ms
img_shop.jpg
98 ms
img_tonikha.jpg
110 ms
img_magazine.gif
89 ms
arrow_t.gif
91 ms
arrow_f.gif
109 ms
img_jasrak.gif
107 ms
navi01_on.gif
107 ms
navi02_on.gif
117 ms
navi03_on.gif
128 ms
navi04_on.gif
126 ms
navi05_on.gif
151 ms
navi06_on.gif
155 ms
navi07_on.gif
156 ms
kuh_72dpi-thumb-200xauto-37.jpg
67 ms
img_release01-thumb-200xauto-10.jpg
65 ms
img_release02-thumb-200xauto-11.jpg
66 ms
img_release03-thumb-200xauto-12.jpg
74 ms
img_release04-thumb-200xauto-13.jpg
68 ms
img_release05-thumb-200xauto-14.jpg
85 ms
kuh_201303_a-thumb-200xauto-36.jpg
101 ms
img_artist01-thumb-200xauto-4.jpg
84 ms
img_artist03-thumb-200xauto-2.jpg
123 ms
img_artist04-thumb-200xauto-1.jpg
96 ms
K0Mv_H0cgto
124 ms
www-player.css
7 ms
www-embed-player.js
29 ms
base.js
63 ms
ad_status.js
174 ms
jj2eNDzr7OxRmG3eEZdf1bHpefYrrxl4VJQY9raQMR0.js
146 ms
embed.js
57 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
57 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
58 ms
id
34 ms
captainhouse.com 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
captainhouse.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
captainhouse.com 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Captainhouse.com 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 Captainhouse.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.
captainhouse.com
Open Graph description is not detected on the main page of CAPTAIN HOUSE. 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: