Tools & Wizards About Us
mydigoo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mydigoo.com

Digoo Official Website | Online Shopping for Digoo Brand Products

Page Load Speed

2.4 sec in total

First Response

144 ms

Resources Loaded

1.4 sec

Page Rendered

844 ms

mydigoo.com screenshot

About Website

Welcome to mydigoo.com homepage info - get ready to check My Digoo best content for India right away, or after learning these important things about mydigoo.com

Digoo are dedicated to creating the best household product，and make sure you enjoy your dream of life. Shop Cheap with high quality household product at mydigoo.com.

Visit mydigoo.com

Key Findings

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

Performance Metrics

mydigoo.com performance score

0

Network Requests Diagram

mydigoo.com

144 ms

www.mydigoo.com

147 ms

basic.css,iconfont.css,swiper.css

94 ms

public.css

111 ms

iconfont.css

114 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 62% of them (38 requests) were addressed to the original Mydigoo.com, 16% (10 requests) were made to Img.mydigoo.com and 5% (3 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (664 ms) relates to the external source Img.mydigoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.0 kB (6%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 70.4 kB

  • Original 79.3 kB
  • After minification 37.5 kB
  • After compression 8.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 41.8 kB, which is 53% 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.4 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 4.4 kB

  • Original 1.2 MB
  • After minification 1.2 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. My Digoo images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 232 B

  • Original 27.5 kB
  • After minification 27.5 kB
  • After compression 27.3 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

-20%

Potential reduce by 9.0 kB

  • Original 46.3 kB
  • After minification 42.3 kB
  • After compression 37.3 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. Mydigoo.com needs all CSS files to be minified and compressed as it can save up to 9.0 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (59%)

Requests Now

58

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mydigoo.com

mydigoo.com

144 ms

www.mydigoo.com

www.mydigoo.com

147 ms

basic.css,iconfont.css,swiper.css

basic.css,iconfont.css,swiper.css

94 ms

public.css

public.css

111 ms

iconfont.css

iconfont.css

114 ms

iconfont.css

iconfont.css

133 ms

flags.css

flags.css

119 ms

smarthome.css

smarthome.css

152 ms

subscribe.css

subscribe.css

178 ms

index.css

index.css

200 ms

jquery.js

jquery.js

122 ms

jquery.lazyload.js

jquery.lazyload.js

222 ms

jq.cookie.js

jq.cookie.js

233 ms

js

js

59 ms

headerUser.css

headerUser.css

219 ms

policy.css

policy.css

259 ms

email-decode.min.js

email-decode.min.js

180 ms

subscribe.js

subscribe.js

366 ms

header.js

header.js

360 ms

swiper.min.js

swiper.min.js

368 ms

common_templates_style.js

common_templates_style.js

237 ms

public.js

public.js

364 ms

policy.js

policy.js

367 ms

bgd.js

bgd.js

129 ms

index.js

index.js

363 ms

Tdrag.js

Tdrag.js

474 ms

homeBuilder.js

homeBuilder.js

455 ms

login.js

login.js

474 ms

login.js

login.js

453 ms

GA.js

GA.js

472 ms

error.js

error.js

455 ms

1552642994_29936699.png

1552642994_29936699.png

247 ms

1553569487_56036699.gif

1553569487_56036699.gif

301 ms

1553569496_59736699.gif

1553569496_59736699.gif

382 ms

1553569504_72936699.gif

1553569504_72936699.gif

650 ms

1553570860_39436699.gif

1553570860_39436699.gif

631 ms

1553569564_73336699.gif

1553569564_73336699.gif

664 ms

1553569567_9836699.gif

1553569567_9836699.gif

473 ms

loading.gif

loading.gif

299 ms

sub_01.png

sub_01.png

369 ms

sub_02.png

sub_02.png

356 ms

userHeaderInfo.html

userHeaderInfo.html

331 ms

loading_default.gif

loading_default.gif

281 ms

analytics.js

analytics.js

197 ms

iconfont.woff

iconfont.woff

242 ms

iconfont.woff

iconfont.woff

270 ms

1599467310_81340244.jpg

1599467310_81340244.jpg

366 ms

1599467395_14240244.jpg

1599467395_14240244.jpg

220 ms

1599467533_96340244.jpg

1599467533_96340244.jpg

276 ms

w

w

184 ms

heat_map_page.js

heat_map_page.js

257 ms

fbevents.js

fbevents.js

80 ms

1593338451_33240244.jpg

1593338451_33240244.jpg

219 ms

api:client.js

api:client.js

112 ms

collect

collect

25 ms

1547401368833299

1547401368833299

153 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

23 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

24 ms

visit

visit

163 ms

iconfont.ttf

iconfont.ttf

145 ms

iconfont.svg

iconfont.svg

114 ms

SEO Factors

mydigoo.com SEO score

0

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

mydigoo.com

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