Tools & Wizards About Us
predating.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 66

    SEO

    Google-friendlier than
    25% of websites

predating.com

Speed Dating Singles Events by Pre-Dating - Largest Speed Dating Service (90+ Cities) in the USA

Page Load Speed

1.3 sec in total

First Response

109 ms

Resources Loaded

1.1 sec

Page Rendered

128 ms

predating.com screenshot

About Website

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

Pre-Dating Speed Dating events for busy single professionals. The world's largest speed dating service with monthly events in over 90 cities.

Visit predating.com

Key Findings

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

Performance Metrics

predating.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

48/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value12,310 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

predating.com

109 ms

www.pre-dating.com

460 ms

predating_style.css

58 ms

plusone.js

67 ms

jquery-latest.js

30 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Predating.com, 53% (41 requests) were made to Pre-dating.com and 10% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (478 ms) relates to the external source Pre-dating.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 427.5 kB (58%)

Content Size

736.9 kB

After Optimization

309.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 79.1 kB

  • Original 107.1 kB
  • After minification 101.2 kB
  • After compression 28.1 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 79.1 kB or 74% of the original size.

Image Optimization

-23%

Potential reduce by 23.9 kB

  • Original 102.8 kB
  • After minification 78.9 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, Pre Dating needs image optimization as it can save up to 23.9 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 322.9 kB

  • Original 524.8 kB
  • After minification 501.9 kB
  • After compression 201.9 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 322.9 kB or 62% of the original size.

CSS Optimization

-78%

Potential reduce by 1.6 kB

  • Original 2.1 kB
  • After minification 1.7 kB
  • After compression 465 B

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. Predating.com needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (71%)

Requests Now

72

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

predating.com

predating.com

109 ms

www.pre-dating.com

www.pre-dating.com

460 ms

predating_style.css

predating_style.css

58 ms

plusone.js

plusone.js

67 ms

jquery-latest.js

jquery-latest.js

30 ms

jquery.validate.min.js

jquery.validate.min.js

91 ms

addthis_widget.js

addthis_widget.js

34 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

12 ms

conversion.js

conversion.js

72 ms

dc.js

dc.js

73 ms

all.js

all.js

69 ms

trans.gif

trans.gif

72 ms

header_left_outer.gif

header_left_outer.gif

73 ms

header_left_inner.gif

header_left_inner.gif

71 ms

cupid_predating_logo4.gif

cupid_predating_logo4.gif

148 ms

header_right_inner.gif

header_right_inner.gif

72 ms

header_right_outer.gif

header_right_outer.gif

74 ms

leftside_bg.gif

leftside_bg.gif

148 ms

leftside_topcurve.gif

leftside_topcurve.gif

147 ms

PDclockWslogoNoNEW-med.jpg

PDclockWslogoNoNEW-med.jpg

220 ms

predating-speed-dating-fun-r.gif

predating-speed-dating-fun-r.gif

220 ms

find_an_event2.gif

find_an_event2.gif

219 ms

find_an_event_arrow.gif

find_an_event_arrow.gif

228 ms

rightside_bg.gif

rightside_bg.gif

247 ms

rightside_topcurve.gif

rightside_topcurve.gif

247 ms

leftside2_bg.gif

leftside2_bg.gif

277 ms

leftside2_topcurve.gif

leftside2_topcurve.gif

276 ms

upcoming_events.gif

upcoming_events.gif

282 ms

Pre-DatingMap.jpg

Pre-DatingMap.jpg

406 ms

rightside2_bg.gif

rightside2_bg.gif

308 ms

rightside2_topcurve.gif

rightside2_topcurve.gif

319 ms

leftside2_btmcurve.gif

leftside2_btmcurve.gif

342 ms

rightside2_btmcurve.gif

rightside2_btmcurve.gif

343 ms

leftside2_btmcurve2.gif

leftside2_btmcurve2.gif

344 ms

rightside2_btmcurve2.gif

rightside2_btmcurve2.gif

365 ms

leftside3_bg.gif

leftside3_bg.gif

372 ms

leftside3_topcurve.gif

leftside3_topcurve.gif

386 ms

testimonials.gif

testimonials.gif

387 ms

testimonial_couple5.jpg

testimonial_couple5.jpg

430 ms

leftside3_btm_center2.gif

leftside3_btm_center2.gif

419 ms

be_notified.gif

be_notified.gif

425 ms

leftside3_btm_bg.gif

leftside3_btm_bg.gif

439 ms

leftside3_btmcurve2.gif

leftside3_btmcurve2.gif

441 ms

leftside3_btm_center.gif

leftside3_btm_center.gif

463 ms

rightside3_btm_bg.gif

rightside3_btm_bg.gif

470 ms

rightside3_btmcurve2.gif

rightside3_btmcurve2.gif

478 ms

WRe0.js

WRe0.js

62 ms

113 ms

113 ms

rightside3_bg.gif

rightside3_bg.gif

468 ms

__utm.gif

__utm.gif

75 ms

131 ms

rightside3_topcurve.gif

rightside3_topcurve.gif

430 ms

leftside3_btmcurve.gif

leftside3_btmcurve.gif

429 ms

rightside3_btmcurve.gif

rightside3_btmcurve.gif

450 ms

xd_arbiter.php

xd_arbiter.php

72 ms

xd_arbiter.php

xd_arbiter.php

124 ms

monitor2.aspx

monitor2.aspx

174 ms

300lo.json

300lo.json

106 ms

counter.5524cceca805eb4b9b2b.js

counter.5524cceca805eb4b9b2b.js

78 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

68 ms

fastbutton

fastbutton

116 ms

92 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

59 ms

like.php

like.php

49 ms

shares.json

shares.json

18 ms

postmessageRelay

postmessageRelay

74 ms

94 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

87 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

87 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

38 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

38 ms

80 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

80 ms

monitor2.js

monitor2.js

28 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

49 ms

rpc:shindig_random.js

rpc:shindig_random.js

39 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

Accessibility Review

predating.com accessibility score

71

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

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

Best Practices

predating.com best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

predating.com SEO score

66

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Predating.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 Predating.com main page’s claimed encoding is iso-8859-1. 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

predating.com

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