Tools & Wizards About Us
captainfathands.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

captainfathands.com

HOME

Page Load Speed

2.4 sec in total

First Response

109 ms

Resources Loaded

1.8 sec

Page Rendered

459 ms

captainfathands.com screenshot

About Website

Welcome to captainfathands.com homepage info - get ready to check Captainfathands best content right away, or after learning these important things about captainfathands.com

Captain Fathands Home Page

Visit captainfathands.com

Key Findings

We analyzed Captainfathands.com page load time and found that the first response time was 109 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

captainfathands.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value14,180 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value38.6 s

0/100

10%

Network Requests Diagram

captainfathands.com

109 ms

captainfathands.com

153 ms

application-6ec7031d80aa850ceefe88074166f22e5f05afc9fbcc6ab0f91a580f4cf57944.css

65 ms

beckett-957c745067eb88f065e16509d581dcdcbb91ea79c398a087695756147e0c1432.css

77 ms

stylesheet.css

53 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 10% of them (6 requests) were addressed to the original Captainfathands.com, 27% (16 requests) were made to Embed-cdn.spotifycdn.com and 10% (6 requests) were made to Assets-app-production-pubnet.bndzgl.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source D10j3mvrs1suex.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (34%)

Content Size

5.3 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Captainfathands.com main page is 5.3 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. Only a small number of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 44.3 kB

  • Original 55.5 kB
  • After minification 54.7 kB
  • After compression 11.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 44.3 kB or 80% of the original size.

Image Optimization

-30%

Potential reduce by 1.1 MB

  • Original 3.8 MB
  • After minification 2.7 MB

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, Captainfathands needs image optimization as it can save up to 1.1 MB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-44%

Potential reduce by 620.9 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 798.8 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 620.9 kB or 44% of the original size.

CSS Optimization

-0%

Potential reduce by 42 B

  • Original 74.4 kB
  • After minification 74.4 kB
  • After compression 74.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. Captainfathands.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (56%)

Requests Now

50

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Captainfathands. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

captainfathands.com

captainfathands.com

109 ms

captainfathands.com

captainfathands.com

153 ms

application-6ec7031d80aa850ceefe88074166f22e5f05afc9fbcc6ab0f91a580f4cf57944.css

application-6ec7031d80aa850ceefe88074166f22e5f05afc9fbcc6ab0f91a580f4cf57944.css

65 ms

beckett-957c745067eb88f065e16509d581dcdcbb91ea79c398a087695756147e0c1432.css

beckett-957c745067eb88f065e16509d581dcdcbb91ea79c398a087695756147e0c1432.css

77 ms

stylesheet.css

stylesheet.css

53 ms

stylesheet.css

stylesheet.css

61 ms

stylesheet.css

stylesheet.css

80 ms

stylesheet.css

stylesheet.css

67 ms

css2

css2

38 ms

application-4774d9607584b20d9667fdf9d66b80b29d3f5b1f4fc5e411050942347add3b42.js

application-4774d9607584b20d9667fdf9d66b80b29d3f5b1f4fc5e411050942347add3b42.js

106 ms

usersite-6e6d8523bc9b473fa8057597f18b74066c86ef4d8b7808ce76231bec8a276d8a.js

usersite-6e6d8523bc9b473fa8057597f18b74066c86ef4d8b7808ce76231bec8a276d8a.js

180 ms

usersite-922a9f953ad08c50d003c2d24df3de07c7e960f32dd57618709651ff5fa30a0d.css

usersite-922a9f953ad08c50d003c2d24df3de07c7e960f32dd57618709651ff5fa30a0d.css

85 ms

js

js

69 ms

meta%3AeyJzcmNCdWNrZXQiOiJiemdsZmlsZXMifQ%3D%3D.png

meta%3AeyJzcmNCdWNrZXQiOiJiemdsZmlsZXMifQ%3D%3D.png

1396 ms

447 ms

593 ms

592 ms

448 ms

446 ms

590 ms

ZJYjgXehZME

ZJYjgXehZME

137 ms

3QkN5VvGFayOiiV3xH2JF1

3QkN5VvGFayOiiV3xH2JF1

499 ms

4tOCx75TC7YolGCBnLX6ry

4tOCx75TC7YolGCBnLX6ry

586 ms

5pXVStkgi4wcoEVGrQuVTl

5pXVStkgi4wcoEVGrQuVTl

811 ms

stats.js

stats.js

78 ms

23651248.html

23651248.html

88 ms

23651272.html

23651272.html

323 ms

23654865.html

23654865.html

424 ms

6167291.html

6167291.html

428 ms

usersite_print-54751968beb622ee3de912bc218d2b9ac3a8d135d26a0cf1beb003bfc0870409.css

usersite_print-54751968beb622ee3de912bc218d2b9ac3a8d135d26a0cf1beb003bfc0870409.css

29 ms

Fm3JsqMzGTg

Fm3JsqMzGTg

387 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

24 ms

base.js

base.js

48 ms

ad_status.js

ad_status.js

282 ms

mdECNSLjE0kOqmWWpouU2WaUq2E9oglGDw0jXzAA5F4.js

mdECNSLjE0kOqmWWpouU2WaUq2E9oglGDw0jXzAA5F4.js

229 ms

embed.js

embed.js

151 ms

widget-5-4e9069de0c32.js

widget-5-4e9069de0c32.js

178 ms

widget-8-af988f73d8db.js

widget-8-af988f73d8db.js

177 ms

widget-9-6c79c9dd8ce8.js

widget-9-6c79c9dd8ce8.js

529 ms

fd67e1fb69fabcc3.css

fd67e1fb69fabcc3.css

120 ms

f412ef630b28bdaa.css

f412ef630b28bdaa.css

138 ms

2dde3bebb2f7a1de.css

2dde3bebb2f7a1de.css

314 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

333 ms

webpack-62e7c6a3a6427d8e.js

webpack-62e7c6a3a6427d8e.js

317 ms

framework-160e3f4943d4ca83.js

framework-160e3f4943d4ca83.js

360 ms

main-db993876a962f8d0.js

main-db993876a962f8d0.js

365 ms

_app-9f21b9eaae4f4ebb.js

_app-9f21b9eaae4f4ebb.js

449 ms

fec483df-87a6891f9916661b.js

fec483df-87a6891f9916661b.js

448 ms

370d8c6a-ba7b9fa33b972102.js

370d8c6a-ba7b9fa33b972102.js

332 ms

9187-656ef74def42cd3c.js

9187-656ef74def42cd3c.js

877 ms

347-38f3b180564db59e.js

347-38f3b180564db59e.js

470 ms

3666-fbcb8c0bae39e183.js

3666-fbcb8c0bae39e183.js

447 ms

%5Bid%5D-b4e152d529cc932f.js

%5Bid%5D-b4e152d529cc932f.js

448 ms

_buildManifest.js

_buildManifest.js

472 ms

_ssgManifest.js

_ssgManifest.js

471 ms

id

id

193 ms

Create

Create

233 ms

Create

Create

770 ms

logo-200x120-3190df52.png

logo-200x120-3190df52.png

24 ms

Accessibility Review

captainfathands.com accessibility score

64

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

Best Practices

captainfathands.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

captainfathands.com SEO score

86

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

Image elements do not have [alt] attributes

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Captainfathands.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Captainfathands.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.

Social Sharing Optimization

captainfathands.com

Open Graph data is detected on the main page of Captainfathands. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: