Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

clover.co

Clover Live

Page Load Speed

443 ms in total

First Response

25 ms

Resources Loaded

201 ms

Page Rendered

217 ms

clover.co screenshot

About Website

Visit clover.co now to see the best up-to-date Clover content for United States and also check out these interesting facts you probably never knew about clover.co

Clover is the fastest way to meet new people on iPhone, iPad and Apple Watch. Forget needing to use multiple dating apps, Clover is the only free dating app you’ll ever need. Clover = Tinder + Match +...

Visit clover.co

Key Findings

We analyzed Clover.co page load time and found that the first response time was 25 ms and then it took 418 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

clover.co performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.916

3/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

clover.co

25 ms

font-awesome.min.css

7 ms

web-header.css

10 ms

web-index.css

11 ms

web-footer.css

13 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 72% of them (23 requests) were addressed to the original Clover.co, 13% (4 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (93 ms) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.0 kB (25%)

Content Size

1.1 MB

After Optimization

808.0 kB

In fact, the total size of Clover.co main page is 1.1 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. 60% of websites need less resources to load. Images take 804.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 7.2 kB

  • Original 9.6 kB
  • After minification 7.7 kB
  • After compression 2.4 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 1.9 kB, which is 20% 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 7.2 kB or 75% of the original size.

Image Optimization

-10%

Potential reduce by 76.4 kB

  • Original 804.1 kB
  • After minification 727.7 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. Clover images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 153.2 kB

  • Original 220.0 kB
  • After minification 189.6 kB
  • After compression 66.8 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 153.2 kB or 70% of the original size.

CSS Optimization

-77%

Potential reduce by 36.2 kB

  • Original 47.3 kB
  • After minification 42.6 kB
  • After compression 11.1 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. Clover.co needs all CSS files to be minified and compressed as it can save up to 36.2 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (50%)

Requests Now

26

After Optimization

13

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

Accessibility Review

clover.co accessibility score

72

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

clover.co best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

clover.co SEO score

92

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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