Tools & Wizards About Us
matchmaker.fm screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

matchmaker.fm

MatchMaker.fm - Connecting podcasters with great guests

Page Load Speed

2.3 sec in total

First Response

31 ms

Resources Loaded

623 ms

Page Rendered

1.6 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 31 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% 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.5 s

36/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value2,850 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

matchmaker.fm

31 ms

www.matchmaker.fm

106 ms

normalize.css

26 ms

webflow.css

53 ms

matchmakerfm24.webflow.css

50 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 89% of them (62 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 (280 ms) belongs to the original domain Matchmaker.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.3 kB (24%)

Content Size

394.2 kB

After Optimization

298.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 90.7 kB

  • Original 113.6 kB
  • After minification 99.7 kB
  • After compression 23.0 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 13.9 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 90.7 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 362 B

  • Original 4.4 kB
  • After minification 4.0 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 29 B

  • Original 255.4 kB
  • After minification 255.4 kB
  • After compression 255.4 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

-21%

Potential reduce by 4.3 kB

  • Original 20.8 kB
  • After minification 20.0 kB
  • After compression 16.5 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.3 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (67%)

Requests Now

45

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 45 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 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

matchmaker.fm

matchmaker.fm

31 ms

www.matchmaker.fm

www.matchmaker.fm

106 ms

normalize.css

normalize.css

26 ms

webflow.css

webflow.css

53 ms

matchmakerfm24.webflow.css

matchmakerfm24.webflow.css

50 ms

mm_logo_full.svg

mm_logo_full.svg

121 ms

SymbolColourLight.svg

SymbolColourLight.svg

38 ms

menu.svg

menu.svg

116 ms

rocket-loader.min.js

rocket-loader.min.js

61 ms

em423axju9.jsonp

em423axju9.jsonp

148 ms

email-decode.min.js

email-decode.min.js

59 ms

jquery-3.5.1.min.dc5e7f18c8.js

jquery-3.5.1.min.dc5e7f18c8.js

155 ms

webflow.js

webflow.js

144 ms

E-v1.js

E-v1.js

187 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

139 ms

tradies_success_1tradies_success.webp

tradies_success_1tradies_success.webp

134 ms

allen_lycka_1allen_lycka.webp

allen_lycka_1allen_lycka.webp

137 ms

lost_spaces_1lost_spaces.webp

lost_spaces_1lost_spaces.webp

135 ms

embodied_1embodied.webp

embodied_1embodied.webp

136 ms

avigail_gimpel_1avigail_gimpel.webp

avigail_gimpel_1avigail_gimpel.webp

120 ms

ready_to_fly_1ready_to_fly.webp

ready_to_fly_1ready_to_fly.webp

234 ms

marie_antoinette_1marie_antoinette.webp

marie_antoinette_1marie_antoinette.webp

186 ms

affiliation-logo-telemundo.svg

affiliation-logo-telemundo.svg

156 ms

affiliation-logo-nbc.svg

affiliation-logo-nbc.svg

151 ms

affiliation-logo-mw.svg

affiliation-logo-mw.svg

159 ms

affiliation-logo-cbs.svg

affiliation-logo-cbs.svg

162 ms

affiliation-logo-fox.svg

affiliation-logo-fox.svg

182 ms

affiliation-logo-abc.svg

affiliation-logo-abc.svg

179 ms

swatch

swatch

123 ms

matched_1matched.webp

matched_1matched.webp

196 ms

faves.svg

faves.svg

268 ms

community.svg

community.svg

198 ms

message.svg

message.svg

196 ms

forShows_1.avif

forShows_1.avif

200 ms

podcaster_search.svg

podcaster_search.svg

273 ms

podcaster_grow.svg

podcaster_grow.svg

267 ms

podcaster_discover.svg

podcaster_discover.svg

269 ms

collab.svg

collab.svg

270 ms

Group-11.svg

Group-11.svg

274 ms

hiw_Guestprofile_1.avif

hiw_Guestprofile_1.avif

273 ms

search.svg

search.svg

275 ms

hiw_match_1.avif

hiw_match_1.avif

272 ms

hiw_inbox_1.avif

hiw_inbox_1.avif

277 ms

home_pro_1.avif

home_pro_1.avif

276 ms

video.svg

video.svg

277 ms

rec.svg

rec.svg

280 ms

booking.svg

booking.svg

279 ms

fbevents.js

fbevents.js

123 ms

gtm.js

gtm.js

179 ms

mobile-app.svg

mobile-app.svg

224 ms

faq.svg

faq.svg

224 ms

Cross-icon.svg

Cross-icon.svg

223 ms

JayFranze_1JayFranze.avif

JayFranze_1JayFranze.avif

221 ms

deadbird_tweets.svg

deadbird_tweets.svg

200 ms

KyleSpyrides_1KyleSpyrides.avif

KyleSpyrides_1KyleSpyrides.avif

195 ms

DominicONorton_1DominicONorton.avif

DominicONorton_1DominicONorton.avif

202 ms

TerriNakamura_1TerriNakamura.avif

TerriNakamura_1TerriNakamura.avif

199 ms

DaisyPaigeUM322_1DaisyPaigeUM322.avif

DaisyPaigeUM322_1DaisyPaigeUM322.avif

209 ms

CindyJuddBurns_1CindyJuddBurns.avif

CindyJuddBurns_1CindyJuddBurns.avif

205 ms

Matt_LeBris_1Matt_LeBris.avif

Matt_LeBris_1Matt_LeBris.avif

203 ms

RonnieNoize_1RonnieNoize.avif

RonnieNoize_1RonnieNoize.avif

200 ms

cta_img_1.avif

cta_img_1.avif

199 ms

Group-64.svg

Group-64.svg

207 ms

mm-logo-light.svg

mm-logo-light.svg

198 ms

googleplay.svg

googleplay.svg

194 ms

appstore.svg

appstore.svg

153 ms

deadbird_footer.svg

deadbird_footer.svg

153 ms

mm_tt_1mm_tt.png

mm_tt_1mm_tt.png

153 ms

mm_ig_1mm_ig.avif

mm_ig_1mm_ig.avif

161 ms

jquery-3.5.1.min.dc5e7f18c8.js

jquery-3.5.1.min.dc5e7f18c8.js

5 ms

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

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

matchmaker.fm SEO score

91

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

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

matchmaker.fm

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: