Tools & Wizards About Us
paylinks.app screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

paylinks.app

Send links to accept payments with PayPal and Stripe by Paylinks

Page Load Speed

327 ms in total

First Response

44 ms

Resources Loaded

283 ms

Page Rendered

0 ms

paylinks.app screenshot

About Website

Click here to check amazing Paylinks content. Otherwise, check out these important facts you probably never knew about paylinks.app

Get paid using a simple link. Download the app, create a pay link and share with your friends and customers. Available for PayPal, Stripe. Find out more...

Visit paylinks.app

Key Findings

We analyzed Paylinks.app page load time and found that the first response time was 44 ms and then it took 283 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

paylinks.app performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value2,730 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

paylinks.app

44 ms

www.paylinks.app

78 ms

bootstrap.min.css

42 ms

css2

52 ms

js

78 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 56% of them (5 requests) were addressed to the original Paylinks.app, 11% (1 request) were made to Stackpath.bootstrapcdn.com and 11% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (119 ms) belongs to the original domain Paylinks.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.9 kB (59%)

Content Size

8.2 kB

After Optimization

3.3 kB

  • HTML

In fact, the total size of Paylinks.app main page is 8.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 8.2 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 4.9 kB

  • Original 8.2 kB
  • After minification 8.2 kB
  • After compression 3.3 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 4.9 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (43%)

Requests Now

7

After Optimization

4

  • JavaScript
  • CSS

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

Network Requests Diagram

paylinks.app

paylinks.app

44 ms

www.paylinks.app

www.paylinks.app

78 ms

bootstrap.min.css

bootstrap.min.css

42 ms

css2

css2

52 ms

js

js

78 ms

main.a4a13d5d.chunk.css

main.a4a13d5d.chunk.css

119 ms

js

js

50 ms

5.8e5162ed.chunk.js

5.8e5162ed.chunk.js

27 ms

main.1fef440e.chunk.js

main.1fef440e.chunk.js

29 ms

Accessibility Review

paylinks.app accessibility score

78

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

paylinks.app 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

paylinks.app 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 Paylinks.app 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 Paylinks.app 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

paylinks.app

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