Tools & Wizards About Us
diandian.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

diandian.com

点点数据-专业移动应用/游戏App数据查询分析平台

Page Load Speed

42.1 sec in total

First Response

4.8 sec

Resources Loaded

29.9 sec

Page Rendered

7.4 sec

diandian.com screenshot

About Website

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

点点数据，专业移动应用/游戏App数据查询分析平台，为您提供App市场份额分析(App下载/收入数据)、用户行为分析(App活跃、App留存、使用次数、使用时长、用户画像)等App数据分析统计。

Visit diandian.com

Key Findings

We analyzed Diandian.com page load time and found that the first response time was 4.8 sec and then it took 37.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

diandian.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.7 s

0/100

25%

SI (Speed Index)

Value23.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,270 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

diandian.com

4781 ms

startpage.$7250.less

2457 ms

seed.$6804.js

2863 ms

trackerbase.js

805 ms

htmlbg.$5752.png

718 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Diandian.com, 54% (29 requests) were made to S.srcdd.com and 19% (10 requests) were made to M3.img.srcdd.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source M1.img.srcdd.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 439.1 kB (68%)

Content Size

646.2 kB

After Optimization

207.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-90%

Potential reduce by 134.7 kB

  • Original 150.0 kB
  • After minification 115.9 kB
  • After compression 15.3 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 34.0 kB, which is 23% 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 134.7 kB or 90% of the original size.

Image Optimization

-13%

Potential reduce by 10.9 kB

  • Original 81.8 kB
  • After minification 70.9 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, Diandian needs image optimization as it can save up to 10.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 200.7 kB

  • Original 306.3 kB
  • After minification 306.3 kB
  • After compression 105.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 200.7 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 92.8 kB

  • Original 108.2 kB
  • After minification 108.2 kB
  • After compression 15.4 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. Diandian.com needs all CSS files to be minified and compressed as it can save up to 92.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (25%)

Requests Now

48

After Optimization

36

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

diandian.com

diandian.com

4781 ms

startpage.$7250.less

startpage.$7250.less

2457 ms

seed.$6804.js

seed.$6804.js

2863 ms

trackerbase.js

trackerbase.js

805 ms

htmlbg.$5752.png

htmlbg.$5752.png

718 ms

feed.$7227.js

feed.$7227.js

1126 ms

util.$7202.js

util.$7202.js

739 ms

DD6DD1EA2A1F2FBF15141F72BD7B9C438C062A7A0153B_500_167.GIF

DD6DD1EA2A1F2FBF15141F72BD7B9C438C062A7A0153B_500_167.GIF

1071 ms

header.$5752.png

header.$5752.png

783 ms

logo-0518.$6396.png

logo-0518.$6396.png

764 ms

split.$6883.png

split.$6883.png

762 ms

content-holder.$5106.png

content-holder.$5106.png

757 ms

feed-icons.$6973.png

feed-icons.$6973.png

1074 ms

feed-bg-sprites.$5106.png

feed-bg-sprites.$5106.png

977 ms

8FA5F72EA0B42727AE4BE40B42A01E0A_S64_64_64.jpeg

8FA5F72EA0B42727AE4BE40B42A01E0A_S64_64_64.jpeg

613 ms

core.js

core.js

1766 ms

loading-small.$6925.gif

loading-small.$6925.gif

334 ms

feed-img-too-high-tip.$5594.png

feed-img-too-high-tip.$5594.png

546 ms

D3E62DB058802CA5E2002AE07F6C3932_S64_64_64.JPEG

D3E62DB058802CA5E2002AE07F6C3932_S64_64_64.JPEG

2990 ms

template.js

template.js

885 ms

sky.js

sky.js

878 ms

Dialog.js

Dialog.js

868 ms

feedslide.js

feedslide.js

837 ms

photo-reply.js

photo-reply.js

780 ms

aside-reg-login-line.$7164.png

aside-reg-login-line.$7164.png

2295 ms

aside-login-register-btn.$7164.png

aside-login-register-btn.$7164.png

549 ms

reg-login-formv2.$7176.js

reg-login-formv2.$7176.js

547 ms

sidemenu.$6372.png

sidemenu.$6372.png

