Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

Page Load Speed

9.5 sec in total

First Response

994 ms

Resources Loaded

7.8 sec

Page Rendered

754 ms

dingtalk.com screenshot

About Website

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

钉钉是阿里集团专为中小企业打造的通讯、协同的移动办公平台,帮助企业内部沟通和商务沟通更加高效安全。特色支持:消息阅读状态一目了然,重要事DING电话使命必达,紧急事免费电话多方通话,企业通讯录随时随地找人,多端互动。

Visit dingtalk.com

Key Findings

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

Performance Metrics

dingtalk.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value6.7 s

35/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.681

8/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

dingtalk.com

994 ms

www.dingtalk.com

5304 ms

index.css

227 ms

aplus_v2.js

829 ms

TB1FN16LFXXXXXJXpXXXXXXXXXX-256-130.png

2930 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Dingtalk.com, 37% (48 requests) were made to Img.alicdn.com and 15% (19 requests) were made to Gtms03.alicdn.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Dingtalk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (15%)

Content Size

6.6 MB

After Optimization

5.6 MB

In fact, the total size of Dingtalk.com main page is 6.6 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. 75% 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. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 60.8 kB

  • Original 70.5 kB
  • After minification 53.1 kB
  • After compression 9.8 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 17.4 kB, which is 25% 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 60.8 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 546.3 kB

  • Original 6.0 MB
  • After minification 5.5 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. Dingtalk images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 217.8 kB

  • Original 287.9 kB
  • After minification 231.3 kB
  • After compression 70.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 217.8 kB or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 191.0 kB

  • Original 223.4 kB
  • After minification 177.9 kB
  • After compression 32.5 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. Dingtalk.com needs all CSS files to be minified and compressed as it can save up to 191.0 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

126

After Optimization

122

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

Accessibility Review

dingtalk.com accessibility score

46

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

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

High

Page has valid source maps

SEO Factors

dingtalk.com SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

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