Tools & Wizards About Us
captable.io screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

captable.io

Important update for LTSE Equity customers

Page Load Speed

2.7 sec in total

First Response

266 ms

Resources Loaded

2.1 sec

Page Rendered

365 ms

captable.io screenshot

About Website

Click here to check amazing Captable content for United States. Otherwise, check out these important facts you probably never knew about captable.io

Important update for LTSE Equity customers.

Visit captable.io

Key Findings

We analyzed Captable.io page load time and found that the first response time was 266 ms and then it took 2.5 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

captable.io performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.329

35/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

captable.io

266 ms

home.html

275 ms

css

24 ms

bootstrap.css

218 ms

captable.css

266 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 71% of them (12 requests) were addressed to the original Captable.io, 12% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (709 ms) belongs to the original domain Captable.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 247.0 kB (27%)

Content Size

910.9 kB

After Optimization

664.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Captable.io main page is 910.9 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 565.8 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 7.6 kB

  • Original 11.1 kB
  • After minification 10.1 kB
  • After compression 3.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 7.6 kB or 68% of the original size.

Image Optimization

-1%

Potential reduce by 6.5 kB

  • Original 565.8 kB
  • After minification 559.3 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. Captable images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 110.3 kB

  • Original 191.0 kB
  • After minification 167.5 kB
  • After compression 80.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 110.3 kB or 58% of the original size.

CSS Optimization

-86%

Potential reduce by 122.6 kB

  • Original 143.0 kB
  • After minification 115.4 kB
  • After compression 20.4 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. Captable.io needs all CSS files to be minified and compressed as it can save up to 122.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (20%)

Requests Now

15

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

captable.io

captable.io

266 ms

home.html

home.html

275 ms

css

css

24 ms

bootstrap.css

bootstrap.css

218 ms

captable.css

captable.css

266 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

360 ms

bootstrap.js

bootstrap.js

277 ms

mixpanel-2.2.min.js

mixpanel-2.2.min.js

50 ms

hero.jpg

hero.jpg

620 ms

1.jpg

1.jpg

709 ms

4.jpg

4.jpg

445 ms

3.jpg

3.jpg

628 ms

ssl_logo.png

ssl_logo.png

284 ms

analytics.js

analytics.js

79 ms

icon-angellist-white.png

icon-angellist-white.png

275 ms

39 ms

collect

collect

28 ms

Accessibility Review

captable.io accessibility score

91

Accessibility Issues

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

Buttons do not have an accessible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

Best Practices

captable.io 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

Page has valid source maps

SEO Factors

captable.io SEO score

90

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Captable.io 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 Captable.io main page’s claimed encoding is iso-8859-1. 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

captable.io

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