Tools & Wizards About Us
capitex.se screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

capitex.se

Vertical Software - Vitec

Page Load Speed

2.8 sec in total

First Response

706 ms

Resources Loaded

2 sec

Page Rendered

164 ms

capitex.se screenshot

About Website

Visit capitex.se now to see the best up-to-date Capitex content for Sweden and also check out these interesting facts you probably never knew about capitex.se

Vitec är ledande inom Vertical Market Software i Norden. Vi utvecklar och levererar standardprogram för olika nischer.

Visit capitex.se

Key Findings

We analyzed Capitex.se page load time and found that the first response time was 706 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

capitex.se performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value2,400 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.251

49/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

capitex.se

706 ms

screen.css

675 ms

flexslider.css

226 ms

modernizr-2.6.2.min.js

335 ms

jquery-1.9.1.min.js

6 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 62% of them (21 requests) were addressed to the original Capitex.se, 15% (5 requests) were made to Fonts.gstatic.com and 12% (4 requests) were made to Tr.prospecteye.com. The less responsive or slowest element that took the longest time to load (706 ms) belongs to the original domain Capitex.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 324.2 kB (66%)

Content Size

490.5 kB

After Optimization

166.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Capitex.se main page is 490.5 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. 30% of websites need less resources to load. Javascripts take 278.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 18.9 kB

  • Original 24.4 kB
  • After minification 19.7 kB
  • After compression 5.5 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 4.7 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 18.9 kB or 77% of the original size.

Image Optimization

-14%

Potential reduce by 12.4 kB

  • Original 88.9 kB
  • After minification 76.5 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. Obviously, Capitex needs image optimization as it can save up to 12.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 211.2 kB

  • Original 278.8 kB
  • After minification 193.8 kB
  • After compression 67.6 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 211.2 kB or 76% of the original size.

CSS Optimization

-83%

Potential reduce by 81.6 kB

  • Original 98.3 kB
  • After minification 96.9 kB
  • After compression 16.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. Capitex.se needs all CSS files to be minified and compressed as it can save up to 81.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (48%)

Requests Now

27

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

capitex.se

capitex.se

706 ms

screen.css

screen.css

675 ms

flexslider.css

flexslider.css

226 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

335 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

6 ms

jquery.equalHeights.js

jquery.equalHeights.js

126 ms

jquery.flexslider.js

jquery.flexslider.js

347 ms

jquery.colorbox.js

jquery.colorbox.js

442 ms

handlebars-1.0.rc.1.js

handlebars-1.0.rc.1.js

570 ms

bootstrap-scrollspy.js

bootstrap-scrollspy.js

235 ms

jquery.dropdown.js

jquery.dropdown.js

253 ms

main.js

main.js

354 ms

css

css

25 ms

bg-header.jpg

bg-header.jpg

118 ms

vitec.png

vitec.png

118 ms

bg-nav.png

bg-nav.png

120 ms

bg-content.png

bg-content.png

118 ms

icon-health.png

icon-health.png

117 ms

loader.gif

loader.gif

153 ms

vd.png

vd.png

231 ms

icon-pdf.png

icon-pdf.png

199 ms

bg-footer.png

bg-footer.png

301 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

410 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

16 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

21 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

22 ms

PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff

PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff

21 ms

xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff

xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff

22 ms

ga.js

ga.js

20 ms

track.js

track.js

222 ms

__utm.gif

__utm.gif

15 ms

tr.prospecteye.com

tr.prospecteye.com

233 ms

track_includes.js

track_includes.js

240 ms

formtag.js

formtag.js

231 ms

Accessibility Review

capitex.se accessibility score

78

Accessibility Issues

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Links do not have a discernible name

Best Practices

capitex.se best practices score

83

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

SEO Factors

capitex.se SEO score

69

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

High

Document doesn't have a valid hreflang

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    SV

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

capitex.se

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