Tools & Wizards About Us
datingdr.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

datingdr.com

Reviewing Dating Programs and Systems — My HONEST Reviews on the top-selling Dating Guides

Page Load Speed

3.2 sec in total

First Response

134 ms

Resources Loaded

2.8 sec

Page Rendered

260 ms

datingdr.com screenshot

About Website

Visit datingdr.com now to see the best up-to-date Dating Dr content and also check out these interesting facts you probably never knew about datingdr.com

Reviewing the best dating books, courses, and programs and giving our honest opinions. Check out our Dating advice, tips and Reviews

Visit datingdr.com

Key Findings

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

Performance Metrics

datingdr.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

datingdr.com

134 ms

bY3hCsMgDIRfqCHt_mxvU0QzK1gVExm-_dS2bIz9SXJ3H5cZZSN2vC6PG7JUT9P8benCEnf0qsYif6NjTQtWElAhNiJDJq-EDKTIwpB8sS4c9fhyxpI0XqskelOomc_PzYtBlBZ4xrzDHV3QvhjiD8O_0Nndga7Xq8k4a6GPEfVjOCN-Aw.css

40 ms

M9QvL9BNTixJTc8vqtQtyC8uKdbNySwu0S8uSSzJTNZPLi6GqgAL65ZkpOamAgA.css

46 ms

lctbCsAgDETRDTWISwo-Q61KJlC6-0rpBvy5H8Mc7-5JgS2VoQ_NAQM1gTkYmwQXgP_xzSul2uE3VWQ9t1ER7qujRcqCuu05qmQj6RQ18YUX.css

46 ms

styles.css

1855 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 24% of them (13 requests) were addressed to the original Datingdr.com, 22% (12 requests) were made to Apis.google.com and 13% (7 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Datingdr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.4 kB (62%)

Content Size

419.2 kB

After Optimization

157.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Datingdr.com main page is 419.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. 55% of websites need less resources to load. Javascripts take 218.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 85.6 kB

  • Original 108.5 kB
  • After minification 107.2 kB
  • After compression 22.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 85.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 45 B

  • Original 51.3 kB
  • After minification 51.2 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. Dating Dr images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 142.9 kB

  • Original 218.3 kB
  • After minification 218.0 kB
  • After compression 75.4 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 142.9 kB or 65% of the original size.

CSS Optimization

-80%

Potential reduce by 32.9 kB

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

Requests Breakdown

Number of requests can be reduced by 23 (46%)

Requests Now

50

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

datingdr.com

datingdr.com

134 ms

bY3hCsMgDIRfqCHt_mxvU0QzK1gVExm-_dS2bIz9SXJ3H5cZZSN2vC6PG7JUT9P8benCEnf0qsYif6NjTQtWElAhNiJDJq-EDKTIwpB8sS4c9fhyxpI0XqskelOomc_PzYtBlBZ4xrzDHV3QvhjiD8O_0Nndga7Xq8k4a6GPEfVjOCN-Aw.css

bY3hCsMgDIRfqCHt_mxvU0QzK1gVExm-_dS2bIz9SXJ3H5cZZSN2vC6PG7JUT9P8benCEnf0qsYif6NjTQtWElAhNiJDJq-EDKTIwpB8sS4c9fhyxpI0XqskelOomc_PzYtBlBZ4xrzDHV3QvhjiD8O_0Nndga7Xq8k4a6GPEfVjOCN-Aw.css

40 ms

M9QvL9BNTixJTc8vqtQtyC8uKdbNySwu0S8uSSzJTNZPLi6GqgAL65ZkpOamAgA.css

M9QvL9BNTixJTc8vqtQtyC8uKdbNySwu0S8uSSzJTNZPLi6GqgAL65ZkpOamAgA.css

46 ms

lctbCsAgDETRDTWISwo-Q61KJlC6-0rpBvy5H8Mc7-5JgS2VoQ_NAQM1gTkYmwQXgP_xzSul2uE3VWQ9t1ER7qujRcqCuu05qmQj6RQ18YUX.css

lctbCsAgDETRDTWISwo-Q61KJlC6-0rpBvy5H8Mc7-5JgS2VoQ_NAQM1gTkYmwQXgP_xzSul2uE3VWQ9t1ER7qujRcqCuu05qmQj6RQ18YUX.css

46 ms

styles.css

styles.css

1855 ms

M9bPKixNLarUMYYydHMz04sSS1L1cjPzAA.js

M9bPKixNLarUMYYydHMz04sSS1L1cjPzAA.js

85 ms

FB.Share

FB.Share

12 ms

plusone.js

plusone.js

39 ms

widgets.js

widgets.js

14 ms

pinit.js

pinit.js

6 ms

M9RPzs8rSUwu0U3LL8rVNdfPzEvOKU1JLdbPAqLC0tSiSj2QjF5uZh4A.js

M9RPzs8rSUwu0U3LL8rVNdfPzEvOKU1JLdbPAqLC0tSiSj2QjF5uZh4A.js

65 ms

M9RPzs8rSUwu0U3LL8rVNdfPzEvOKU1JLdbPKtYvTi7KLCgpBgA.js

M9RPzs8rSUwu0U3LL8rVNdfPzEvOKU1JLdbPKtYvTi7KLCgpBgA.js

64 ms

e-201611.js

e-201611.js

14 ms

e-201611.js

e-201611.js

51 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

45 ms

icon-rss.gif

icon-rss.gif

46 ms

dot-ddd.gif

dot-ddd.gif

45 ms

Pandoras-Box-System.png

Pandoras-Box-System.png

76 ms

pandoras-box-3-questions.jpg

pandoras-box-3-questions.jpg

75 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

55 ms

158 ms

xd_arbiter.php

xd_arbiter.php

165 ms

xd_arbiter.php

xd_arbiter.php

320 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

5 ms

fastbutton

fastbutton

69 ms

pinit_main.js

pinit_main.js

266 ms

postmessageRelay

postmessageRelay

68 ms

fastbutton

fastbutton

83 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

79 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

79 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

78 ms

share_button.php

share_button.php

173 ms

fastbutton

fastbutton

147 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

120 ms

rpc:shindig_random.js

rpc:shindig_random.js

120 ms

fastbutton

fastbutton

123 ms

like.php

like.php

136 ms

like.php

like.php

126 ms

like.php

like.php

236 ms

g.gif

g.gif

71 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

168 ms

fastbutton

fastbutton

162 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

57 ms

like.php

like.php

141 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

369 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

415 ms

like.php

like.php

149 ms

count.json

count.json

185 ms

count.json

count.json

185 ms

count.json

count.json

187 ms

count.json

count.json

184 ms

count.json

count.json

185 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

36 ms

jot.html

jot.html

2 ms

Accessibility Review

datingdr.com accessibility score

67

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

datingdr.com best practices score

58

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

datingdr.com SEO score

69

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

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

datingdr.com

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