Tools & Wizards About Us
p.ly screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    83% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

p.ly

PayMeWith: One page for all your social payments.

Page Load Speed

287 ms in total

First Response

91 ms

Resources Loaded

112 ms

Page Rendered

84 ms

p.ly screenshot

About Website

Visit p.ly now to see the best up-to-date P content and also check out these interesting facts you probably never knew about p.ly

Create a single page for all your social payments. PayMeWith supports Venmo, Cash App, PayPal, and Google Pay. Claim your username today!

Visit p.ly

Key Findings

We analyzed P.ly page load time and found that the first response time was 91 ms and then it took 196 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

p.ly performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

p.ly

91 ms

bootstrap.min.css

5 ms

bootstrap-responsive.css

11 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that all of those requests were addressed to P.ly and no external sources were called. The less responsive or slowest element that took the longest time to load (91 ms) belongs to the original domain P.ly.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.8 kB (83%)

Content Size

98.7 kB

After Optimization

16.9 kB

  • HTML
  • CSS

In fact, the total size of P.ly main page is 98.7 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. Only 10% of websites need less resources to load. CSS take 97.4 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 684 B

  • Original 1.3 kB
  • After minification 1.1 kB
  • After compression 583 B

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. This page needs HTML code to be minified as it can gain 140 B, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 684 B or 54% of the original size.

CSS Optimization

-83%

Potential reduce by 81.1 kB

  • Original 97.4 kB
  • After minification 93.6 kB
  • After compression 16.3 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. P.ly needs all CSS files to be minified and compressed as it can save up to 81.1 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

  • CSS

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of P. According to our analytics all requests are already optimized.

Network Requests Diagram

p.ly

p.ly

91 ms

bootstrap.min.css

bootstrap.min.css

5 ms

bootstrap-responsive.css

bootstrap-responsive.css

11 ms

Accessibility Review

p.ly accessibility score

98

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.

Best Practices

p.ly best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

p.ly SEO score

100

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

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 P.ly 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 P.ly 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

p.ly

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