1.7 sec in total
229 ms
1.3 sec
264 ms
Click here to check amazing My Match content for United States. Otherwise, check out these important facts you probably never knew about my.match.com
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 my.match.comWe analyzed My.match.com page load time and found that the first response time was 229 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
my.match.com performance score
name
value
score
weighting
Value3.2 s
45/100
10%
Value5.9 s
15/100
25%
Value4.8 s
67/100
10%
Value970 ms
29/100
30%
Value0.076
95/100
15%
Value6.9 s
54/100
10%
229 ms
73 ms
70 ms
143 ms
129 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 18% of them (12 requests) were addressed to the original My.match.com, 40% (26 requests) were made to Images.match.com and 6% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (535 ms) relates to the external source Sp.analytics.yahoo.com.
Page size can be reduced by 211.6 kB (35%)
611.6 kB
399.9 kB
In fact, the total size of My.match.com main page is 611.6 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. 45% of websites need less resources to load. Images take 301.7 kB which makes up the majority of the site volume.
Potential reduce by 39.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. 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 39.2 kB or 79% of the original size.
Potential reduce by 12.6 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. My Match images are well optimized though.
Potential reduce by 139.1 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 139.1 kB or 60% of the original size.
Potential reduce by 20.8 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. My.match.com needs all CSS files to be minified and compressed as it can save up to 20.8 kB or 77% of the original size.
Number of requests can be reduced by 30 (48%)
62
32
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My 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 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
my.match.com
229 ms
current.min.js
73 ms
match.min.js
70 ms
adrum.js
143 ms
core.js
129 ms
main.css
67 ms
match_enhanced.min.cssx
64 ms
intl-core.css
65 ms
screen.min.css
128 ms
css
131 ms
index_control.css
201 ms
conversion.js
307 ms
jquery.customSelect.min.js
112 ms
index.js
187 ms
fbds.js
203 ms
activityi;src=4707600;type=invmedia;cat=8omy2yjy;ord=7490674569271.505
354 ms
bg-site.jpg
132 ms
lb
258 ms
Matchcom_Landing_0611
276 ms
beacon
270 ms
spp.pl
535 ms
spotlight200_18033.jpg
65 ms
spotlight200_17823.jpg
64 ms
spotlight200_17973.jpg
63 ms
spotlight200_18013.jpg
63 ms
spotlight200_17907.jpg
63 ms
spotlight200_17919.jpg
255 ms
spotlight200_18005.jpg
268 ms
spotlight200_17902.jpg
265 ms
spotlight200_17929.jpg
265 ms
spotlight200_17967.jpg
266 ms
spotlight200_17917.jpg
263 ms
spotlight200_17915.jpg
269 ms
spotlight200_18043.jpg
276 ms
spotlight200_17940.jpg
277 ms
spotlight200_17990.jpg
303 ms
spotlight200_17969.jpg
274 ms
spotlight200_17836.jpg
276 ms
spotlight200_17955.jpg
274 ms
spotlight200_18019.jpg
296 ms
spotlight200_18007.jpg
296 ms
spotlight200_17827.jpg
298 ms
spotlight200_17821.jpg
297 ms
spotlight200_17972.jpg
296 ms
spotlight200_17904.jpg
487 ms
lb
247 ms
lb
248 ms
MatchIconFont-Regular_V3.woff
289 ms
290 ms
siteIcons.png
471 ms
274 ms
480 ms
quant.js
243 ms
pand.retargeting;dc_seg=30885130;ord=4377061270643.026
230 ms
ga.js
227 ms
ajaxGeo.js
126 ms
cs-drop.png
100 ms
mapuid
224 ms
pixel;r=1618598118;a=p-kRQnYzW_0gqbU;labels=_fp.event.Homepage;fpan=1;fpa=P0-1488738880-1458143918228;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458143918227;tzo=-180;ref=;url=http%3A%2F%2Fmy.match.com%2F;ogl=
190 ms
__utm.gif
122 ms
106 ms
129 ms
4 ms
4 ms
adrum-ext.ca98cd9e9bc9be02e16c4d7fb16dbb51.js
7 ms
my.match.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
my.match.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Uses deprecated APIs
Page has valid source maps
my.match.com SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My.match.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 My.match.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.
my.match.com
Open Graph description is not detected on the main page of My 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: