Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

cabin.vc

Cabin VC® | An investment firm focused exclusively on blockchain tech and digital assets

Page Load Speed

987 ms in total

First Response

171 ms

Resources Loaded

759 ms

Page Rendered

57 ms

cabin.vc screenshot

About Website

Visit cabin.vc now to see the best up-to-date Cabin content and also check out these interesting facts you probably never knew about cabin.vc

Visit cabin.vc

Key Findings

We analyzed Cabin.vc page load time and found that the first response time was 171 ms and then it took 816 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

cabin.vc performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.259

47/100

15%

TTI (Time to Interactive)

Value4.9 s

77/100

10%

Network Requests Diagram

cabin.vc

171 ms

materialdesignicons.min.css

145 ms

core.css

155 ms

cpanel.css

149 ms

config.js

179 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that all of those requests were addressed to Cabin.vc and no external sources were called. The less responsive or slowest element that took the longest time to load (234 ms) belongs to the original domain Cabin.vc.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 kB (1%)

Content Size

188.1 kB

After Optimization

185.9 kB

In fact, the total size of Cabin.vc main page is 188.1 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. Javascripts take 170.2 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 967 B

  • Original 1.5 kB
  • After minification 1.0 kB
  • After compression 521 B

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 449 B, which is 30% 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 967 B or 65% of the original size.

JavaScript Optimization

-0%

Potential reduce by 495 B

  • Original 170.2 kB
  • After minification 170.1 kB
  • After compression 169.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 724 B

  • Original 16.4 kB
  • After minification 16.4 kB
  • After compression 15.7 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. Cabin.vc has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cabin. According to our analytics all requests are already optimized.

Accessibility Review

cabin.vc accessibility score

63

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

cabin.vc best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

cabin.vc SEO score

91

Search Engine Optimization Advices

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 uses 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 Cabin.vc 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 Cabin.vc 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

Open Graph description is not detected on the main page of Cabin. 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: