Tools & Wizards About Us
capitalia.lt screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

capitalia.lt

Verslo finansavimas | CAPITALIA

Page Load Speed

3.8 sec in total

First Response

449 ms

Resources Loaded

3.1 sec

Page Rendered

247 ms

capitalia.lt screenshot

About Website

Visit capitalia.lt now to see the best up-to-date CAPITALIA content for Lithuania and also check out these interesting facts you probably never knew about capitalia.lt

Capitalia yra pirmaujanti įmonė smulkaus ir vidutinio verslo finansavimo bei konsultavimo sektoriuje Baltijos šalyse.

Visit capitalia.lt

Key Findings

We analyzed Capitalia.lt page load time and found that the first response time was 449 ms and then it took 3.3 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

capitalia.lt performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

capitalia.lt

449 ms

lt

542 ms

jquery.min.js

28 ms

main.minified.css

322 ms

script.js

18 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Capitalia.lt, 38% (15 requests) were made to Capitalia.com and 31% (12 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Capitalia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.9 kB (7%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Capitalia.lt main page is 1.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. 20% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 29.1 kB

  • Original 39.1 kB
  • After minification 31.7 kB
  • After compression 10.0 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. This page needs HTML code to be minified as it can gain 7.4 kB, which is 19% 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 29.1 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 33.4 kB

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

JavaScript Optimization

-13%

Potential reduce by 23.4 kB

  • Original 179.5 kB
  • After minification 179.5 kB
  • After compression 156.1 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 23.4 kB or 13% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 40.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.

Requests Breakdown

Number of requests can be reduced by 24 (67%)

Requests Now

36

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CAPITALIA. 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 as a result speed up the page load time.

Network Requests Diagram

capitalia.lt

capitalia.lt

449 ms

lt

lt

542 ms

jquery.min.js

jquery.min.js

28 ms

main.minified.css

main.minified.css

322 ms

script.js

script.js

18 ms

gtm.js

gtm.js

121 ms

capitalia-logo.png

capitalia-logo.png

335 ms

capitalia-graphic.png

capitalia-graphic.png

336 ms

menu.png

menu.png

336 ms

promo2.jpg

promo2.jpg

1748 ms

capitalia-graphic-medium.png

capitalia-graphic-medium.png

460 ms

tree.png

tree.png

1271 ms

lv.png

lv.png

127 ms

lt.png

lt.png

133 ms

ee.png

ee.png

128 ms

default

default

239 ms

jquery.lazy.min.js

jquery.lazy.min.js

22 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

633 ms

jquery.lazy.plugins.min.js

jquery.lazy.plugins.min.js

15 ms

bootstrap.min.js

bootstrap.min.js

17 ms

capitalia.minified.js

capitalia.minified.js

149 ms

cookies.js

cookies.js

109 ms

typed.min.js

typed.min.js

414 ms

jquery.cookie.min.js

jquery.cookie.min.js

14 ms

jquery.mask.min.js

jquery.mask.min.js

35 ms

subscribe.js

subscribe.js

132 ms

insight.min.js

insight.min.js

35 ms

insight_tag_errors.gif

insight_tag_errors.gif

98 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

197 ms

twk-event-polyfill.js

twk-event-polyfill.js

178 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

63 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

71 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

68 ms

twk-main.js

twk-main.js

79 ms

twk-vendor.js

twk-vendor.js

76 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

88 ms

twk-chunk-common.js

twk-chunk-common.js

236 ms

twk-runtime.js

twk-runtime.js

98 ms

twk-app.js

twk-app.js

139 ms

Accessibility Review

capitalia.lt accessibility score

78

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

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

capitalia.lt best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

capitalia.lt SEO score

99

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    LT

  • Encoding

    UTF-8

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

capitalia.lt

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