Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

matchmaker.fm

MatchMaker.fm - Connecting podcasters with great guests

Page Load Speed

2.7 sec in total

First Response

82 ms

Resources Loaded

544 ms

Page Rendered

2.1 sec

matchmaker.fm screenshot

About Website

Visit matchmaker.fm now to see the best up-to-date Match Maker content for United States and also check out these interesting facts you probably never knew about matchmaker.fm

Find podcast guests to interview & get booked on podcasts for more exposure. Join MatchMaker for free and search thousands of podcasters & guests today.

Visit matchmaker.fm

Key Findings

We analyzed Matchmaker.fm page load time and found that the first response time was 82 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

matchmaker.fm performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value2,530 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

www.matchmaker.fm

82 ms

LDGea2en30lUDdVMIrLSivNWn9E.js

22 ms

normalize.css

52 ms

webflow.css

47 ms

mm-marketing-staging.webflow.css

43 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 83% of them (63 requests) were addressed to the original Matchmaker.fm, 4% (3 requests) were made to Fast.wistia.com and 3% (2 requests) were made to D3e54v103j8qbb.cloudfront.net. The less responsive or slowest element that took the longest time to load (215 ms) belongs to the original domain Matchmaker.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.7 kB (9%)

Content Size

1.1 MB

After Optimization

964.4 kB

In fact, the total size of Matchmaker.fm main page is 1.1 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. 70% of websites need less resources to load. Images take 608.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 95.5 kB

  • Original 120.1 kB
  • After minification 105.7 kB
  • After compression 24.5 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 14.4 kB, which is 12% 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 95.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 362 B

  • Original 608.1 kB
  • After minification 607.7 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 Maker images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 266 B

  • Original 314.2 kB
  • After minification 314.2 kB
  • After compression 313.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

-20%

Potential reduce by 4.5 kB

  • Original 22.8 kB
  • After minification 22.0 kB
  • After compression 18.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. Matchmaker.fm needs all CSS files to be minified and compressed as it can save up to 4.5 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (50%)

Requests Now

66

After Optimization

33

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

Accessibility Review

matchmaker.fm accessibility score

92

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

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

matchmaker.fm 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

matchmaker.fm SEO score

92

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 uses 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 Matchmaker.fm 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 Matchmaker.fm 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

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