Tools & Wizards About Us
dootix.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

dootix.com

Dootix | Gold partner of Odoo in Switzerland and specialist in custom development

Page Load Speed

3.2 sec in total

First Response

226 ms

Resources Loaded

2.6 sec

Page Rendered

291 ms

dootix.com screenshot

About Website

Click here to check amazing Dootix content. Otherwise, check out these important facts you probably never knew about dootix.com

Gold partner of Odoo in Switzerland and specialist in custom development. Fribourg, Bern, Valais, Lausanne, Geneva.

Visit dootix.com

Key Findings

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

Performance Metrics

dootix.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

Network Requests Diagram

dootix.com

226 ms

www.dootix.com

457 ms

en

776 ms

gtm.js

70 ms

tailwind.css

101 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 89% of them (31 requests) were addressed to the original Dootix.com, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (924 ms) belongs to the original domain Dootix.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 123.8 kB (48%)

Content Size

256.7 kB

After Optimization

132.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Dootix.com main page is 256.7 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. 25% of websites need less resources to load. HTML takes 132.1 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 117.6 kB

  • Original 132.1 kB
  • After minification 118.6 kB
  • After compression 14.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 117.6 kB or 89% of the original size.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 118.2 kB
  • After minification 118.2 kB
  • After compression 118.2 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

-98%

Potential reduce by 6.2 kB

  • Original 6.3 kB
  • After minification 154 B
  • After compression 140 B

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. Dootix.com needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 98% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

24

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dootix. 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

dootix.com

dootix.com

226 ms

www.dootix.com

www.dootix.com

457 ms

en

en

776 ms

gtm.js

gtm.js

70 ms

tailwind.css

tailwind.css

101 ms

site.css

site.css

200 ms

vue.global.prod.js

vue.global.prod.js

42 ms

js

js

80 ms

site.js

site.js

588 ms

vue.global.prod.js

vue.global.prod.js

38 ms

4a140de8fb6d8483848456dd3abb555e.webp

4a140de8fb6d8483848456dd3abb555e.webp

101 ms

label4.svg

label4.svg

235 ms

f044378d31f5edc3a9be3f80ff80330f.webp

f044378d31f5edc3a9be3f80ff80330f.webp

200 ms

eb8cf5ce345bb749a03f286366299c6f.webp

eb8cf5ce345bb749a03f286366299c6f.webp

293 ms

a26589921c6b718faa81e369d12a3f18.webp

a26589921c6b718faa81e369d12a3f18.webp

293 ms

dc19e5c298eb523695eb955084b221c2.webp

dc19e5c298eb523695eb955084b221c2.webp

298 ms

background-home-header.svg

background-home-header.svg

303 ms

a62bae0cc05d2c5a2b98f42125899ff8.webp

a62bae0cc05d2c5a2b98f42125899ff8.webp

437 ms

76c2daa2f9ff01e77bb3951c63bcab3d.webp

76c2daa2f9ff01e77bb3951c63bcab3d.webp

488 ms

979544d156cf62f5298bf77976bb2aff.webp

979544d156cf62f5298bf77976bb2aff.webp

392 ms

9fb92a594d5f4e5d7a952142b3d1deb7.webp

9fb92a594d5f4e5d7a952142b3d1deb7.webp

397 ms

1313e44992cb3cdfc6e9c8c79a14cd25.webp

1313e44992cb3cdfc6e9c8c79a14cd25.webp

505 ms

acd6a281a661264bf1498a3100ad3608.webp

acd6a281a661264bf1498a3100ad3608.webp

477 ms

13c47b5f3530f8695635c89cb6efb23a.webp

13c47b5f3530f8695635c89cb6efb23a.webp

489 ms

fef1d7091d2c8332e4e786753dad62b5.webp

fef1d7091d2c8332e4e786753dad62b5.webp

496 ms

7a8f34ee6faa53b2320b4d5f30bd80b5.webp

7a8f34ee6faa53b2320b4d5f30bd80b5.webp

538 ms

background-home-header-blanc.svg

background-home-header-blanc.svg

577 ms

46fc599a91ce2bbe2a3f9f08fe994e73.webp

46fc599a91ce2bbe2a3f9f08fe994e73.webp

681 ms

dootix_logo_blanc_neg.svg

dootix_logo_blanc_neg.svg

587 ms

5e5280a77248954356662d746c653af7.webp

5e5280a77248954356662d746c653af7.webp

593 ms

odoo_gold_partner_rgb.svg

odoo_gold_partner_rgb.svg

606 ms

Pilat%20Regular.otf

Pilat%20Regular.otf

838 ms

Pilat%20Book.otf

Pilat%20Book.otf

723 ms

Pilat%20Demi.otf

Pilat%20Demi.otf

924 ms

Pilat%20Light.otf

Pilat%20Light.otf

835 ms

Accessibility Review

dootix.com accessibility score

89

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

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

Image elements do not have [alt] attributes

Best Practices

dootix.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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dootix.com 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

Image elements do not have [alt] attributes

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 Dootix.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 Dootix.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

dootix.com

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