Tools & Wizards About Us
diddots.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

diddots.com

Did dots

Page Load Speed

9.2 sec in total

First Response

1 sec

Resources Loaded

7.7 sec

Page Rendered

460 ms

diddots.com screenshot

About Website

Welcome to diddots.com homepage info - get ready to check Did Dots best content right away, or after learning these important things about diddots.com

Visit diddots.com

Key Findings

We analyzed Diddots.com page load time and found that the first response time was 1 sec and then it took 8.2 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

diddots.com performance score

0

Network Requests Diagram

www.diddots.com

1045 ms

css

112 ms

css

123 ms

application-2e458b90b32997c5c50c40c186cd13b3.css

74 ms

rebel.css

425 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 6% of them (4 requests) were addressed to the original Diddots.com, 38% (26 requests) were made to Img-shoplineapp-com.s3.amazonaws.com and 13% (9 requests) were made to S3-ap-southeast-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (6 sec) relates to the external source Img-shoplineapp-com.s3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 975.9 kB (11%)

Content Size

8.9 MB

After Optimization

7.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 62.8 kB

  • Original 77.6 kB
  • After minification 66.3 kB
  • After compression 14.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 11.3 kB, which is 15% 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 62.8 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 378.6 kB

  • Original 8.1 MB
  • After minification 7.7 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. Did Dots images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 166.7 kB

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

CSS Optimization

-83%

Potential reduce by 367.8 kB

  • Original 445.6 kB
  • After minification 442.7 kB
  • After compression 77.9 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. Diddots.com needs all CSS files to be minified and compressed as it can save up to 367.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (22%)

Requests Now

59

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.diddots.com

www.diddots.com

1045 ms

css

css

112 ms

css

css

123 ms

application-2e458b90b32997c5c50c40c186cd13b3.css

application-2e458b90b32997c5c50c40c186cd13b3.css

74 ms

rebel.css

rebel.css

425 ms

currencies.js

currencies.js

95 ms

application-feba3982bba9496e47fe14937c83f025.js

application-feba3982bba9496e47fe14937c83f025.js

108 ms

rebel.barebone.css

rebel.barebone.css

565 ms

proxy

proxy

1877 ms

card_allpay.png

card_allpay.png

1155 ms

mixpanel-2.2.min.js

mixpanel-2.2.min.js

255 ms

analytics.js

analytics.js

171 ms

events

events

586 ms

cart

cart

393 ms

card_visa.png

card_visa.png

1008 ms

card_master.png

card_master.png

1005 ms

card_amex.png

card_amex.png

1005 ms

card_paypal.png

card_paypal.png

1010 ms

logo-powered-by-dark.png

logo-powered-by-dark.png

1011 ms

Y5xXVP_6Cj4

Y5xXVP_6Cj4

179 ms

large.jpg

large.jpg

1226 ms

~text

~text

282 ms

large.jpg

large.jpg

1192 ms

large.jpg

large.jpg

973 ms

large.jpg

large.jpg

1412 ms

large.jpg

large.jpg

1210 ms

large.jpg

large.jpg

1409 ms

large.jpg

large.jpg

1677 ms

large.jpg

large.jpg

2073 ms

large.jpg

large.jpg

1648 ms

large.png

large.png

1905 ms

large.png

large.png

2553 ms

large.jpg

large.jpg

2093 ms

large.png

large.png

2772 ms

large.jpg

large.jpg

2168 ms

large.jpg

large.jpg

2382 ms

large.jpg

large.jpg

2767 ms

large.jpg

large.jpg

2788 ms

original.png

original.png

2643 ms

original.png

original.png

3081 ms

original.png

original.png

2805 ms

original.png

original.png

2879 ms

original.png

original.png

4755 ms

original.png

original.png

5429 ms

original.png

original.png

4143 ms

original.png

original.png

4616 ms

original.png

original.png

5974 ms

arrow-left.png

arrow-left.png

1160 ms

arrow-right.png

arrow-right.png

1159 ms

loader2.gif

loader2.gif

1197 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

94 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

102 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

127 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

128 ms

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

127 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

44 ms

collect

collect

18 ms

~text

~text

154 ms

88 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

136 ms

www-embed-player.js

www-embed-player.js

162 ms

base.js

base.js

224 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

39 ms

ad_status.js

ad_status.js

75 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

25 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

24 ms

events

events

482 ms

nr-885.min.js

nr-885.min.js

16 ms

SEO Factors

diddots.com SEO score

0

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

diddots.com

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