6.5 sec in total
272 ms
5.8 sec
510 ms
Welcome to centralpay.fr homepage info - get ready to check Central Pay best content for Spain right away, or after learning these important things about centralpay.fr
La solution de paiement CentralPay aide les entreprises à accepter des paiements, unifier leur poste client, effectuer des virements et bien plus encore.
Visit centralpay.frWe analyzed Centralpay.fr page load time and found that the first response time was 272 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
centralpay.fr performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value10.6 s
0/100
25%
Value16.1 s
0/100
10%
Value12,270 ms
0/100
30%
Value0.064
97/100
15%
Value22.8 s
1/100
10%
272 ms
941 ms
68 ms
174 ms
177 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Centralpay.fr, 86% (92 requests) were made to Centralpay.eu and 7% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Centralpay.eu.
Page size can be reduced by 709.6 kB (43%)
1.7 MB
943.1 kB
In fact, the total size of Centralpay.fr main page is 1.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. 45% of websites need less resources to load. Images take 916.2 kB which makes up the majority of the site volume.
Potential reduce by 49.7 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 49.7 kB or 81% of the original size.
Potential reduce by 117.3 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, Central Pay needs image optimization as it can save up to 117.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 100.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 100.4 kB or 65% of the original size.
Potential reduce by 442.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. Centralpay.fr needs all CSS files to be minified and compressed as it can save up to 442.1 kB or 85% of the original size.
Number of requests can be reduced by 69 (71%)
97
28
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Central Pay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
centralpay.fr
272 ms
941 ms
css
68 ms
system.base.css
174 ms
system.menus.css
177 ms
system.messages.css
201 ms
system.theme.css
202 ms
comment.css
201 ms
field.css
197 ms
node.css
343 ms
search.css
353 ms
user.css
361 ms
views.css
291 ms
colorbox_style.css
373 ms
ctools.css
363 ms
flexslider_img.css
462 ms
flexslider.css
507 ms
eu_cookie_compliance.css
524 ms
general1.css
540 ms
faq.css
535 ms
front1.css
543 ms
jquery.mobile.css
641 ms
custom1.css
668 ms
slicknav.css
690 ms
faq-2.css
706 ms
faq-3.css
703 ms
tarif1.css
710 ms
recrutement1.css
816 ms
contact1.css
831 ms
ywa1-2.css
929 ms
ywa2.css
878 ms
ywa3.css
887 ms
smartlink1.css
889 ms
responsive-nav.css
985 ms
jquery.min.js
52 ms
jquery.once.js
992 ms
drupal.js
1052 ms
fr_cspOVdF4m6Y4KvL2F3teZgOc6TbqT7pAX5srmglol2Q.js
1042 ms
jquery.colorbox-min.js
1051 ms
colorbox.js
1094 ms
colorbox_style.js
996 ms
colorbox_load.js
990 ms
captcha.js
1021 ms
jquery.flexslider-min.js
1025 ms
googleanalytics.js
1030 ms
jquery.slicknav.min.js
1077 ms
jquery.ddslick.min.js
1048 ms
responsive3.js
995 ms
codewebtools.js
1036 ms
html5shiv.js
1035 ms
jquery.slicknav.min.js
1035 ms
jquery.colorbox.js
1082 ms
ywa.js
1043 ms
flexslider.load.js
1006 ms
eu_cookie_compliance.js
1029 ms
css
24 ms
reset.css
1019 ms
font1.css
1032 ms
analytics.js
103 ms
ic1.png
189 ms
ic2.png
188 ms
ic3.png
189 ms
env.png
192 ms
fr.jpg
191 ms
it.png
220 ms
es.jpg
351 ms
logohaut.gif
353 ms
compte.gif
352 ms
arrow-to-top-blue-100.png
426 ms
diaporma-1_0_1.jpg
595 ms
diaporma-2_3.jpg
1604 ms
diaporma-3_0.jpg
742 ms
arrow-down.png
504 ms
cell-hover.png
1510 ms
icon-two.png
590 ms
icon-three.png
592 ms
online-pay-options.png
705 ms
link-btn.png
760 ms
square-box-04.png
1766 ms
square-box-03.png
792 ms
square-box-02.png
827 ms
square-box-01.png
847 ms
framework-list.png
1123 ms
arrow-left.png
995 ms
gaurentee-box.png
1438 ms
gaurentee-box-01.png
1173 ms
gaurentee-box-02.png
1294 ms
gaurentee-box-03.png
1182 ms
Smartlink-centralpay_0.png
2419 ms
centralpay-logo_0.png
1464 ms
actualites-graphic.png
1778 ms
seo.png
1632 ms
menu_in.png
1597 ms
sinscrire1.png
2845 ms
logobas.png
1706 ms
contact.png
1541 ms
menu-expanded.png
1713 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
30 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
127 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
31 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
158 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
77 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
156 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
76 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
156 ms
collect
106 ms
collect
99 ms
centralpay.fr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
centralpay.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
centralpay.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Document uses legible font sizes
EN
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Centralpay.fr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Centralpay.fr 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.
centralpay.fr
Open Graph description is not detected on the main page of Central Pay. 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: