4.7 sec in total
558 ms
3.7 sec
432 ms
Welcome to captain.co.jp homepage info - get ready to check Captain best content right away, or after learning these important things about captain.co.jp
千葉県勝浦のバーベキューを楽しむコテージ。貸別荘タイプのコテージは全8棟、キッチンのあるコテージでは自炊も。テニスコート1面もあり、お子様とのバーベキュー旅行に。
Visit captain.co.jpWe analyzed Captain.co.jp page load time and found that the first response time was 558 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
captain.co.jp performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value7.7 s
3/100
25%
Value5.6 s
53/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value3.6 s
91/100
10%
558 ms
730 ms
177 ms
352 ms
491 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 98% of them (53 requests) were addressed to the original Captain.co.jp, 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Captain.co.jp.
Page size can be reduced by 44.6 kB (9%)
502.6 kB
458.0 kB
In fact, the total size of Captain.co.jp main page is 502.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 451.1 kB which makes up the majority of the site volume.
Potential reduce by 13.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. 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 13.1 kB or 70% of the original size.
Potential reduce by 6.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. Captain images are well optimized though.
Potential reduce by 24.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 24.2 kB or 79% of the original size.
Potential reduce by 1.0 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. Captain.co.jp needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 47% of the original size.
Number of requests can be reduced by 5 (10%)
52
47
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Captain. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
captain.co.jp
558 ms
captain.co.jp
730 ms
style.css
177 ms
script.js
352 ms
lightbox.css
491 ms
spica.js
519 ms
lightbox_plus.js
692 ms
Logo_40wht.gif
58 ms
bg.gif
178 ms
header-2.jpg
529 ms
menu_over_01.gif
166 ms
menu_02.gif
175 ms
menu_03.gif
175 ms
menu_04.gif
329 ms
menu_05.gif
348 ms
menu_06.gif
349 ms
menu_07.gif
353 ms
logo-image.jpg
982 ms
introduction.gif
521 ms
6gaikan100.jpg
697 ms
2gaikan100.jpg
526 ms
bbq100.jpg
530 ms
morning100.jpg
695 ms
danro100.jpg
701 ms
sauna100-02.jpg
702 ms
waterbath100.jpg
707 ms
topix2.gif
869 ms
hina23.jpg
871 ms
asaichi.jpg
874 ms
kastutan.jpg
875 ms
what'new.gif
882 ms
news.gif
1041 ms
kp00.jpg
1047 ms
happy240.jpg
1049 ms
sauna170.jpg
1050 ms
netplan.gif
1057 ms
menu.gif
1144 ms
aboutus.gif
1213 ms
IG35.jpg
1220 ms
w-board150.jpg
1224 ms
seasky150.jpg
1226 ms
loading.gif
178 ms
prev.gif
176 ms
next.gif
165 ms
expand.gif
174 ms
close.gif
175 ms
zzoop.gif
176 ms
menu_over_02.gif
327 ms
menu_over_03.gif
346 ms
menu_over_04.gif
346 ms
menu_over_05.gif
346 ms
menu_over_06.gif
347 ms
menu_over_07.gif
349 ms
overlay.png
490 ms
captain.co.jp accessibility score
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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
captain.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
captain.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
Image elements do not have [alt] attributes
![]()
JA
![]()
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Captain.co.jp 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 Captain.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
captain.co.jp
Open Graph description is not detected on the main page of Captain. 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: