Tools & Wizards About Us
za.60singlesdating.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

za.60singlesdating.com

60 Singles Dating | Dating for 60+ single men and women in South Africa

Page Load Speed

6.3 sec in total

First Response

1.9 sec

Resources Loaded

4.2 sec

Page Rendered

131 ms

za.60singlesdating.com screenshot

About Website

Welcome to za.60singlesdating.com homepage info - get ready to check Za 60 Singles Dating best content right away, or after learning these important things about za.60singlesdating.com

Meet 1000's of single men and women over the age of 60 online in South Africa. Register for free and meet somebody special today.

Visit za.60singlesdating.com

Key Findings

We analyzed Za.60singlesdating.com page load time and found that the first response time was 1.9 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

za.60singlesdating.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

za.60singlesdating.com

1934 ms

style.css

628 ms

popup.js

631 ms

siteid%7C19544_limit%7C8_amin%7C58_amax%7C75

1847 ms

widgets.js

83 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 54% of them (27 requests) were addressed to the original Za.60singlesdating.com, 6% (3 requests) were made to Platform.twitter.com and 6% (3 requests) were made to S6.wldcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Za.60singlesdating.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.1 kB (29%)

Content Size

207.0 kB

After Optimization

147.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Za.60singlesdating.com main page is 207.0 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. 40% of websites need less resources to load. Images take 118.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 31.2 kB

  • Original 39.4 kB
  • After minification 34.0 kB
  • After compression 8.2 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 5.4 kB, which is 14% 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 31.2 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 2.2 kB

  • Original 118.1 kB
  • After minification 115.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. Za 60 Singles Dating images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 4.8 kB

  • Original 23.6 kB
  • After minification 23.5 kB
  • After compression 18.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 4.8 kB or 20% of the original size.

CSS Optimization

-81%

Potential reduce by 20.9 kB

  • Original 25.9 kB
  • After minification 21.6 kB
  • After compression 4.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. Za.60singlesdating.com needs all CSS files to be minified and compressed as it can save up to 20.9 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

49

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Za 60 Singles 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 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

za.60singlesdating.com

za.60singlesdating.com

1934 ms

style.css

style.css

628 ms

popup.js

popup.js

631 ms

siteid%7C19544_limit%7C8_amin%7C58_amax%7C75

siteid%7C19544_limit%7C8_amin%7C58_amax%7C75

1847 ms

widgets.js

widgets.js

83 ms

wld.facebook.connect.min.js

wld.facebook.connect.min.js

10 ms

reset.css

reset.css

491 ms

default.css

default.css

508 ms

but_login_small.gif

but_login_small.gif

201 ms

splash_60_1.jpg

splash_60_1.jpg

406 ms

logo_60_singles_dating_com.gif

logo_60_singles_dating_com.gif

208 ms

but_reg.png

but_reg.png

209 ms

tickbox.png

tickbox.png

210 ms

bg_block_bot_blue.gif

bg_block_bot_blue.gif

211 ms

footer_logo_60_singles_dating_com.gif

footer_logo_60_singles_dating_com.gif

400 ms

20_fl.gif

20_fl.gif

410 ms

30_fl.gif

30_fl.gif

410 ms

40_fl.gif

40_fl.gif

411 ms

50_fl.gif

50_fl.gif

413 ms

60_fl.gif

60_fl.gif

604 ms

square.jpg

square.jpg

254 ms

square.jpg

square.jpg

248 ms

square.jpg

square.jpg

32 ms

square.jpg

square.jpg

241 ms

square.jpg

square.jpg

234 ms

bg_block_wbg_blue.gif

bg_block_wbg_blue.gif

211 ms

but_search.png

but_search.png

204 ms

flag_au_1.png

flag_au_1.png

208 ms

flag_ca_1.png

flag_ca_1.png

209 ms

flag_ie_1.png

flag_ie_1.png

207 ms

flag_nz_1.png

flag_nz_1.png

225 ms

flag_za_1.png

flag_za_1.png

408 ms

flag_us_1.png

flag_us_1.png

403 ms

flag_uk_1.png

flag_uk_1.png

408 ms

square.jpg

square.jpg

51 ms

square.jpg

square.jpg

373 ms

square.jpg

square.jpg

51 ms

but_taf.png

but_taf.png

390 ms

ga.js

ga.js

7 ms

all.js

all.js

26 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

135 ms

__utm.gif

__utm.gif

34 ms

like.php

like.php

203 ms

230 ms

xd_arbiter.php

xd_arbiter.php

28 ms

xd_arbiter.php

xd_arbiter.php

34 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

43 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

37 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

26 ms

jot

jot

94 ms

Accessibility Review

za.60singlesdating.com accessibility score

64

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

za.60singlesdating.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

za.60singlesdating.com SEO score

77

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

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 Za.60singlesdating.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 Za.60singlesdating.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

za.60singlesdating.com

Open Graph description is not detected on the main page of Za 60 Singles 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: