Tools & Wizards About Us
duole.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

duole.com

多乐游戏-让生活多一点乐趣 | 全国各地游戏合集

Page Load Speed

7.7 sec in total

First Response

725 ms

Resources Loaded

6.7 sec

Page Rendered

315 ms

duole.com screenshot

About Website

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

多乐游戏是全国深受欢迎的够级、保皇、跑得快、升级、掼蛋、象棋、双扣等棋牌游戏平台。如：多乐贵阳捉鸡麻将、多乐中国象棋、多乐跑胡子、多乐双扣等，多乐棋牌秉承用户至上的理念，让棋牌文化多一份快乐，多一份传承。

Visit duole.com

Key Findings

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

Performance Metrics

duole.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

duole.com

725 ms

www.duole.com

1067 ms

polyfill.min.js

1463 ms

swiper.min.js

1498 ms

app.833aaa42f8f8bcaa1cf45bd91a9189d2.css

236 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 69% of them (36 requests) were addressed to the original Duole.com, 21% (11 requests) were made to Assets-v2.duole.com and 8% (4 requests) were made to Assets.duole.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Duole.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 278.0 kB (8%)

Content Size

3.3 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Duole.com main page is 3.3 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. 50% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 73.7 kB

  • Original 90.6 kB
  • After minification 90.4 kB
  • After compression 16.9 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 73.7 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 204.3 kB

  • Original 3.2 MB
  • After minification 3.0 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. Duole images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 36 B

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

Requests Breakdown

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

Requests Now

50

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

duole.com

duole.com

725 ms

www.duole.com

www.duole.com

1067 ms

polyfill.min.js

polyfill.min.js

1463 ms

swiper.min.js

swiper.min.js

1498 ms

app.833aaa42f8f8bcaa1cf45bd91a9189d2.css

app.833aaa42f8f8bcaa1cf45bd91a9189d2.css

236 ms

manifest.7f5492cb5d9ebc6399de.js

manifest.7f5492cb5d9ebc6399de.js

470 ms

base.52e9ce372af4996b1ca6.js

base.52e9ce372af4996b1ca6.js

702 ms

1.0c90e26ded92bb790bd8.js

1.0c90e26ded92bb790bd8.js

706 ms

vendor.20052043def064ba001d.js

vendor.20052043def064ba001d.js

1066 ms

app.74094c35684906bb1fc6.js

app.74094c35684906bb1fc6.js

708 ms

shengji-200x200.png

shengji-200x200.png

1396 ms

label_sm_90020.png

label_sm_90020.png

959 ms

2dc3612b6cffb763a866fb58cb6fe4cb.png

2dc3612b6cffb763a866fb58cb6fe4cb.png

260 ms

1a0965580edc4fa8cbb94168db2e009b.png

1a0965580edc4fa8cbb94168db2e009b.png

258 ms

logo_black.e167bbd.png

logo_black.e167bbd.png

236 ms

3.6ee0173.jpg

3.6ee0173.jpg

1191 ms

5.75d08d9.jpg

5.75d08d9.jpg

1095 ms

6.caa4932.jpg

6.caa4932.jpg

1016 ms

4.6ee994b.jpg

4.6ee994b.jpg

951 ms

8.4ccbd03.jpg

8.4ccbd03.jpg

1312 ms

shengjiCode.3293138.png

shengjiCode.3293138.png

551 ms

banner.a7ae81e.png

banner.a7ae81e.png

786 ms

goujiCode.9db5125.png

goujiCode.9db5125.png

1020 ms

banner.6613abd.png

banner.6613abd.png

1294 ms

guandanCode.22c4379.png

guandanCode.22c4379.png

1295 ms

banner.01efcd6.png

banner.01efcd6.png

1354 ms

baohuangCode.5c4aa20.png

baohuangCode.5c4aa20.png

1430 ms

banner.e0c36be.png

banner.e0c36be.png

1582 ms

paohuziCode.67f1929.png

paohuziCode.67f1929.png

1661 ms

banner.88fe7d4.png

banner.88fe7d4.png

1531 ms

paodekuaiCode.29cfd32.png

paodekuaiCode.29cfd32.png

1613 ms

banner.a3b29b3.png

banner.a3b29b3.png

1681 ms

dlxiangqiCode.5358c6a.png

dlxiangqiCode.5358c6a.png

1670 ms

duolemjCode.f801a4a.png

duolemjCode.f801a4a.png

1846 ms

zhuojimjCode.9f40ff2.png

zhuojimjCode.9f40ff2.png

1909 ms

doudizhuCode.397ff6c.png

doudizhuCode.397ff6c.png

1881 ms

shuangkouCode.eb5a12d.png

shuangkouCode.eb5a12d.png

1948 ms

message.24aa4c0.png

message.24aa4c0.png

1910 ms

duole_logo.c2d317e.png

duole_logo.c2d317e.png

1915 ms

keep_on_record.d0289dc.png

keep_on_record.d0289dc.png

2084 ms

erweima.c0c3b10.jpg

erweima.c0c3b10.jpg

2421 ms

gouji-200x200.png

gouji-200x200.png

1638 ms

guandan-200x200.png

guandan-200x200.png

1961 ms

baohuang-200x200.png

baohuang-200x200.png

1698 ms

paohuzi-200x200.png

paohuzi-200x200.png

1414 ms

paodekuai-200x200.png

paodekuai-200x200.png

1423 ms

dlxiangqi-200x200.png

dlxiangqi-200x200.png

1896 ms

duolemj-200x200.png

duolemj-200x200.png

1656 ms

zhuojimj-200x200.png

zhuojimj-200x200.png

1675 ms

doudizhu-200x200.png

doudizhu-200x200.png

2127 ms

shuangkou-200x200.png

shuangkou-200x200.png

1898 ms

get-game-list

get-game-list

2154 ms

Accessibility Review

duole.com accessibility score

75

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

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

duole.com

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