Tools & Wizards About Us
my-matchmaker.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

my-matchmaker.com

My Matchmaker : Select your International Medical Insurance

Page Load Speed

4.2 sec in total

First Response

252 ms

Resources Loaded

3.6 sec

Page Rendered

251 ms

my-matchmaker.com screenshot

About Website

Visit my-matchmaker.com now to see the best up-to-date My Matchmaker content and also check out these interesting facts you probably never knew about my-matchmaker.com

Choose the International Private Medical Insurance that's right for you with our unique online Selector tool

Visit my-matchmaker.com

Key Findings

We analyzed My-matchmaker.com page load time and found that the first response time was 252 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

my-matchmaker.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value18.7 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value1,370 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.126

83/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

my-matchmaker.com

252 ms

my-matchmaker.com

389 ms

987 ms

k2.css

14 ms

bootstrap.min.css

30 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 83% of them (83 requests) were addressed to the original My-matchmaker.com, 5% (5 requests) were made to Youtube.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (987 ms) belongs to the original domain My-matchmaker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 574.3 kB (22%)

Content Size

2.7 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of My-matchmaker.com main page is 2.7 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. Only a small number of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 69.3 kB

  • Original 84.2 kB
  • After minification 84.2 kB
  • After compression 14.9 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 69.3 kB or 82% of the original size.

Image Optimization

-14%

Potential reduce by 263.9 kB

  • Original 1.8 MB
  • After minification 1.6 MB

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. Obviously, My Matchmaker needs image optimization as it can save up to 263.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-38%

Potential reduce by 237.9 kB

  • Original 619.2 kB
  • After minification 619.2 kB
  • After compression 381.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 237.9 kB or 38% of the original size.

CSS Optimization

-2%

Potential reduce by 3.2 kB

  • Original 137.5 kB
  • After minification 137.5 kB
  • After compression 134.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. My-matchmaker.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

93

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

my-matchmaker.com

my-matchmaker.com

252 ms

my-matchmaker.com

my-matchmaker.com

389 ms

987 ms

k2.css

k2.css

14 ms

bootstrap.min.css

bootstrap.min.css

30 ms

grid-responsive.css

grid-responsive.css

45 ms

bootstrap-ie8.css

bootstrap-ie8.css

532 ms

master-f79a8c4af96e2bedb9893f1d2f0cd1c3.css

master-f79a8c4af96e2bedb9893f1d2f0cd1c3.css

37 ms

master-ie8.css

master-ie8.css

367 ms

demo-f79a8c4af96e2bedb9893f1d2f0cd1c3.css

demo-f79a8c4af96e2bedb9893f1d2f0cd1c3.css

25 ms

demo.css

demo.css

42 ms

mediaqueries.css

mediaqueries.css

44 ms

rt_anacron-custom.css

rt_anacron-custom.css

45 ms

btcontentslider.css

btcontentslider.css

44 ms

showcase.css

showcase.css

50 ms

style2.0.css

style2.0.css

61 ms

template.css

template.css

51 ms

mootools-core.js

mootools-core.js

61 ms

jquery.min.js

jquery.min.js

64 ms

jquery-noconflict.js

jquery-noconflict.js

74 ms

jquery-migrate.min.js

jquery-migrate.min.js

76 ms

core.js

core.js

74 ms

k2.js

k2.js

76 ms

caption.js

caption.js

83 ms

mootools-more.js

mootools-more.js

106 ms

bootstrap.min.js

bootstrap.min.js

87 ms

chart.js

chart.js

89 ms

gantry-totop.js

gantry-totop.js

92 ms

selectivizr-min.js

selectivizr-min.js

461 ms

browser-engines.js

browser-engines.js

103 ms

html5shim.js

html5shim.js

443 ms

canvas-unsupported.js

canvas-unsupported.js

460 ms

placeholder-ie.js

placeholder-ie.js

467 ms

rokmediaqueries.js

rokmediaqueries.js

378 ms

hammer.js

hammer.js

