Access en.payfacile.com.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value2,380 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

en.payfacile.com

227 ms

www.payfacile.com

492 ms

d22bdb36043192b0082ebb62d9a2d823269961df.css

282 ms

icon

34 ms

css2

52 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original En.payfacile.com, 57% (38 requests) were made to Payfacile-prod.s3.eu-west-1.amazonaws.com and 16% (11 requests) were made to Payfacile.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Payfacile.com.

Content Size

560.3 kB

After Optimization

306.7 kB

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

HTML Optimization

-83%

Potential reduce by 171.6 kB

Original 206.5 kB
After minification 206.4 kB
After compression 34.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 171.6 kB or 83% of the original size.

Image Optimization

-23%

Potential reduce by 82.1 kB

Original 353.8 kB
After minification 271.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. Obviously, En Payfacile needs image optimization as it can save up to 82.1 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 En.payfacile.com 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 En.payfacile.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

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