Tools & Wizards About Us
digitalis.io screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

digitalis.io

Apache Cassandra, Kafka and Data Experts | Digitalis

Page Load Speed

1.9 sec in total

First Response

166 ms

Resources Loaded

1 sec

Page Rendered

674 ms

digitalis.io screenshot

About Website

Visit digitalis.io now to see the best up-to-date Digitalis content for United Kingdom and also check out these interesting facts you probably never knew about digitalis.io

We provide design & implementation through to fully managed 24×7 operations for your Apache Cassandra, Kafka & Data platforms.

Visit digitalis.io

Key Findings

We analyzed Digitalis.io page load time and found that the first response time was 166 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

digitalis.io performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value2,110 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value1.036

2/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

digitalis.io

166 ms

digitalis.io

169 ms

all.min.css

45 ms

7a82b.css

94 ms

6baa9.css

27 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 76% of them (38 requests) were addressed to the original Digitalis.io, 6% (3 requests) were made to Static.addtoany.com and 4% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (264 ms) belongs to the original domain Digitalis.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.4 kB (29%)

Content Size

759.8 kB

After Optimization

541.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digitalis.io main page is 759.8 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. 45% of websites need less resources to load. Javascripts take 294.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 216.2 kB

  • Original 247.8 kB
  • After minification 239.5 kB
  • After compression 31.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 216.2 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 309 B

  • Original 85.6 kB
  • After minification 85.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. Digitalis images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.9 kB

  • Original 294.1 kB
  • After minification 294.1 kB
  • After compression 292.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

-0%

Potential reduce by 5 B

  • Original 132.3 kB
  • After minification 132.3 kB
  • After compression 132.3 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. Digitalis.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (62%)

Requests Now

37

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

digitalis.io

digitalis.io

166 ms

digitalis.io

digitalis.io

169 ms

all.min.css

all.min.css

45 ms

7a82b.css

7a82b.css

94 ms

6baa9.css

6baa9.css

27 ms

email-decode.min.js

email-decode.min.js

25 ms

d5ca8.css

d5ca8.css

35 ms

b441f.js

b441f.js

42 ms

b68ea.js

b68ea.js

156 ms

ede7d.js

ede7d.js

50 ms

api.js

api.js

49 ms

4e280.js

4e280.js

50 ms

api.js

api.js

71 ms

2a6b9.js

2a6b9.js

56 ms

11d31.js

11d31.js

71 ms

82111.js

82111.js

71 ms

864c2.js

864c2.js

71 ms

bfd15.js

bfd15.js

152 ms

js

js

65 ms

7d501.js

7d501.js

152 ms

rocket-loader.min.js

rocket-loader.min.js

147 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

65 ms

BG_Blocks_v1.svg

BG_Blocks_v1.svg

18 ms

aws_300x260-01.svg

aws_300x260-01.svg

24 ms

DataStax_300x260.svg

DataStax_300x260.svg

29 ms

kubernetes_300x260-01.svg

kubernetes_300x260-01.svg

17 ms

SUSE.png

SUSE.png

189 ms

elastic_300x260.svg

elastic_300x260.svg

22 ms

Confluent.png

Confluent.png

190 ms

azure_300x260-01-01.svg

azure_300x260-01-01.svg

36 ms

LogoImages_TigeraColor2.png

LogoImages_TigeraColor2.png

190 ms

WANdisco.png

WANdisco.png

247 ms

HeaderWithLines.jpg

HeaderWithLines.jpg

187 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

186 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

188 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

188 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

218 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

217 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

218 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

242 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

243 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

264 ms

modules.ttf

modules.ttf

115 ms

page.js

page.js

45 ms

loader.js

loader.js

214 ms

61a7c3ef079ef0001c14f51e

61a7c3ef079ef0001c14f51e

135 ms

loader

loader

156 ms

sm.25.html

sm.25.html

16 ms

eso.D0Uc7kY6.js

eso.D0Uc7kY6.js

25 ms

loader.min.js

loader.min.js

64 ms

Accessibility Review

digitalis.io accessibility score

82

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

Heading elements are not in a sequentially-descending order

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

digitalis.io best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

digitalis.io SEO score

84

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digitalis.io 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 Digitalis.io 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

digitalis.io

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