Tools & Wizards About Us
yapily.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

yapily.com

Yapily - Open Banking Platform

Page Load Speed

3.7 sec in total

First Response

27 ms

Resources Loaded

2 sec

Page Rendered

1.7 sec

yapily.com screenshot

About Website

Click here to check amazing Yapily content for United Kingdom. Otherwise, check out these important facts you probably never knew about yapily.com

Connect to thousands of banks across 19 countries in minutes through Yapily's open banking API. Access data, process payments, and much more. What will you build?

Visit yapily.com

Key Findings

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

Performance Metrics

yapily.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value1,410 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

yapily.com

27 ms

www.yapily.com

513 ms

hotjar-3232074.js

100 ms

54f809098de3b468.css

155 ms

b6ddc70d2117c74c.css

112 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 35% of them (24 requests) were addressed to the original Yapily.com, 49% (34 requests) were made to Images.ctfassets.net and 10% (7 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Yapily.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 320.6 kB (10%)

Content Size

3.4 MB

After Optimization

3.1 MB

  • HTML
  • Images

In fact, the total size of Yapily.com main page is 3.4 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. 50% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 119.8 kB

  • Original 147.2 kB
  • After minification 147.2 kB
  • After compression 27.5 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 119.8 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 200.9 kB

  • Original 3.2 MB
  • After minification 3.0 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. Yapily images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 20 (32%)

Requests Now

63

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yapily.com

yapily.com

27 ms

www.yapily.com

www.yapily.com

513 ms

hotjar-3232074.js

hotjar-3232074.js

100 ms

54f809098de3b468.css

54f809098de3b468.css

155 ms

b6ddc70d2117c74c.css

b6ddc70d2117c74c.css

112 ms

653b327b7050594d.css

653b327b7050594d.css

341 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

442 ms

webpack-d81cde0689a3b554.js

webpack-d81cde0689a3b554.js

339 ms

framework-0c7baedefba6b077.js

framework-0c7baedefba6b077.js

549 ms

main-959f6b95aa5205a7.js

main-959f6b95aa5205a7.js

556 ms

_app-d9d2962536237f7e.js

_app-d9d2962536237f7e.js

698 ms

459-93ad5915bc771c9f.js

459-93ad5915bc771c9f.js

461 ms

967-1c6ba321e9812df1.js

967-1c6ba321e9812df1.js

482 ms

185-0b92dc56cb12ed98.js

185-0b92dc56cb12ed98.js

894 ms

index-7b9ca40675f4e32e.js

index-7b9ca40675f4e32e.js

558 ms

_buildManifest.js

_buildManifest.js

573 ms

_ssgManifest.js

_ssgManifest.js

613 ms

Payments_48px.svg

Payments_48px.svg

28 ms

VRP_48px.svg

VRP_48px.svg

28 ms

cvrp_icon.svg

cvrp_icon.svg

32 ms

Bulk-Payments_48px.svg

Bulk-Payments_48px.svg

31 ms

Data_48px.svg

Data_48px.svg

35 ms

Validate_48px.svg

Validate_48px.svg

32 ms

Connect_48px.svg

Connect_48px.svg

34 ms

Payment-Services_48px.svg

Payment-Services_48px.svg

35 ms

icon_gambling_48px.svg

icon_gambling_48px.svg

36 ms

Accounting_48px.svg

Accounting_48px.svg

37 ms

Lending-Credit_48px.svg

Lending-Credit_48px.svg

39 ms

Crypto_48px.svg

Crypto_48px.svg

43 ms

open-banking-solution-proptech.svg

open-banking-solution-proptech.svg

41 ms

Investing_48px.svg

Investing_48px.svg

40 ms

Digital-Banking_48px.svg

Digital-Banking_48px.svg

44 ms

Console_48_px.svg

Console_48_px.svg

43 ms

Docs_48px.svg

Docs_48px.svg

45 ms

Demo_48px.svg

Demo_48px.svg

46 ms

Culture_48px.svg

Culture_48px.svg

49 ms

Careers_48px.svg

Careers_48px.svg

51 ms

Blog_48px.svg

Blog_48px.svg

48 ms

FAQs_48px.svg

FAQs_48px.svg

165 ms

case_study_icon.svg

case_study_icon.svg

53 ms

events_icon.svg

events_icon.svg

51 ms

Resource-hub_48px.svg

Resource-hub_48px.svg

53 ms

Homepage-logo-1.svg

Homepage-logo-1.svg

54 ms

Homepage-logo-2.svg

Homepage-logo-2.svg

55 ms

Homepage-logo-4.svg

Homepage-logo-4.svg

57 ms

Homepage-logo-5.svg

Homepage-logo-5.svg

58 ms

Homepage-logo-6.svg

Homepage-logo-6.svg

59 ms

VRP_64px.svg

VRP_64px.svg

60 ms

Virtual-Accounts_48px.svg

Virtual-Accounts_48px.svg

166 ms

Pleo.svg

Pleo.svg

204 ms

image

image

962 ms

image

image

964 ms

image

image

1290 ms

image

image

794 ms

image

image

1313 ms

image

image

1010 ms

image

image

1434 ms

css2

css2

40 ms

css2

css2

58 ms

css2

css2

61 ms

css2

css2

63 ms

css2

css2

62 ms

css2

css2

63 ms

css2

css2

65 ms

Homepage_hero-bg.png

Homepage_hero-bg.png

85 ms

NEXTPanBook-Regular.fdfe54e7.woff

NEXTPanBook-Regular.fdfe54e7.woff

765 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf

26 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZg.ttf

88 ms

HI_diYsKILxRpg3hIP6sJ7fM7PqPMcMnZFqUwX28DMyQhM4.ttf

HI_diYsKILxRpg3hIP6sJ7fM7PqPMcMnZFqUwX28DMyQhM4.ttf

96 ms

Accessibility Review

yapily.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

yapily.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

SEO Factors

yapily.com SEO score

98

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Yapily.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 Yapily.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

yapily.com

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