Tools & Wizards About Us
daml.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

daml.com

Develop with Daml

Page Load Speed

1.3 sec in total

First Response

97 ms

Resources Loaded

885 ms

Page Rendered

302 ms

daml.com screenshot

About Website

Visit daml.com now to see the best up-to-date Daml content for India and also check out these interesting facts you probably never knew about daml.com

Build regulatory-grade tokenization and blockchain applications with the Daml smart contract platform and Canton blockchain protocol

Visit daml.com

Key Findings

We analyzed Daml.com page load time and found that the first response time was 97 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

daml.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value5.4 s

55/100

10%

TBT (Total Blocking Time)

Value4,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

developers

97 ms

gtm.js

96 ms

css2

48 ms

jquery-1.11.2.js

34 ms

jquery-migrate-1.2.1.js

67 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Daml.com, 25% (12 requests) were made to Fonts.gstatic.com and 8% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (387 ms) relates to the external source Cmp.osano.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.0 kB (26%)

Content Size

200.6 kB

After Optimization

148.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Daml.com main page is 200.6 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. 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. Javascripts take 95.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 44.3 kB

  • Original 52.7 kB
  • After minification 37.0 kB
  • After compression 8.4 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 15.7 kB, which is 30% 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 44.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 47.7 kB
  • After minification 47.7 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. Daml images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 7.3 kB

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

-8%

Potential reduce by 362 B

  • Original 4.5 kB
  • After minification 4.5 kB
  • After compression 4.2 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. Daml.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (77%)

Requests Now

35

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

developers

developers

97 ms

gtm.js

gtm.js

96 ms

css2

css2

48 ms

jquery-1.11.2.js

jquery-1.11.2.js

34 ms

jquery-migrate-1.2.1.js

jquery-migrate-1.2.1.js

67 ms

styles.css

styles.css

74 ms

style2.min.css

style2.min.css

71 ms

module_170337940822_Global_Header.min.css

module_170337940822_Global_Header.min.css

93 ms

module_170100213331_hero.min.css

module_170100213331_hero.min.css

66 ms

module_169998636655_content_column.min.css

module_169998636655_content_column.min.css

63 ms

module_169807534122_intro.min.css

module_169807534122_intro.min.css

95 ms

module_170337940595_Global_Footer.min.css

module_170337940595_Global_Footer.min.css

95 ms

js

js

92 ms

osano.js

osano.js

387 ms

js

js

93 ms

embed.js

embed.js

40 ms

jquery.min.js

jquery.min.js

96 ms

bootstrap.min.js

bootstrap.min.js

133 ms

slick.min.js

slick.min.js

134 ms

main.min.js

main.min.js

134 ms

primaryNav.min.js

primaryNav.min.js

135 ms

project.js

project.js

136 ms

module_169998636655_content_column.min.js

module_169998636655_content_column.min.js

135 ms

2704830.js

2704830.js

136 ms

index.js

index.js

136 ms

gtm.js

gtm.js

102 ms

footer-logo-white.svg

footer-logo-white.svg

93 ms

nav-icon-arrow.svg

nav-icon-arrow.svg

82 ms

training-certification-hero.jpg

training-certification-hero.jpg

83 ms

chevron.svg

chevron.svg

84 ms

footer-logo.svg

footer-logo.svg

86 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf

45 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fMZg.ttf

61 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfMZg.ttf

84 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfMZg.ttf

91 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeMZg.ttf

91 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYMZg.ttf

91 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZg.ttf

92 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYMZg.ttf

84 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYMZg.ttf

104 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

103 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

105 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

104 ms

insight.min.js

insight.min.js

51 ms

banner.js

banner.js

69 ms

2704830.js

2704830.js

91 ms

collectedforms.js

collectedforms.js

63 ms

insight_tag_errors.gif

insight_tag_errors.gif

113 ms

Accessibility Review

daml.com accessibility score

84

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

[role] values are not valid

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

Image elements do not have [alt] attributes

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

daml.com SEO score

79

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

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

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

daml.com

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