Tools & Wizards About Us
capis.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

capis.com

CAPIS | Trading. Transparency. Trust.

Page Load Speed

5.4 sec in total

First Response

157 ms

Resources Loaded

5.2 sec

Page Rendered

82 ms

capis.com screenshot

About Website

Visit capis.com now to see the best up-to-date CAPIS content for United States and also check out these interesting facts you probably never knew about capis.com

Trade Execution and Commission Management for Institutions. Experience the Difference with CAPIS. Click Here to Learn More.

Visit capis.com

Key Findings

We analyzed Capis.com page load time and found that the first response time was 157 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

capis.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

capis.com

157 ms

capis.com

2238 ms

ifw1bgm.css

115 ms

fwc1mgg.css

246 ms

grid.min.css

41 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 60% of them (82 requests) were addressed to the original Capis.com, 13% (18 requests) were made to Use.typekit.net and 11% (15 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Capis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 263.9 kB (13%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Capis.com main page is 2.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 261.0 kB

  • Original 312.1 kB
  • After minification 303.1 kB
  • After compression 51.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 261.0 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 614 B

  • Original 1.2 MB
  • After minification 1.2 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. CAPIS images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.0 kB

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

CSS Optimization

-1%

Potential reduce by 1.2 kB

  • Original 215.9 kB
  • After minification 215.9 kB
  • After compression 214.6 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. Capis.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 83 (86%)

Requests Now

97

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

capis.com

capis.com

157 ms

capis.com

capis.com

2238 ms

ifw1bgm.css

ifw1bgm.css

115 ms

fwc1mgg.css

fwc1mgg.css

246 ms

grid.min.css

grid.min.css

41 ms

helper-parts.min.css

helper-parts.min.css

40 ms

main.min.css

main.min.css

46 ms

bundle.css

bundle.css

79 ms

ekiticons.css

ekiticons.css

75 ms

swiper.min.css

swiper.min.css

56 ms

all.css

all.css

62 ms

frontend.min.css

frontend.min.css

55 ms

general.min.css

general.min.css

53 ms

eael-51025.css

eael-51025.css

68 ms

elementor-icons.min.css

elementor-icons.min.css

71 ms

e-swiper.min.css

e-swiper.min.css

70 ms

post-50310.css

post-50310.css

84 ms

frontend.min.css

frontend.min.css

105 ms

global.css

global.css

91 ms

widget-heading.min.css

widget-heading.min.css

89 ms

widget-text-editor.min.css

widget-text-editor.min.css

97 ms

fadeInUp.min.css

fadeInUp.min.css

108 ms

widget-divider.min.css

widget-divider.min.css

110 ms

fontawesome.min.css

fontawesome.min.css

113 ms

brands.min.css

brands.min.css

108 ms

solid.min.css

solid.min.css

119 ms

regular.min.css

regular.min.css

130 ms

widget-image.min.css

widget-image.min.css

127 ms

widget-icon-list.min.css

widget-icon-list.min.css

121 ms

widget-social-icons.min.css

widget-social-icons.min.css

130 ms

apple-webkit.min.css

apple-webkit.min.css

130 ms

post-51025.css

post-51025.css

207 ms

widget-styles.css

widget-styles.css

213 ms

responsive.css

responsive.css

234 ms

css

css

53 ms

jquery.min.js

jquery.min.js

240 ms

jquery-migrate.min.js

jquery-migrate.min.js

239 ms

js

js

104 ms

email-decode.min.js

email-decode.min.js

100 ms

basic.min.css

basic.min.css

208 ms

theme-ie11.min.css

theme-ie11.min.css

208 ms

theme.min.css

theme.min.css

207 ms

core.min.js

core.min.js

422 ms

main.min.js

main.min.js

424 ms

bundle.js

bundle.js

424 ms

comment-reply.min.js

comment-reply.min.js

307 ms

frontend-script.js

frontend-script.js

407 ms

widget-scripts.js

widget-scripts.js

409 ms

general.min.js

general.min.js

397 ms

imagesloaded.min.js

imagesloaded.min.js

395 ms

dom-ready.min.js

dom-ready.min.js

390 ms

hooks.min.js

hooks.min.js

391 ms

i18n.min.js

i18n.min.js

383 ms

a11y.min.js

a11y.min.js

377 ms

jquery.json.min.js

jquery.json.min.js

375 ms

gravityforms.min.js

gravityforms.min.js

371 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

360 ms

utils.min.js

utils.min.js

362 ms

vendor-theme.min.js

vendor-theme.min.js

362 ms

p.css

p.css

26 ms

scripts-theme.min.js

scripts-theme.min.js

359 ms

webpack.runtime.min.js

webpack.runtime.min.js

357 ms

frontend-modules.min.js

frontend-modules.min.js

352 ms

frontend.min.js

frontend.min.js

350 ms

elementor.js

elementor.js

344 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

343 ms

frontend.min.js

frontend.min.js

342 ms

elements-handlers.min.js

elements-handlers.min.js

342 ms

animate-circle.min.js

animate-circle.min.js

341 ms

roundtrip.js

roundtrip.js

220 ms

gtm.js

gtm.js

107 ms

p.css

p.css

108 ms

elementor.js

elementor.js

242 ms

p.css

p.css

19 ms

spinner.svg

spinner.svg

131 ms

Group%20267.svg

Group%20267.svg

122 ms

logo-part2.svg

logo-part2.svg

125 ms

Icon3.svg

Icon3.svg

124 ms

x32_.svg

x32_.svg

126 ms

ASB_BIG.D-825ddf30.svg

ASB_BIG.D-825ddf30.svg

127 ms

CPS_MorningNote_Dark-Blue-min.jpg

CPS_MorningNote_Dark-Blue-min.jpg

129 ms

Chris-at-Nasdaq.png

Chris-at-Nasdaq.png

444 ms

Graphic-1024x1024.png

Graphic-1024x1024.png

340 ms

Mask-Group-16.png

Mask-Group-16.png

72 ms

Logo.svg

Logo.svg

68 ms

logo1.svg

logo1.svg

69 ms

d

d

277 ms

d

d

279 ms

d

d

281 ms

d

d

280 ms

d

d

283 ms

d

d

339 ms

elementskit.woff

elementskit.woff

338 ms

Termina-Bold.woff

Termina-Bold.woff

276 ms

d

d

336 ms

d

d

281 ms

d

d

280 ms

Termina-Demi.woff

Termina-Demi.woff

336 ms

d

d

336 ms

Termina-Medium.woff

Termina-Medium.woff

274 ms

d

d

334 ms

Termina-Regular.woff

Termina-Regular.woff

385 ms

d

d

338 ms

d

d

335 ms

d

d

336 ms

d

d

336 ms

d

d

337 ms

fa-brands-400.woff

fa-brands-400.woff

355 ms

fa-brands-400.woff

fa-brands-400.woff

187 ms

EWQ7TTIW6RDN5JXUGBUMVO

EWQ7TTIW6RDN5JXUGBUMVO

130 ms

fbevents.js

fbevents.js

74 ms

out

out

7 ms

3DM5XXRDGVBPBMEKNTSRC4

3DM5XXRDGVBPBMEKNTSRC4

60 ms

out

out

62 ms

out

out

62 ms

out

out

127 ms

out

out

127 ms

out

out

127 ms

out

out

127 ms

out

out

127 ms

out

out

129 ms

out

out

130 ms

out

out

128 ms

out

out

128 ms

trigger

trigger

118 ms

tap.php

tap.php

109 ms

Pug

Pug

99 ms

pixel

pixel

19 ms

xuid

xuid

7 ms

sd

sd

6 ms

sync

sync

17 ms

bounce

bounce

15 ms

in

in

3 ms

rum

rum

23 ms

generic

generic

14 ms

generic

generic

4 ms

receive

receive

1621 ms

Accessibility Review

capis.com accessibility score

81

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

Links do not have a discernible name

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

capis.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

capis.com SEO score

89

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

    EN

  • Encoding

    UTF-8

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

capis.com

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