Tools & Wizards About Us
cardlay.com screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    84% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

cardlay.com

We make it easy to handle cards, payments, and expenses.

Page Load Speed

4.5 sec in total

First Response

28 ms

Resources Loaded

3.9 sec

Page Rendered

622 ms

cardlay.com screenshot

About Website

Visit cardlay.com now to see the best up-to-date Cardlay content and also check out these interesting facts you probably never knew about cardlay.com

We deliver fast-scalable white-label solutions to enable and serve financial institutions with the newest commercial payment infrastructure and front end.

Visit cardlay.com

Key Findings

We analyzed Cardlay.com page load time and found that the first response time was 28 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

cardlay.com performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

cardlay.com

28 ms

cardlay.com

30 ms

site.css

933 ms

player.js

36 ms

site.js

837 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 65% of them (31 requests) were addressed to the original Cardlay.com, 8% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Cardlay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 505.2 kB (13%)

Content Size

4.0 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cardlay.com main page is 4.0 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 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 150.9 kB

  • Original 172.6 kB
  • After minification 158.5 kB
  • After compression 21.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 150.9 kB or 87% of the original size.

Image Optimization

-10%

Potential reduce by 352.5 kB

  • Original 3.6 MB
  • After minification 3.3 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. Cardlay images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.8 kB

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

CSS Optimization

-0%

Potential reduce by 25 B

  • Original 58.9 kB
  • After minification 58.9 kB
  • After compression 58.9 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. Cardlay.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (25%)

Requests Now

40

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cardlay.com

cardlay.com

28 ms

cardlay.com

cardlay.com

30 ms

site.css

site.css

933 ms

player.js

player.js

36 ms

site.js

site.js

837 ms

widget.js

widget.js

157 ms

css2

css2

46 ms

flickity.min.css

flickity.min.css

49 ms

flickity.min.css

flickity.min.css

16 ms

widget.css

widget.css

159 ms

de5e1a68e15a38c74201fe3ab.js

de5e1a68e15a38c74201fe3ab.js

303 ms

1a68c510e5b109102f7093a23d924cf9.png

1a68c510e5b109102f7093a23d924cf9.png

40 ms

c12105701e05e5d03b72c86bb06398da.png

c12105701e05e5d03b72c86bb06398da.png

43 ms

d966e9f21e453c135f927d5628632419.png

d966e9f21e453c135f927d5628632419.png

43 ms

98c20a827724b9b4baca20e0c02e0c90.png

98c20a827724b9b4baca20e0c02e0c90.png

50 ms

a87c9393cf2489f2b148a5a693965776.png

a87c9393cf2489f2b148a5a693965776.png

56 ms

01e370aadec25b5e959e3aee74d007f4.png

01e370aadec25b5e959e3aee74d007f4.png

56 ms

aboutcard.svg

aboutcard.svg

57 ms

eurocard.svg

eurocard.svg

481 ms

sap-concur-1.svg

sap-concur-1.svg

486 ms

mc_hrz_rev.svg

mc_hrz_rev.svg

475 ms

seb.svg

seb.svg

515 ms

visa_brandmark_white_rgb.svg

visa_brandmark_white_rgb.svg

79 ms

pwc-color.svg

pwc-color.svg

80 ms

solaris-logo-developers-d65544ba3233b455a70f29218b2dd10a-1.svg

solaris-logo-developers-d65544ba3233b455a70f29218b2dd10a-1.svg

499 ms

spendplatform.svg

spendplatform.svg

903 ms

af727393aae215a4fd51ef76d8d1c31b.png

af727393aae215a4fd51ef76d8d1c31b.png

495 ms

704545c69318beb2eea91daef53ac4f4.png

704545c69318beb2eea91daef53ac4f4.png

1379 ms

d0aa59c229ca14d1f6cd279fee9ab13f.png

d0aa59c229ca14d1f6cd279fee9ab13f.png

1399 ms

de78300a1dbc9f8d71a3c75084365bba.png

de78300a1dbc9f8d71a3c75084365bba.png

1349 ms

b3fb38f07afe266f60c25131116368df.png

b3fb38f07afe266f60c25131116368df.png

1223 ms

partnerlogos_updatedaug24.svg

partnerlogos_updatedaug24.svg

1161 ms

ce6e497f6b3937b2e55c61ba6f0e1063.jpeg

ce6e497f6b3937b2e55c61ba6f0e1063.jpeg

929 ms

51e10499c37f5d841b75304658a7f4a0.png

51e10499c37f5d841b75304658a7f4a0.png

1421 ms

cec755e8c39f11d30a596c999e670b3c.png

cec755e8c39f11d30a596c999e670b3c.png

2537 ms

afe33697144e7e7d4b95108afff46adf.png

afe33697144e7e7d4b95108afff46adf.png

1227 ms

f6cb85ee055fe9945af6f0bbec5c3e3c.png

f6cb85ee055fe9945af6f0bbec5c3e3c.png

1231 ms

526b5fd9835b91656884d6fb1b667bdb.png

526b5fd9835b91656884d6fb1b667bdb.png

1235 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

56 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

70 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

110 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

106 ms

799852509

799852509

259 ms

legal.js

legal.js

72 ms

fbevents.js

fbevents.js

35 ms

lftracker_v1_ywVkO4X12vEaZ6Bj.js

lftracker_v1_ywVkO4X12vEaZ6Bj.js

340 ms

api.js

api.js

12 ms

tr.lfeeder.com

tr.lfeeder.com

61 ms

Accessibility Review

cardlay.com accessibility score

85

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

cardlay.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

cardlay.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Cardlay.com 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 Cardlay.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

cardlay.com

Open Graph data is detected on the main page of Cardlay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: