Tools & Wizards About Us
captain.co.jp screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

captain.co.jp

コテージでバーベキュー●千葉勝浦　丘のログコテージ　キャプテンズテーブル

Page Load Speed

4.6 sec in total

First Response

714 ms

Resources Loaded

3.4 sec

Page Rendered

443 ms

captain.co.jp screenshot

About Website

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.jp

Key Findings

We analyzed Captain.co.jp page load time and found that the first response time was 714 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

captain.co.jp performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

captain.co.jp

714 ms

style.css

328 ms

script.js

339 ms

lightbox.css

341 ms

spica.js

350 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 98% of them (50 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.3 sec) belongs to the original domain Captain.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.6 kB (22%)

Content Size

520.8 kB

After Optimization

407.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Captain.co.jp main page is 520.8 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. 20% of websites need less resources to load. Images take 464.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 13.5 kB

  • Original 19.1 kB
  • After minification 18.8 kB
  • After compression 5.6 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.5 kB or 71% of the original size.

Image Optimization

-15%

Potential reduce by 70.5 kB

  • Original 464.5 kB
  • After minification 394.0 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, Captain needs image optimization as it can save up to 70.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-79%

Potential reduce by 24.2 kB

  • Original 30.6 kB
  • After minification 23.8 kB
  • After compression 6.4 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.

CSS Optimization

-81%

Potential reduce by 5.3 kB

  • Original 6.5 kB
  • After minification 3.6 kB
  • After compression 1.2 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 5.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (10%)

Requests Now

50

After Optimization

45

  • Images
  • JavaScript
  • CSS

The browser has sent 50 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.

Network Requests Diagram

captain.co.jp

captain.co.jp

714 ms

style.css

style.css

328 ms

script.js

script.js

339 ms

lightbox.css

lightbox.css

341 ms

spica.js

spica.js

350 ms

lightbox_plus.js

lightbox_plus.js

989 ms

Logo_40wht.gif

Logo_40wht.gif

58 ms

bg.gif

bg.gif

180 ms

header-2.jpg

header-2.jpg

541 ms

menu_over_01.gif

menu_over_01.gif

171 ms

menu_02.gif

menu_02.gif

172 ms

menu_03.gif

menu_03.gif

182 ms

menu_04.gif

menu_04.gif

165 ms

menu_05.gif

menu_05.gif

328 ms

menu_06.gif

menu_06.gif

339 ms

menu_07.gif

menu_07.gif

340 ms

logo-image.jpg

logo-image.jpg

1068 ms

introduction.gif

introduction.gif

536 ms

10living16a-100.jpg

10living16a-100.jpg

652 ms

6gaikan100.jpg

6gaikan100.jpg

676 ms

2gaikan100.jpg

2gaikan100.jpg

676 ms

bbq100.jpg

bbq100.jpg

715 ms

morning100.jpg

morning100.jpg

718 ms

sauna100.jpg

sauna100.jpg

815 ms

danro100.jpg

danro100.jpg

845 ms

coat100.jpg

coat100.jpg

845 ms

topix2.gif

topix2.gif

893 ms

asaichi.jpg

asaichi.jpg

898 ms

kastutan.jpg

kastutan.jpg

977 ms

b1katsuura01.jpg

b1katsuura01.jpg

1349 ms

what'new.gif

what'new.gif

1015 ms

news.gif

news.gif

1072 ms

netplan.gif

netplan.gif

1077 ms

menu.gif

menu.gif

1139 ms

aboutus.gif

aboutus.gif

1183 ms

w-board150.jpg

w-board150.jpg

1243 ms

zenkei-night150.jpg

zenkei-night150.jpg

1250 ms

seasky150.jpg

seasky150.jpg

1256 ms

loading.gif

loading.gif

181 ms

prev.gif

prev.gif

182 ms

next.gif

next.gif

170 ms

expand.gif

expand.gif

171 ms

close.gif

close.gif

180 ms

zzoop.gif

zzoop.gif

166 ms

menu_over_02.gif

menu_over_02.gif

327 ms

menu_over_03.gif

menu_over_03.gif

339 ms

menu_over_04.gif

menu_over_04.gif

340 ms

menu_over_05.gif

menu_over_05.gif

356 ms

menu_over_06.gif

menu_over_06.gif

357 ms

menu_over_07.gif

menu_over_07.gif

358 ms

overlay.png

overlay.png

489 ms

Accessibility Review

captain.co.jp accessibility score

71

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

captain.co.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

captain.co.jp SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: