Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

couply.io

Couply – the App for Couples. Couples Quizzes, Questions and Relationship Games

Page Load Speed

1.4 sec in total

First Response

11 ms

Resources Loaded

951 ms

Page Rendered

475 ms

couply.io screenshot

About Website

Welcome to couply.io homepage info - get ready to check Couply best content right away, or after learning these important things about couply.io

Couply is the App for Couples. Take Couples Personality Quizzes, Answer Questions and play fun Couples Games that Improve your Relationship.

Visit couply.io

Key Findings

We analyzed Couply.io page load time and found that the first response time was 11 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

couply.io performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

couply.io

11 ms

couply.io

57 ms

www.couply.io

217 ms

couply.webflow.758afcc28.min.css

47 ms

webfont.js

46 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Couply.io, 44% (27 requests) were made to Assets-global.website-files.com and 34% (21 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (514 ms) relates to the external source Assets-global.website-files.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 636.9 kB (8%)

Content Size

7.8 MB

After Optimization

7.1 MB

In fact, the total size of Couply.io main page is 7.8 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. 70% of websites need less resources to load. Images take 7.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.0 kB

  • Original 42.6 kB
  • After minification 42.5 kB
  • After compression 7.6 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 35.0 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 565.6 kB

  • Original 7.4 MB
  • After minification 6.8 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. Couply images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 22.5 kB

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

CSS Optimization

-16%

Potential reduce by 13.9 kB

  • Original 88.2 kB
  • After minification 88.2 kB
  • After compression 74.4 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. Couply.io needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (24%)

Requests Now

38

After Optimization

29

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

Accessibility Review

couply.io accessibility score

93

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.

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

Links do not have a discernible name

Best Practices

couply.io best practices score

83

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

couply.io 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

Links do not have descriptive text

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Couply.io 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 Couply.io 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 data is detected on the main page of Couply. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: