Tools & Wizards About Us
dotodo.net screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

dotodo.net

Page Load Speed

33.8 sec in total

First Response

1.2 sec

Resources Loaded

32.3 sec

Page Rendered

301 ms

dotodo.net screenshot

About Website

Click here to check amazing Dotodo content. Otherwise, check out these important facts you probably never knew about dotodo.net

广州网站建设，品拓互联13年广州网站制作公司经验,政府出资的广州网站设计公司,20000多家网站制作成功案例,专业网页设计公司：广州做网站公司电话020-87530592广州品拓网络科技有限公司

Visit dotodo.net

Key Findings

We analyzed Dotodo.net page load time and found that the first response time was 1.2 sec and then it took 32.6 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 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

dotodo.net performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value20.7 s

0/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.499

16/100

15%

TTI (Time to Interactive)

Value20.9 s

1/100

10%

Network Requests Diagram

dotodo.net

1224 ms

index.htm

1770 ms

ajax.js

1244 ms

css.css

1993 ms

inflash.js

1241 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 75% of them (61 requests) were addressed to the original Dotodo.net, 11% (9 requests) were made to Sysimages.tq.cn and 5% (4 requests) were made to Pub.idqqimg.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Bdimg.share.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 541.4 kB (32%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dotodo.net main page is 1.7 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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 70.3 kB

  • Original 86.2 kB
  • After minification 74.7 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 11.4 kB, which is 13% 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 70.3 kB or 82% of the original size.

Image Optimization

-14%

Potential reduce by 165.7 kB

  • Original 1.2 MB
  • After minification 1.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. Obviously, Dotodo needs image optimization as it can save up to 165.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 272.6 kB

  • Original 378.1 kB
  • After minification 358.8 kB
  • After compression 105.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 272.6 kB or 72% of the original size.

CSS Optimization

-80%

Potential reduce by 32.8 kB

  • Original 41.2 kB
  • After minification 34.8 kB
  • After compression 8.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. Dotodo.net needs all CSS files to be minified and compressed as it can save up to 32.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (28%)

Requests Now

74

After Optimization

53

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dotodo.net

dotodo.net

1224 ms

index.htm

index.htm

1770 ms

ajax.js

ajax.js

1244 ms

css.css

css.css

1993 ms

inflash.js

inflash.js

1241 ms

lytebox.js

lytebox.js

2765 ms

lytebox.css

lytebox.css

1994 ms

index.css

index.css

997 ms

jquery-1.8.1.min.js

jquery-1.8.1.min.js

3664 ms

common.js

common.js

700 ms

index.js

index.js

3136 ms

style.css

style.css

1097 ms

meu.css

meu.css

1036 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

2344 ms

stat.php

stat.php

552 ms

floatcard

floatcard

1186 ms

jquery.homecycle.js

jquery.homecycle.js

374 ms

gd321_02.jpg

gd321_02.jpg

474 ms

banner02.jpg

banner02.jpg

19671 ms

20150207.jpg

20150207.jpg

9788 ms

banner03.jpg

banner03.jpg

19671 ms

GetCode.asp

GetCode.asp

488 ms

ttp_06.jpg

ttp_06.jpg

876 ms

LeSeno.Com_2010071113513744278.jpg

LeSeno.Com_2010071113513744278.jpg

2813 ms

LeSeno.Com_2010051302084444680.jpg

LeSeno.Com_2010051302084444680.jpg

4681 ms

banner.jpg

banner.jpg

12831 ms

foot2014_14.jpg

foot2014_14.jpg

5388 ms

foot2014_16.jpg

foot2014_16.jpg

5119 ms

paycar.jpg

paycar.jpg

5937 ms

foot2014_20.jpg

foot2014_20.jpg

6227 ms

footweixin_03.jpg

footweixin_03.jpg

6376 ms

bottom20131105_06.jpg

bottom20131105_06.jpg

11301 ms

bottom20131105_04.jpg

bottom20131105_04.jpg

7272 ms

weixinkefu.png

weixinkefu.png

8200 ms

tel.jpg

tel.jpg

5407 ms

index_15.jpg

index_15.jpg

2452 ms

LeSeno.Com_201097185423815.jpg

LeSeno.Com_201097185423815.jpg

14580 ms

LeSeno.Com_201091616450241.jpg

LeSeno.Com_201091616450241.jpg

5493 ms

LeSeno_Com_20100502011529533652.jpg

LeSeno_Com_20100502011529533652.jpg

2597 ms

y.gif

y.gif

931 ms

a3.gif

a3.gif

1390 ms

LeSeno.Com_2010092809062695686.jpg

LeSeno.Com_2010092809062695686.jpg

1855 ms

LeSeno.Com_2010092809100326362.jpg

LeSeno.Com_2010092809100326362.jpg

2327 ms

LeSeno.Com_2010092809235514552.jpg

LeSeno.Com_2010092809235514552.jpg

4699 ms

LeSeno.Com_2010092820484049398.jpg

LeSeno.Com_2010092820484049398.jpg

6008 ms

LeSeno.Com_2010050201232239199.jpg

LeSeno.Com_2010050201232239199.jpg

4772 ms

LeSeno.Com_2010092819290952335.jpg

LeSeno.Com_2010092819290952335.jpg

6412 ms

LeSeno.Com_2010092819362191455.jpg

LeSeno.Com_2010092819362191455.jpg

5907 ms

LeSeno.Com_2010092819413785238.jpg

LeSeno.Com_2010092819413785238.jpg

8371 ms

2015.jpg

2015.jpg

15683 ms

2014032601.jpg

2014032601.jpg

15711 ms

2014032602.jpg

2014032602.jpg

19649 ms

gd321_03.gif

gd321_03.gif

7205 ms

gd321_04.gif

gd321_04.gif

6286 ms

gd321_10.gif

gd321_10.gif

13196 ms

menu_new.gif

menu_new.gif

16485 ms

di_16.jpg

di_16.jpg

7747 ms

index_12_2.jpg

index_12_2.jpg

6672 ms

index_12.jpg

index_12.jpg

7268 ms

t-bg_33.jpg

t-bg_33.jpg

7079 ms

stat.htm

stat.htm

234 ms

core.php

core.php

1593 ms

bottom20131105_02.jpg

bottom20131105_02.jpg

14425 ms

share.js

share.js

19922 ms

all_20100501.js

all_20100501.js

2457 ms

as.js

as.js

1009 ms

style.css

style.css

1637 ms

style.css

style.css

1913 ms

float.js

float.js

2638 ms

invite.js

invite.js

2930 ms

hbtn_04.png

hbtn_04.png

12677 ms

hbtn_06.png

hbtn_06.png

10461 ms

pa

pa

19808 ms

bg_c2.png

bg_c2.png

1803 ms

accept_c2.png

accept_c2.png

1182 ms

message_c2.png

message_c2.png

1222 ms

scriptonline.js

scriptonline.js

807 ms

button_11.gif

button_11.gif

819 ms

button_11.gif

button_11.gif

817 ms

button_11.gif

button_11.gif

222 ms

button_11.gif

button_11.gif

220 ms

Accessibility Review

dotodo.net accessibility score

43

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

dotodo.net best practices score

50

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dotodo.net SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dotodo.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Dotodo.net main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

dotodo.net

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