Tools & Wizards About Us
paypal.co.zw screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

paypal.co.zw

A Simple and Safer Way to Pay and Get Paid | PayPal ZW

Page Load Speed

1.2 sec in total

First Response

221 ms

Resources Loaded

838 ms

Page Rendered

182 ms

paypal.co.zw screenshot

About Website

Click here to check amazing Pay Pal content. Otherwise, check out these important facts you probably never knew about paypal.co.zw

PayPal is the faster, safer way to send money and make an online payment or set up a merchant account.

Visit paypal.co.zw

Key Findings

We analyzed Paypal.co.zw page load time and found that the first response time was 221 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

paypal.co.zw performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value1,110 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

paypal.co.zw

221 ms

home

289 ms

ngrlCaptcha.min.js

35 ms

13d0539ec464ee32f44dc22b363ec99b0e72de.css

35 ms

d051c320e03909781887cf54277c8f4247eaa0.css

47 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Paypal.co.zw, 74% (20 requests) were made to Paypalobjects.com and 11% (3 requests) were made to Paypal.com. The less responsive or slowest element that took the longest time to load (289 ms) relates to the external source Paypal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.5 kB (8%)

Content Size

425.5 kB

After Optimization

393.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Paypal.co.zw main page is 425.5 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. 60% of websites need less resources to load. Javascripts take 182.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 25.5 kB

  • Original 34.6 kB
  • After minification 32.9 kB
  • After compression 9.1 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 25.5 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 6.6 kB

  • Original 154.0 kB
  • After minification 147.4 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. Pay Pal images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 144 B

  • Original 182.9 kB
  • After minification 182.9 kB
  • After compression 182.7 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 261 B

  • Original 54.0 kB
  • After minification 54.0 kB
  • After compression 53.8 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. Paypal.co.zw has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (48%)

Requests Now

23

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

paypal.co.zw

paypal.co.zw

221 ms

home

home

289 ms

ngrlCaptcha.min.js

ngrlCaptcha.min.js

35 ms

13d0539ec464ee32f44dc22b363ec99b0e72de.css

13d0539ec464ee32f44dc22b363ec99b0e72de.css

35 ms

d051c320e03909781887cf54277c8f4247eaa0.css

d051c320e03909781887cf54277c8f4247eaa0.css

47 ms

fa89f17d37eb3f97e39b926835ba73c0a3fd63.css

fa89f17d37eb3f97e39b926835ba73c0a3fd63.css

47 ms

fdf5a4f0d44bf94b04e61e953edcb545c79db9.css

fdf5a4f0d44bf94b04e61e953edcb545c79db9.css

46 ms

main-08f0d9c8.css

main-08f0d9c8.css

42 ms

main-aaa6f59d.js

main-aaa6f59d.js

44 ms

6def5b234cbc37a348f3690b696fbb739f6371.js

6def5b234cbc37a348f3690b696fbb739f6371.js

56 ms

ae1d8b387bed087c07d56e5e4fbed891a65a29.js

ae1d8b387bed087c07d56e5e4fbed891a65a29.js

148 ms

pa.js

pa.js

150 ms

marketingIntentsV2.js

marketingIntentsV2.js

55 ms

recaptchav3.js

recaptchav3.js

253 ms

pp_fc_hl.svg

pp_fc_hl.svg

123 ms

homepage-hero-1x.jpg

homepage-hero-1x.jpg

122 ms

1-individuals.jpg

1-individuals.jpg

120 ms

buyonline_browser1.png

buyonline_browser1.png

124 ms

buyonline_browser2.png

buyonline_browser2.png

124 ms

buyonline_browser3.png

buyonline_browser3.png

122 ms

latmconf.js

latmconf.js

27 ms

ts

ts

126 ms

ts

ts

133 ms

PayPalSansBig-Light.woff

PayPalSansBig-Light.woff

40 ms

PayPalSansSmall-Regular.woff

PayPalSansSmall-Regular.woff

22 ms

ts

ts

73 ms

grcenterprise_v3.html

grcenterprise_v3.html

66 ms

Accessibility Review

paypal.co.zw accessibility score

92

Accessibility Issues

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

Image elements do not have [alt] attributes

Best Practices

paypal.co.zw best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

paypal.co.zw SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Paypal.co.zw 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 Paypal.co.zw 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

paypal.co.zw

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