3905 ms

5DBDF4B52332BB4E3C8DA2BBE143D992_S40_40_40.JPEG

5DBDF4B52332BB4E3C8DA2BBE143D992_S40_40_40.JPEG

19641 ms

DAFB9BA8E02EB40B8873B5087B1620CE_S40_40_40.PNG

DAFB9BA8E02EB40B8873B5087B1620CE_S40_40_40.PNG

535 ms

sidemenu-item.$5106.png

sidemenu-item.$5106.png

459 ms

sidemenu-sub-item.$5106.png

sidemenu-sub-item.$5106.png

459 ms

2C329347AC6CF87E423162C8B63DDC31_S40_40_40.JPEG

2C329347AC6CF87E423162C8B63DDC31_S40_40_40.JPEG

20453 ms

EAA48D281AA5B2A2C123887F4E21F04E_S40_40_40.jpeg

EAA48D281AA5B2A2C123887F4E21F04E_S40_40_40.jpeg

353 ms

frameupload.js

frameupload.js

1385 ms

t.gif

t.gif

1287 ms

ga.$5928.js

ga.$5928.js

1297 ms

feed-short-tip.$6396.png

feed-short-tip.$6396.png

1491 ms

4EB9238A67EDF3505087AFDE2674C713_ORIG_245_150.gif

4EB9238A67EDF3505087AFDE2674C713_ORIG_245_150.gif

1226 ms

83619575B159C4ED6AC9B0A1F79071D4_ORIG_245_150.gif

83619575B159C4ED6AC9B0A1F79071D4_ORIG_245_150.gif

1882 ms

__utm.gif

__utm.gif

1790 ms

ABA2D0CF682E5C1E0C89B412A3012FBE_ORIG_245_150.gif

ABA2D0CF682E5C1E0C89B412A3012FBE_ORIG_245_150.gif

856 ms

F5B931C1A4345E1B713295099A006233_ORIG_245_150.gif

F5B931C1A4345E1B713295099A006233_ORIG_245_150.gif

1484 ms

030139D9DBA6235CA36A0ECE10B8BC06_ORIG_500_250.gif

030139D9DBA6235CA36A0ECE10B8BC06_ORIG_500_250.gif

1053 ms

78E9AEF3117641A482555D8DDAACFAE202122212555E3_500_273.GIF

78E9AEF3117641A482555D8DDAACFAE202122212555E3_500_273.GIF

1344 ms

EC81A35F774BD22D7BBB49C93CBB6C3F_B500_900_500_625.jpeg

EC81A35F774BD22D7BBB49C93CBB6C3F_B500_900_500_625.jpeg

679 ms

1B3774DA3923B9A69193BFE2C092CDB2_B250_400_250_202.jpeg

1B3774DA3923B9A69193BFE2C092CDB2_B250_400_250_202.jpeg

697 ms

C1F458F18DFFE79B8AEED1003977342829C08AF51B3A4_500_184.GIF

C1F458F18DFFE79B8AEED1003977342829C08AF51B3A4_500_184.GIF

982 ms

2395F46B27762710C5F42830AE1E8BF08E078112DAC5E_500_184.GIF

2395F46B27762710C5F42830AE1E8BF08E078112DAC5E_500_184.GIF

1012 ms

9C88D000DB79689114E5F4B54DBFD3F6_ORIG_500_272.gif

9C88D000DB79689114E5F4B54DBFD3F6_ORIG_500_272.gif

1056 ms

B413524B94C4DC33B3CFDE6EFE748F17_500_275.GIF

B413524B94C4DC33B3CFDE6EFE748F17_500_275.GIF

1222 ms

12877904B1EA310A0235C08B623C3E8504D6375CA6333_500_184.GIF

12877904B1EA310A0235C08B623C3E8504D6375CA6333_500_184.GIF

1387 ms

5A95E27DB039782F053F59C2952ABB24024289544F237_500_184.GIF

5A95E27DB039782F053F59C2952ABB24024289544F237_500_184.GIF

1405 ms

proxy.html

proxy.html

1540 ms

Accessibility Review

diandian.com accessibility score

52

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.

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

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

diandian.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

diandian.com SEO score

83

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

diandian.com

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