Tools & Wizards About Us
performancedating.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

performancedating.com

Buy Domains - performancedating.com is for sale!

Page Load Speed

2 sec in total

First Response

263 ms

Resources Loaded

1.5 sec

Page Rendered

230 ms

performancedating.com screenshot

About Website

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

Buy a domain and see how a premium domain can be the best investment. Your business starts here. Buy a domain today.

Visit performancedating.com

Key Findings

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

Performance Metrics

performancedating.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.19

64/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

performancedating.com

263 ms

monetate.js

218 ms

application.css

45 ms

ng-modal.css

34 ms

angular.min.js

46 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Performancedating.com, 5% (5 requests) were made to Gstatic.com and 5% (5 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (391 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 781.8 kB (67%)

Content Size

1.2 MB

After Optimization

382.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Performancedating.com main page is 1.2 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. Javascripts take 934.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 30.4 kB

  • Original 40.0 kB
  • After minification 38.8 kB
  • After compression 9.7 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 30.4 kB or 76% of the original size.

Image Optimization

-11%

Potential reduce by 3.5 kB

  • Original 30.3 kB
  • After minification 26.8 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. Obviously, Performancedating needs image optimization as it can save up to 3.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 617.7 kB

  • Original 934.2 kB
  • After minification 906.2 kB
  • After compression 316.6 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 617.7 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 130.3 kB

  • Original 159.7 kB
  • After minification 158.2 kB
  • After compression 29.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. Performancedating.com needs all CSS files to be minified and compressed as it can save up to 130.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (72%)

Requests Now

89

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

performancedating.com

performancedating.com

263 ms

monetate.js

monetate.js

218 ms

application.css

application.css

45 ms

ng-modal.css

ng-modal.css

34 ms

angular.min.js

angular.min.js

46 ms

ng-modal.js

ng-modal.js

33 ms

google_analytics.js

google_analytics.js

33 ms

google_oauth.js

google_oauth.js

31 ms

bold_chat.js

bold_chat.js

37 ms

eloqua.js

eloqua.js

36 ms

hotjar.js

hotjar.js

37 ms

adroll.js

adroll.js

36 ms

impactRadius.js

impactRadius.js

39 ms

in.js

in.js

137 ms

api.js

api.js

57 ms

api:client.js

api:client.js

65 ms

app.js

app.js

37 ms

cookies.js

cookies.js

153 ms

socialMedia.js

socialMedia.js

37 ms

countryDropdown.js

countryDropdown.js

39 ms

monetate.js

monetate.js

38 ms

index.js

index.js

39 ms

lander.js

lander.js

49 ms

seoPages.js

seoPages.js

51 ms

sitePages.js

sitePages.js

52 ms

search.js

search.js

51 ms

modal.js

modal.js

50 ms

forms.js

forms.js

51 ms

tldSelector.js

tldSelector.js

52 ms

setFixedTop.js

setFixedTop.js

52 ms

searchBar.js

searchBar.js

52 ms

currency.js

currency.js

52 ms

trust.js

trust.js

53 ms

conversion.js

conversion.js

46 ms

tdfs-inner.css

tdfs-inner.css

53 ms

tdfs-temp.css

tdfs-temp.css

52 ms

thankyou.css

thankyou.css

53 ms

entry.js

entry.js

9 ms

custom.js

custom.js

12 ms

css

css

31 ms

fontawesome.min.css

fontawesome.min.css

22 ms

bd-icons.min.css

bd-icons.min.css

11 ms

ga.js

ga.js

50 ms

foundation-A136666-2811-40ba-bff2-3df3af8bc2ae1.min.js

foundation-A136666-2811-40ba-bff2-3df3af8bc2ae1.min.js

49 ms

userspace

userspace

321 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

170 ms

recaptcha__en.js

recaptcha__en.js

353 ms

all.js

all.js

391 ms

333 ms

logo-header-2x.png

logo-header-2x.png

271 ms

841983459-0

841983459-0

288 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

208 ms

259 ms

hotjar-10205.js

hotjar-10205.js

180 ms

elqCfg.min.js

elqCfg.min.js

157 ms

bg-main-hilight-fade.jpg

bg-main-hilight-fade.jpg

139 ms

bg-select.png

bg-select.png

139 ms

bg-target-bd-icon.png

bg-target-bd-icon.png

138 ms

__utm.gif

__utm.gif

158 ms

foundation-tags-SD780-3f5b-4f28-957f-6e6dc25a7fc41.min.js

foundation-tags-SD780-3f5b-4f28-957f-6e6dc25a7fc41.min.js

71 ms

postmessageRelay

postmessageRelay

135 ms

__utm.gif

__utm.gif

98 ms

__utm.gif

__utm.gif

99 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

53 ms

svrGP

svrGP

122 ms

framework

framework

111 ms

iframe

iframe

111 ms

modules-043c1e6abe660c48857202e419ff9d8a.js

modules-043c1e6abe660c48857202e419ff9d8a.js

106 ms

841983459-1

841983459-1

57 ms

73 ms

__utm.gif

__utm.gif

40 ms

collect

collect

106 ms

svrGP.aspx

svrGP.aspx

67 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

69 ms

rpc:shindig_random.js

rpc:shindig_random.js

62 ms

1233565733-idpiframe.js

1233565733-idpiframe.js

74 ms

159 ms

xd_arbiter.php

xd_arbiter.php

146 ms

xd_arbiter.php

xd_arbiter.php

292 ms

svrGP.aspx

svrGP.aspx

58 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

12 ms

iframerpc

iframerpc

27 ms

vms.js

vms.js

92 ms

fallback

fallback

34 ms

roundtrip.js

roundtrip.js

15 ms

fallback__ltr.css

fallback__ltr.css

14 ms

payload

payload

20 ms

css

css

71 ms

542IK7HHBBFJJFENPFA7WX.js

542IK7HHBBFJJFENPFA7WX.js

163 ms

xd_arbiter.php

xd_arbiter.php

85 ms

bc.pv

bc.pv

82 ms

logo_48.png

logo_48.png

4 ms

refresh.png

refresh.png

3 ms

audio.png

audio.png

8 ms

Accessibility Review

performancedating.com accessibility score

96

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

performancedating.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

performancedating.com SEO score

84

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

High

Page is blocked from indexing

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

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

performancedating.com

Open Graph data is detected on the main page of Performancedating. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: