Tools & Wizards About Us
match21.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

Page Load Speed

3.4 sec in total

First Response

585 ms

Resources Loaded

2.4 sec

Page Rendered

495 ms

match21.com screenshot

About Website

Click here to check amazing Match21 content. Otherwise, check out these important facts you probably never knew about match21.com

Visit match21.com

Key Findings

We analyzed Match21.com page load time and found that the first response time was 585 ms and then it took 2.9 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

match21.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

match21.com

585 ms

foundation.min.css

113 ms

index.common.css

742 ms

index.css

539 ms

df.js

522 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 58% of them (19 requests) were addressed to the original Match21.com, 24% (8 requests) were made to Galcdn.datingfactory.net and 9% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (742 ms) belongs to the original domain Match21.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.9 kB (31%)

Content Size

879.6 kB

After Optimization

605.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 37.1 kB

  • Original 49.4 kB
  • After minification 45.1 kB
  • After compression 12.3 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 37.1 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 4.7 kB

  • Original 493.1 kB
  • After minification 488.3 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. Match21 images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 220.7 kB

  • Original 323.9 kB
  • After minification 323.9 kB
  • After compression 103.2 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 220.7 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 11.4 kB

  • Original 13.2 kB
  • After minification 13.2 kB
  • After compression 1.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. Match21.com needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (39%)

Requests Now

31

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Match21. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

match21.com

match21.com

585 ms

foundation.min.css

foundation.min.css

113 ms

index.common.css

index.common.css

742 ms

index.css

index.css

539 ms

df.js

df.js

522 ms

theme.js

theme.js

261 ms

Index.js

Index.js

252 ms

modernizr.min.js

modernizr.min.js

250 ms

fastclick.min.js

fastclick.min.js

378 ms

css

css

139 ms

d454bf04ad6e5f1c23302822c3651365.png

d454bf04ad6e5f1c23302822c3651365.png

324 ms

logo.png

logo.png

110 ms

78fde06a8274e9144744c1d58dc6a282.png

78fde06a8274e9144744c1d58dc6a282.png

457 ms

69637848db2a2822c24fb8db93e45d29.png

69637848db2a2822c24fb8db93e45d29.png

345 ms

3eac541ab217bfd5723c4c534f598a07.png

3eac541ab217bfd5723c4c534f598a07.png

278 ms

fe2f0492018f4359f5d3e756cf47fd0e.png

fe2f0492018f4359f5d3e756cf47fd0e.png

301 ms

f86223f0daad1d93060e4426ed1a9dbb.png

f86223f0daad1d93060e4426ed1a9dbb.png

369 ms

425ec4fccc5d251a3bd5552cc05c9852.png

425ec4fccc5d251a3bd5552cc05c9852.png

406 ms

15bbc3e696f0290f66b3a35454762c3b.png

15bbc3e696f0290f66b3a35454762c3b.png

454 ms

SwitchLocale.js

SwitchLocale.js

112 ms

selector_arrow_bottom.gif

selector_arrow_bottom.gif

135 ms

visual.jpg

visual.jpg

541 ms

RegistrationSimple.js

RegistrationSimple.js

132 ms

jquery.select.behavior.js

jquery.select.behavior.js

114 ms

bgreg.png

bgreg.png

248 ms

ico_warning.gif

ico_warning.gif

248 ms

icon_auth.png

icon_auth.png

249 ms

providers.gif

providers.gif

249 ms

ga.js

ga.js

47 ms

__utm.gif

__utm.gif

30 ms

__utm.gif

__utm.gif

64 ms

ajs.php

ajs.php

296 ms

collect

collect

214 ms

Accessibility Review

match21.com accessibility score

65

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Form elements do not have associated labels

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

match21.com SEO score

83

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Match21.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Match21.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

match21.com

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