399 ms

slides.js

slides.js

419 ms

default.js

default.js

437 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

455 ms

getgeotrustsslseal

getgeotrustsslseal

5 ms

component.css

component.css

453 ms

normalize.css

normalize.css

453 ms

crawler.js

crawler.js

448 ms

mootools-mobile.js

mootools-mobile.js

547 ms

rokmediaqueries.js

rokmediaqueries.js

434 ms

roksprocket.js

roksprocket.js

437 ms

moofx.js

moofx.js

442 ms

features.js

features.js

446 ms

showcase.js

showcase.js

443 ms

jquery.simplemodal.js

jquery.simplemodal.js

447 ms

default.js

default.js

447 ms

jquery.cookie.js

jquery.cookie.js

450 ms

cookie.js

cookie.js

448 ms

modernizr.custom.js

modernizr.custom.js

441 ms

tooltip.js

tooltip.js

445 ms

app.js

app.js

442 ms

classie.js

classie.js

440 ms

gnmenu.js

gnmenu.js

447 ms

analytics.js

analytics.js

25 ms

mascotte_1.png

mascotte_1.png

107 ms

mascotte_3.png

mascotte_3.png

101 ms

mascotte_2.png

mascotte_2.png

102 ms

Logo_TransparentBackground.png

Logo_TransparentBackground.png

102 ms

Logo-mmm-alc.png

Logo-mmm-alc.png

18 ms

Logo-mmm-allianz.png

Logo-mmm-allianz.png

19 ms

Logo-mmm-cigna.png

Logo-mmm-cigna.png

106 ms

Logo-mmm-globality.png

Logo-mmm-globality.png

105 ms

Logo-mmm-now.png

Logo-mmm-now.png

505 ms

Logo_mmm_vumi.png

Logo_mmm_vumi.png

106 ms

logo_mmm_aetna.png

logo_mmm_aetna.png

106 ms

logo_mmm_aprilinternationalNB.png

logo_mmm_aprilinternationalNB.png

155 ms

logo_mmm_international.png

logo_mmm_international.png

154 ms

logo_mmm_msh.png

logo_mmm_msh.png

154 ms

b8292acafd72142128a3481ac4b0abff_XL.jpg

b8292acafd72142128a3481ac4b0abff_XL.jpg

156 ms

d6e7bc44feb1613d041d5385e5745b10_XL.jpg

d6e7bc44feb1613d041d5385e5745b10_XL.jpg

159 ms

FT_logo-05.png

FT_logo-05.png

160 ms

lato-light-webfont.woff

lato-light-webfont.woff

591 ms

all.js

all.js

94 ms

logo.svg

logo.svg

486 ms

piZYFcnJai0

piZYFcnJai0

166 ms

collect

collect

56 ms

yes.png

yes.png

61 ms

no.png

no.png

80 ms

consultation.png

consultation.png

412 ms

dentaire.png

dentaire.png

79 ms

maternite.png

maternite.png

87 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

609 ms

noise.png

noise.png

97 ms

widgets.js

widgets.js

67 ms

all.js

all.js

42 ms

cabin-semibold-webfont.woff

cabin-semibold-webfont.woff

593 ms

js

js

100 ms

31 ms

www-player.css

www-player.css

5 ms

www-embed-player.js

www-embed-player.js

23 ms

base.js

base.js

61 ms

ad_status.js

ad_status.js

131 ms

7ESZfzt6B-auShnY1KkIRp8yP8-UPE-sKM1mi9LhusY.js

7ESZfzt6B-auShnY1KkIRp8yP8-UPE-sKM1mi9LhusY.js

89 ms

embed.js

embed.js

31 ms

id

id

12 ms

Create

Create

77 ms

Accessibility Review

my-matchmaker.com accessibility score

52

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.

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 IDs are not unique

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

my-matchmaker.com best practices score

67

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

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

my-matchmaker.com SEO score

76

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

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My-matchmaker.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 My-matchmaker.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

my-matchmaker.com

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