Tools & Wizards About Us
match.com.au screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

match.com.au

Match® | The leading dating app for singles. Find better matches.

Page Load Speed

888 ms in total

First Response

99 ms

Resources Loaded

662 ms

Page Rendered

127 ms

match.com.au screenshot

About Website

Visit match.com.au now to see the best up-to-date Match content for Australia and also check out these interesting facts you probably never knew about match.com.au

Match.com is the number one destination for online dating with more dates, more relationships, & more marriages than any other dating or personals site.

Visit match.com.au

Key Findings

We analyzed Match.com.au page load time and found that the first response time was 99 ms and then it took 789 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

match.com.au performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

match.com.au

99 ms

au.match.com

215 ms

polyfills-c67a75d1b6f99dc8.js

49 ms

4630-a86731fcccfbc53a.js

122 ms

672-62fb85c916d45b5c.js

179 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Match.com.au, 75% (27 requests) were made to Au.match.com and 22% (8 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (307 ms) relates to the external source Au.match.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.1 kB (30%)

Content Size

519.2 kB

After Optimization

363.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Match.com.au main page is 519.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. 50% of websites need less resources to load. Images take 210.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 148.5 kB

  • Original 179.3 kB
  • After minification 179.3 kB
  • After compression 30.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. 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 148.5 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 7.4 kB

  • Original 210.5 kB
  • After minification 203.1 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. Match images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 45 B

  • Original 125.0 kB
  • After minification 125.0 kB
  • After compression 124.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 52 B

  • Original 4.4 kB
  • After minification 4.4 kB
  • After compression 4.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. Match.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (76%)

Requests Now

34

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

match.com.au

match.com.au

99 ms

au.match.com

au.match.com

215 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

49 ms

4630-a86731fcccfbc53a.js

4630-a86731fcccfbc53a.js

122 ms

672-62fb85c916d45b5c.js

672-62fb85c916d45b5c.js

179 ms

6598-e66977003ad6bfe9.js

6598-e66977003ad6bfe9.js

118 ms

6884-5d3707ef3ca6275c.js

6884-5d3707ef3ca6275c.js

151 ms

1268-7c64e433893e790e.js

1268-7c64e433893e790e.js

117 ms

76-5fa7490a80c13a25.js

76-5fa7490a80c13a25.js

111 ms

7014-e19b1d3453363d51.js

7014-e19b1d3453363d51.js

192 ms

3613-0e0afe25f278fd21.js

3613-0e0afe25f278fd21.js

158 ms

7346.269c11319a764663.js

7346.269c11319a764663.js

159 ms

8729-0b923ad7d10d63f6.js

8729-0b923ad7d10d63f6.js

160 ms

134-f1b6770e9ee946ae.js

134-f1b6770e9ee946ae.js

195 ms

1064.5108a27b0d87ba4d.js

1064.5108a27b0d87ba4d.js

199 ms

webpack-3792630cb27609e9.js

webpack-3792630cb27609e9.js

199 ms

framework-4ed89e9640adfb9e.js

framework-4ed89e9640adfb9e.js

206 ms

main-efc647ed83eba299.js

main-efc647ed83eba299.js

220 ms

_app-93b13139eb67da1e.js

_app-93b13139eb67da1e.js

244 ms

2003-00cbbf145c47ae99.js

2003-00cbbf145c47ae99.js

243 ms

4470-45d9c10320a03c57.js

4470-45d9c10320a03c57.js

254 ms

5279-8dcb6fda9596923b.js

5279-8dcb6fda9596923b.js

245 ms

en-au-f1a5b9f27506441c.js

en-au-f1a5b9f27506441c.js

258 ms

_buildManifest.js

_buildManifest.js

278 ms

_ssgManifest.js

_ssgManifest.js

279 ms

otSDKStub.js

otSDKStub.js

26 ms

7f436592-82ea-4d50-a34d-85e80f2a608d.json

7f436592-82ea-4d50-a34d-85e80f2a608d.json

32 ms

en-desktop-landing-2a78516e8c0aed13202930721f552d8a.jpg

en-desktop-landing-2a78516e8c0aed13202930721f552d8a.jpg

307 ms

theme-logo-e93621da86fe4901427fe6f5c3e331d4.svg

theme-logo-e93621da86fe4901427fe6f5c3e331d4.svg

263 ms

carat-down-3489a7fe030858aa232d0427294df251.png

carat-down-3489a7fe030858aa232d0427294df251.png

264 ms

otBannerSdk.js

otBannerSdk.js

20 ms

en.json

en.json

28 ms

otCenterRounded.json

otCenterRounded.json

132 ms

otPcCenter.json

otPcCenter.json

111 ms

otCommonStyles.css

otCommonStyles.css

129 ms

ot_logo.png

ot_logo.png

19 ms

Accessibility Review

match.com.au accessibility score

89

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Best Practices

match.com.au 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

SEO Factors

match.com.au SEO score

83

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

Links do not have descriptive text

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

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 Match.com.au 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 Match.com.au 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

match.com.au

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