Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

match.se

Dejting med Match | Dejtingsajt för seriösa singlar

Page Load Speed

2.7 sec in total

First Response

193 ms

Resources Loaded

2.5 sec

Page Rendered

55 ms

match.se screenshot

About Website

Visit match.se now to see the best up-to-date Match content and also check out these interesting facts you probably never knew about match.se

På Match finns någon för alla. Bli medlem kostnadsfritt idag och träffa någon av våra tusentals singlar. Vem vet vad det kan leda till?

Visit match.se

Key Findings

We analyzed Match.se page load time and found that the first response time was 193 ms and then it took 2.5 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

match.se performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

match.se

193 ms

se.match.com

777 ms

large-2b6653b2214.webp

88 ms

bundle-bb58412e76a8e7c.js

69 ms

positive-27ae9801c9c.svg

61 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Match.se, 96% (52 requests) were made to Iliusstu-a.akamaihd.net and 2% (1 request) were made to Se.match.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Iliusstu-a.akamaihd.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 176.0 kB (14%)

Content Size

1.2 MB

After Optimization

1.1 MB

In fact, the total size of Match.se main page is 1.2 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. 35% of websites need less resources to load. Images take 799.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 137.5 kB

  • Original 172.3 kB
  • After minification 172.3 kB
  • After compression 34.8 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 137.5 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 9.7 kB

  • Original 799.6 kB
  • After minification 789.8 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 images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 28.7 kB

  • Original 278.0 kB
  • After minification 278.0 kB
  • After compression 249.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 16 (31%)

Requests Now

52

After Optimization

36

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

Accessibility Review

match.se accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

match.se 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

match.se SEO score

86

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

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

    SV

  • Language Claimed

    SV

  • Encoding

    UTF-8

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