paypou.com

paypou.com is SSL secured

Free website and domain report on paypou.com

Last Updated: 12th April, 2024
Overview

Snoop Summary for paypou.com

This is a free and comprehensive report about paypou.com. Paypou.com is hosted in United States on a server with an IP address of 104.21.95.110, where USD is the local currency and the local language is English. Our records indicate that paypou.com is privately registered by REDACTED FOR PRIVACY. Paypou.com has the potential to be earning an estimated $3 USD per day from advertising revenue. If paypou.com was to be sold it would possibly be worth $2,425 USD (based on the daily revenue potential of the website over a 24 month period). Paypou.com receives an estimated 1,161 unique visitors every day - a large amount of traffic! This report was last updated 12th April, 2024.

About paypou.com

Site Preview: paypou.com paypou.com
Title: Facebook Video Downloader
Description: PHP Video Downloader Script allows you to download videos from multiple video sources.
Keywords and Tags: facebook video download, search engines, youtube to mp3 converter, youtube video downloader
Related Terms: 123movies downloader, 4k video downloader review, downloader helper, facebook downloader, fb video downloader, igtv downloader, m3u8 downloader, mixdrop downloader, social video downloader, webshare downloader
Fav Icon:
Age: Over 4 years old
Domain Created: 24th November, 2019
Domain Updated: 17th September, 2023
Domain Expires: 24th November, 2024
Review

Snoop Score

2/5

Valuation

$2,425 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 725,027
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,161
Monthly Visitors: 35,337
Yearly Visitors: 423,765
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $3 USD
Monthly Revenue: $101 USD
Yearly Revenue: $1,208 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: paypou.com 10
Domain Name: paypou 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.46 seconds
Load Time Comparison: Faster than 96% of sites

PageSpeed Insights

Avg. (All Categories) 73
Performance 98
Accessibility 79
Best Practices 75
SEO 91
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
98

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for paypou.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 70 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://paypou.com/
http/1.1
0
253.08500009123
4780
13228
200
text/html
Document
https://paypou.com/webroot/css/bootstrap.min.css
h2
261.1480000196
1178.2160000876
25555
160403
200
text/css
Stylesheet
https://paypou.com/webroot/css/all.min.css
h2
262.422000058
512.93000008445
11911
51161
200
text/css
Stylesheet
https://paypou.com/webroot/css/style.css
h2
262.7630000934
503.67500004359
5277
21185
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Open+Sans:300,300i,400,400i,600,600i,700,700i,800,800i|Roboto:100,100i,300,300i,400,400i,500,500i,700,700i,900,900i
h2
262.86400004756
291.51900007855
2616
51740
200
text/css
Stylesheet
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
h2
1180.085
1202.6349999942
56062
172084
200
text/javascript
Script
https://paypou.com/webroot/images/logo.png
h2
1185.9770000447
1446.7220000224
16257
15526
200
image/png
Image
https://paypou.com/webroot/js/jquery.min.js
h2
514.73300007638
543.33700006828
32710
89475
200
application/javascript
Script
https://paypou.com/webroot/js/bootstrap.min.js
h2
551.70399998315
616.64400005247
16224
60174
200
application/javascript
Script
https://paypou.com/webroot/js/front.app.js
h2
623.81100002676
815.27600006666
1361
1915
200
application/javascript
Script
https://paypou.com/webroot/js/thumb.js
h2
818.02700005937
1060.5080000823
1133
891
200
application/javascript
Script
https://paypou.com/webroot/js/footer-end.js
h2
1062.4519999838
1324.5009999955
837
185
200
application/javascript
Script
https://paypou.com/webroot/images/titleBorder.svg
h2
1199.4800000684
1418.7699999893
1106
863
200
image/svg+xml
Image
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
h2
1200.4160000943
1203.2210000325
12087
11160
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1200.6820000242
1204.1700000409
11956
11028
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1200.9120000293
1203.6870000884
11967
11040
200
font/woff2
Font
https://paypou.com/webroot/fonts/fa-brands-400.woff2
1200.6040000124
1684.493000037
0
0
-1
Font
https://paypou.com/webroot/fonts/fa-solid-900.woff2
1200.8420000784
1715.8730000956
0
0
-1
Font
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
1201.734000002
1206.0550000751
12000
11072
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
h2
1205.2350000013
1209.1900000814
40300
39372
200
font/woff2
Font
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js
h2
1273.4359999886
1306.30200007
119762
362053
200
text/javascript
Script
https://googleads.g.doubleclick.net/pagead/html/r20221027/r20190131/zrt_lookup.html
h2
1281.9390000077
1286.1050000647
5022
9849
200
text/html
Document
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
http/1.1
1340.0499999989
1386.5600000136
17843
34628
200
application/javascript
Script
https://partner.googleadservices.com/gampad/cookie.js?domain=paypou.com&callback=_gfp_s_&client=ca-pub-7679612849647892&gpid_exp=1
h2
1382.7270000475
1387.5580000458
891
387
200
text/javascript
Script
https://adservice.google.com/adsid/integrator.js?domain=paypou.com
h2
1389.0580000589
1395.0140000088
758
107
200
application/javascript
Script
https://googleads.g.doubleclick.net/pagead/ads?client=ca-pub-7679612849647892&output=html&adk=1812271804&adf=3025194257&lmt=1667367334&plat=9%3A32776%2C16%3A8388608%2C17%3A32%2C24%3A32%2C25%3A32%2C30%3A1081344%2C32%3A32&format=0x0&url=http%3A%2F%2Fpaypou.com%2F&ea=0&pra=5&wgl=1&dt=1667367334315&bpp=4&bdt=1014&idt=97&shv=r20221027&mjsv=m202210260101&ptt=9&saldr=aa&abxe=1&nras=1&correlator=4578406858226&frm=20&pv=2&ga_vid=1867951098.1667367334&ga_sid=1667367334&ga_hid=1358991597&ga_fc=0&u_tz=-420&u_his=2&u_h=600&u_w=800&u_ah=600&u_aw=800&u_cd=24&u_sd=1&adx=-12245933&ady=-12245933&biw=1350&bih=940&scr_x=0&scr_y=0&eid=42531705%2C44775016&oid=2&pvsid=1179669766947210&tmod=724071789&uas=0&nvt=1&eae=2&fc=1920&brdim=0%2C0%2C0%2C0%2C800%2C0%2C1%2C1%2C1350%2C940&vis=1&rsz=%7C%7Cs%7C&abl=NS&fu=32768&bc=23&ifi=1&uci=a!1&fsb=1&dtd=124
h2
1399.8879999854
1419.934000005
867
603
200
text/html
Document
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
http/1.1
1423.4350000042
1449.9650000362
9712
19341
200
application/javascript
Other
https://paypou.com/webroot/fonts/fa-brands-400.woff
1684.0410000877
2225.3800000763
0
0
-1
Font
https://paypou.com/webroot/fonts/fa-solid-900.woff
1715.5460000504
2312.3980000382
0
0
-1
Font
http://paypou.com/cdn-cgi/challenge-platform/h/b/cv/result/763a81e7d94f5dda
http/1.1
2158.429000061
2214.389000088
950
2
200
text/plain
XHR
https://paypou.com/webroot/fonts/fa-brands-400.ttf
2225.0600000843
3042.310000048
0
0
-1
Font
https://paypou.com/webroot/fonts/fa-solid-900.ttf
2312.0730000082
3342.9140000371
0
0
-1
Font
https://pagead2.googlesyndication.com/getconfig/sodar?sv=200&tid=gda&tv=r20221027&st=env
h2
3346.5220000362
3360.0050000241
11631
14426
200
application/json
XHR
https://tpc.googlesyndication.com/sodar/sodar2.js
h2
3372.0090000425
3380.0010000123
7166
17314
200
text/javascript
Script
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
h2
3393.00000004
3402.9230000451
5856
12817
200
text/html
Document
https://www.google.com/recaptcha/api2/aframe
h2
3396.8380000442
3407.0589999901
1425
783
200
text/html
Document
https://pagead2.googlesyndication.com/pagead/sodar?id=sodar2&v=225&li=gda_r20221027&jk=1179669766947210&rc=
h2
3439.3810000038
3444.382000016
516
0
204
text/html
Image
https://pagead2.googlesyndication.com/bg/PTWQOrfCOp17EyrMcPeT6PfhP85_faJCCfTgkqMfTIQ.js
h2
3442.8280000575
3447.5920000114
17112
37237
200
text/javascript
Script
https://tpc.googlesyndication.com/generate_204?l6AwGA
h2
3643.1800000137
3646.6789999977
268
0
204
text/plain
Image
https://pagead2.googlesyndication.com/pagead/sodar?id=sodar2&v=225&t=2&li=gda_r20221027&jk=1179669766947210&bg=!j4yljMjNAAZPh4lnb4c7ACkAdvg8WuA_Ar9v0P7Lq0J_1XoX6LNNuxCQad3Xu7SvRZxH4SbO4Mu2EwIAAAD0UgAAAApoAQeZAvgCvOauEYoCc5eeta2X8v2PUcJwEh_PwRqr9PEdGQCJt3bXqokSqyQjAghTNuqWqZCmOqSfom2TZpJFpsw-w3AH8YvlhMNKVSwzAgr5pVn1UI3LaMeUG0zQ3hD3_e_A5Shgs0SFP2aoBUqq03XLIqlovmXXJ01wbIfA239JjAbepBzY_uRboovSgZ8-WBlzeCF_SDEZ5UD5rgwDg_w4kNPbgf-kJWCRcYWvZVxS-fVc4f8Zh6lXSFEuic51JFyg35MtgI7uaDl2QtplvbndDOgOb2bqaWEJJkq0_k9tutjB5kt_3Tx_cEexVBYFO_FRHe9OhGOEpsDyfI2rZa4vUsUD5mNfAt9SfR5WiGY6iQsmUAx3NhmaRK-faWTzwJpUO7jDtfmywgSw9U_r-o8zc6w9KYILojUORJnk3ndVVtsehUzsgtnSmMBGuWwgVYrz0YH8wChRqp3sKnvYaHD3EXTIQM4npChfQVB2ea5N7Wle1ltfltQyMwA96tVp0t6QhBIvGMm3x7BY6Xwd_nSL9pz4Yr1U2zlMcuqwP2AhSm39ULA5ZPrDt6cPj3NRwhg2rDixCd1cPQmVBKe5hhM6-sJosADnHkI34ftH0Q2Q0P4gLikwdeheWVbJwDZNV9GKD5v1WXLqMEFi66KUVAK2-iiTrssQM1x3-o4NEjPol6FpOoNNq3MaO6sRfEZSPRVcjDOSb0fckVV5mejT9RrgN8gj5PobY0mI_YwcaW1oMtgSvVnQ1rKA_DZ9jwc1wTKEeRKsGNlQ497hrY-uwUKm1npQjLihZwt_sqUxvzTBBP_SN-cWHeGt7XDFuab5bTR8J5xqS4qXoA6te8aZZEimJtc8q9bAhvzEEwhytR0ROEDz0Wnu1cChIcI1PDcCTYIrltXttbq1uuRtc8kKwI-Pd2VDbeQd0s7VD5Xxwnm2bIPFFGXiGULalPtpKEAt_Db8osLPhLWrgu6igw86fkigxzwG7zhiU8D3NiILYUo4-lqAx26bzF47OHnE
h2
4230.5740000447
4239.906999981
516
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
257.57
12.844
1180.068
5.542
1187.754
29.153
1216.919
18.899
1242.959
6.671
1250.605
29.389
1290.48
6.609
1327.294
9.623
1340.988
59.968
1405.257
5.969
1416.106
7.701
1427.294
7.344
1686.073
5.24
1717.126
5.073
1779.65
379.645
2170.583
5.87
3043.855
7.103
3343.585
9.887
3384.495
11.027
3408.41
9.543
3419.636
9.396
3450.69
30.788
3483.255
11.601
3494.904
13.029
3507.978
13.962
3522.783
15.285
3544.461
31.985
3576.94
6.621
3584.531
22.921
3608.371
11.879
3626.307
17.493
3644.626
15.382
3661.726
21.342
3683.952
12.378
3697.586
13.1
4214.701
11.81
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Paypou.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Paypou.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Paypou.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Paypou.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 36 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Paypou.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://paypou.com/webroot/css/bootstrap.min.css
25555
24789
https://paypou.com/webroot/css/all.min.css
11911
11789
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 15 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://paypou.com/webroot/images/logo.png
15526
14934.25
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 250 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://paypou.com/
254.074
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Paypou.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Paypou.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 454 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js
119762
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
56062
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
40300
https://paypou.com/webroot/js/jquery.min.js
32710
https://paypou.com/webroot/css/bootstrap.min.css
25555
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
17843
https://pagead2.googlesyndication.com/bg/PTWQOrfCOp17EyrMcPeT6PfhP85_faJCCfTgkqMfTIQ.js
17112
https://paypou.com/webroot/images/logo.png
16257
https://paypou.com/webroot/js/bootstrap.min.js
16224
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
12087
Avoids an excessive DOM size — 142 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
142
Maximum DOM Depth
12
Maximum Child Elements
10
Avoid chaining critical requests — 19 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Paypou.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
393.923
374.209
1.717
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
245.209
230.651
2.717
http://paypou.com/
111.696
12.103
3.457
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js
66.619
49.973
8.046
Unattributable
56.643
1.666
0
Minimizes main-thread work — 1.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
764.965
Other
102.086
Style & Layout
61.137
Script Parsing & Compilation
28.789
Garbage Collection
22.69
Rendering
21.748
Parse HTML & CSS
15.54
Keep request counts low and transfer sizes small — 40 requests • 454 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
40
464434
Script
12
271859
Font
11
88310
Stylesheet
4
45359
Other
3
22293
Image
5
18663
Document
5
17950
Media
0
0
Third-party
20
318778
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
226427
0
90926
0
1425
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00050836800574335
0.0002080899810062
2.0948253217757E-5
1.5485837492339E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
628
190
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js
988
60
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of paypou.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Max Potential First Input Delay — 190 ms
Users could experience a delay when interacting with the page.

Other

Eliminate render-blocking resources — Potential savings of 520 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Paypou.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://paypou.com/webroot/css/bootstrap.min.css
25555
190
https://fonts.googleapis.com/css?family=Open+Sans:300,300i,400,400i,600,600i,700,700i,800,800i|Roboto:100,100i,300,300i,400,400i,500,500i,700,700i,900,900i
2616
230
Reduce unused JavaScript — Potential savings of 130 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js
119762
81562
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
56062
29017
https://paypou.com/webroot/js/jquery.min.js
32710
22977
Serve static assets with an efficient cache policy — 7 resources found
Paypou.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
14400000
17843
https://paypou.com/webroot/images/titleBorder.svg
14400000
1106
https://paypou.com/webroot/css/bootstrap.min.css
43200000
25555
https://paypou.com/webroot/css/all.min.css
43200000
11911
https://paypou.com/webroot/js/thumb.js
43200000
1133
https://paypou.com/webroot/js/footer-end.js
43200000
837
https://paypou.com/webroot/images/logo.png
2592000000
16257

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
2.8049999382347
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.4880000166595
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
2.7750000590459
https://paypou.com/webroot/fonts/fa-brands-400.woff2
483.88900002465
https://paypou.com/webroot/fonts/fa-solid-900.woff2
515.03100001719
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
4.3210000731051
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
3.9550000801682
https://paypou.com/webroot/fonts/fa-brands-400.woff
541.33899998851
https://paypou.com/webroot/fonts/fa-solid-900.woff
596.85199998785
https://paypou.com/webroot/fonts/fa-brands-400.ttf
817.24999996368
https://paypou.com/webroot/fonts/fa-solid-900.ttf
1030.8410000289
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://paypou.com/webroot/images/logo.png
79

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of paypou.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Paypou.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that paypou.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.5.0
jQuery
3.5.1
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://paypou.com/webroot/js/bootstrap.min.js
https://paypou.com/webroot/js/bootstrap.min.js.map
https://pagead2.googlesyndication.com/bg/PTWQOrfCOp17EyrMcPeT6PfhP85_faJCCfTgkqMfTIQ.js
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 4 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://paypou.com/
Allowed
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
Allowed
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
Allowed
http://paypou.com/cdn-cgi/challenge-platform/h/b/cv/result/763a81e7d94f5dda
Allowed

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
`window.webkitStorageInfo` is deprecated. Please use `navigator.webkitTemporaryStorage` or `navigator.webkitPersistentStorage` instead.
...
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Access to font at 'https://paypou.com/webroot/fonts/fa-brands-400.ttf' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-brands-400.woff' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-brands-400.woff2' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-solid-900.ttf' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-solid-900.woff' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-solid-900.woff2' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for paypou.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of paypou.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of paypou.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of paypou.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 65
Performance 63
Accessibility 75
Best Practices 67
SEO 91
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
63

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for paypou.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Paypou.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Paypou.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Paypou.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Paypou.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 110 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://paypou.com/
113.548
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Paypou.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Paypou.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 454 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js?bust=31070606
119762
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
56078
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
40300
https://paypou.com/webroot/js/jquery.min.js
32698
https://paypou.com/webroot/css/bootstrap.min.css
25559
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
17915
https://pagead2.googlesyndication.com/bg/PTWQOrfCOp17EyrMcPeT6PfhP85_faJCCfTgkqMfTIQ.js
17112
https://paypou.com/webroot/images/logo.png
16251
https://paypou.com/webroot/js/bootstrap.min.js
16207
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
12088
Avoids an excessive DOM size — 142 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
142
Maximum DOM Depth
12
Maximum Child Elements
10
Avoid chaining critical requests — 19 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Paypou.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 40 requests • 454 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
40
464807
Script
12
271942
Font
11
88310
Stylesheet
4
45534
Other
3
22411
Image
5
18653
Document
5
17957
Media
0
0
Third-party
20
319015
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0024970160590278
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 14 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
3290
913
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js?bust=31070606
4369
413
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
2217
202
http://paypou.com/
692
157
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
5982
136
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
6182
97
https://paypou.com/webroot/js/jquery.min.js
2610
87
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
6371
81
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
6452
66
https://pagead2.googlesyndication.com/bg/PTWQOrfCOp17EyrMcPeT6PfhP85_faJCCfTgkqMfTIQ.js
6118
64
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
6567
60
http://paypou.com/
630
57
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
6674
55
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
5929
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of paypou.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://paypou.com/
http/1.1
0
112.55900003016
4787
13228
200
text/html
Document
https://paypou.com/webroot/css/bootstrap.min.css
h2
124.46400010958
404.61000008509
25559
160403
200
text/css
Stylesheet
https://paypou.com/webroot/css/all.min.css
h2
124.72800025716
209.81300016865
11915
51161
200
text/css
Stylesheet
https://paypou.com/webroot/css/style.css
h2
125.04000030458
151.13600017503
5291
21185
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Open+Sans:300,300i,400,400i,600,600i,700,700i,800,800i|Roboto:100,100i,300,300i,400,400i,500,500i,700,700i,900,900i
h2
125.51699997857
148.71300011873
2769
58117
200
text/css
Stylesheet
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
h2
415.24700028822
437.75600008667
56078
172122
200
text/javascript
Script
https://paypou.com/webroot/images/logo.png
h2
415.56300036609
694.05600009486
16251
15526
200
image/png
Image
https://paypou.com/webroot/js/jquery.min.js
h2
212.17499999329
242.28100012988
32698
89475
200
application/javascript
Script
https://paypou.com/webroot/js/bootstrap.min.js
h2
251.18200015277
724.23000028357
16207
60174
200
application/javascript
Script
https://paypou.com/webroot/js/front.app.js
h2
407.49200014398
599.90600030869
1360
1915
200
application/javascript
Script
https://paypou.com/webroot/js/thumb.js
h2
414.20800006017
440.07100025192
1154
891
200
application/javascript
Script
https://paypou.com/webroot/js/footer-end.js
h2
414.50199997053
606.17600008845
839
185
200
application/javascript
Script
data
440.47200027853
440.62600005418
0
216
200
image/svg+xml
Image
https://paypou.com/webroot/images/titleBorder.svg
h2
442.75900023058
632.33399996534
1102
863
200
image/svg+xml
Image
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
h2
445.86999993771
450.74400026351
12088
11160
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
447.93300004676
451.77600020543
11966
11040
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
449.06800007448
452.34700012952
11956
11028
200
font/woff2
Font
https://paypou.com/webroot/fonts/fa-brands-400.woff2
448.52300034836
540.82500003278
0
0
-1
Font
https://paypou.com/webroot/fonts/fa-solid-900.woff2
448.86900018901
528.12700020149
0
0
-1
Font
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
452.90500018746
456.0670000501
12000
11072
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
h2
459.1720001772
463.63600017503
40300
39372
200
font/woff2
Font
https://paypou.com/webroot/fonts/fa-solid-900.woff
527.89600007236
658.25200034305
0
0
-1
Font
https://paypou.com/webroot/fonts/fa-brands-400.woff
540.49100028351
1166.5360000916
0
0
-1
Font
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js?bust=31070606
h2
594.28900014609
628.79200000316
119762
362053
200
text/javascript
Script
https://googleads.g.doubleclick.net/pagead/html/r20221027/r20190131/zrt_lookup.html
h2
608.83600031957
613.88100031763
5022
9849
200
text/html
Document
https://paypou.com/webroot/fonts/fa-solid-900.ttf
657.92800020427
774.19000025839
0
0
-1
Font
https://partner.googleadservices.com/gampad/cookie.js?domain=paypou.com&callback=_gfp_s_&client=ca-pub-7679612849647892&gpid_exp=1
h2
733.95600030199
743.93700016662
893
387
200
text/javascript
Script
https://adservice.google.com/adsid/integrator.js?domain=paypou.com
h2
746.20399996638
751.99900008738
758
107
200
application/javascript
Script
https://googleads.g.doubleclick.net/pagead/ads?client=ca-pub-7679612849647892&output=html&adk=1812271804&adf=3025194257&lmt=1667367358&plat=16%3A8388608%2C17%3A32%2C24%3A32%2C25%3A32%2C32%3A32&format=0x0&url=http%3A%2F%2Fpaypou.com%2F&ea=0&pra=5&wgl=1&easpi=1&asntp=0&asntpv=0&asntpl=0&asntpm=0&asntpc=300&asna=5&asnd=5&asnp=5&asns=5&asmat=0.4&asptt=-1&aspe=0&asro=0&dt=1667367357914&bpp=8&bdt=474&idt=117&shv=r20221027&mjsv=m202210260101&ptt=9&saldr=aa&abxe=1&nras=1&correlator=6543174293126&frm=20&pv=2&ga_vid=341672819.1667367358&ga_sid=1667367358&ga_hid=1976789614&ga_fc=0&u_tz=-420&u_his=2&u_h=640&u_w=360&u_ah=640&u_aw=360&u_cd=24&u_sd=2.625&adx=-12245933&ady=-12245933&biw=360&bih=640&scr_x=0&scr_y=0&eid=44759876%2C44759927%2C44759837%2C42531705%2C44773614%2C31070606%2C44775016%2C44777813&oid=2&pvsid=1849271569829695&tmod=1254153841&uas=0&nvt=1&eae=2&fc=1920&brdim=0%2C0%2C0%2C0%2C360%2C0%2C360%2C640%2C360%2C640&vis=1&rsz=%7C%7Cs%7C&abl=NS&fu=32768&bc=23&ifi=1&uci=a!1&fsb=1&dtd=174
h2
772.20800006762
792.28099994361
867
603
200
text/html
Document
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
http/1.1
830.02700004727
852.92700026184
17915
35486
200
application/javascript
Script
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
http/1.1
882.48600019142
941.07400020584
9776
19786
200
application/javascript
Other
https://paypou.com/webroot/fonts/fa-brands-400.ttf
1166.0960000008
2007.8239999712
0
0
-1
Font
http://paypou.com/cdn-cgi/challenge-platform/h/b/cv/result/763a827f589c9c55
http/1.1
2008.6500002071
2048.9469999447
938
2
200
text/plain
XHR
https://pagead2.googlesyndication.com/getconfig/sodar?sv=200&tid=gda&tv=r20221027&st=env
h2
2010.4479999281
2022.2390000708
11697
14506
200
application/json
XHR
https://tpc.googlesyndication.com/sodar/sodar2.js
h2
2026.8680001609
2032.6650002971
7166
17314
200
text/javascript
Script
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
h2
2048.4200003557
2055.9769999236
5856
12817
200
text/html
Document
https://www.google.com/recaptcha/api2/aframe
h2
2052.2720003501
2060.6010002084
1425
783
200
text/html
Document
https://pagead2.googlesyndication.com/pagead/sodar?id=sodar2&v=225&li=gda_r20221027&jk=1849271569829695&rc=
h2
2099.3880000897
2103.9960002527
516
0
204
text/html
Image
https://pagead2.googlesyndication.com/bg/PTWQOrfCOp17EyrMcPeT6PfhP85_faJCCfTgkqMfTIQ.js
h2
2103.5220003687
2109.6450001933
17112
37237
200
text/javascript
Script
https://tpc.googlesyndication.com/generate_204?y-QZLg
h2
2314.1129999422
2317.2309999354
268
0
204
text/plain
Image
https://pagead2.googlesyndication.com/pagead/sodar?id=sodar2&v=225&t=2&li=gda_r20221027&jk=1849271569829695&bg=!Xl2lXRnNAAZPh4lnb4c7ACkAdvg8WmMVdibKNhW-3iKupc0NxRJQ6x7itsSj0lwkOmleojRI7ue89QIAAAEEUgAAAAloAQeZAvJZdhuHBdD2t-KV1LDZHDh0LYKDL3II_-MK8744bQJfRXkFYcsyweczfnjv2SaKRSQGXqHVz25QjG0H_aNKGCov6dTSQsjHk0eR_ULVPcRWJceTF-pEYbSu1nK5_0jrOlAVCKQGWKJy20c0lPzsyZyQKssiTHxnVTNCF-tsTGGsR-cveb0WkR_Eb3ipIspL9D0zx6ZWMGIU8wjXX_RcKvV8rIsSRnwCiSRyWIBYinopM36XY1-3pIiJL6Gcc6wNCoOPdrFdYOJRBLfKNkENLLca-TMfOQ28n_oj7EBuHll-VmrCMGDC-6P9tsBkg7e7Up2rzXnoorw1PZQuH2FCbNHSLqwbeD9zKrDNyE6fw-roEYbpnlxlZsXt7ztbDE2CY2hXQVfYwhSTQh8BaNhIArzwU4bYJ0KfTqYmumhj4-BysmFThOJFYHLiHij-a4ebkMNcBdQmQOTGAcmT4bIKzvU_Z2I2JbFEvJccrZJujN2l8rnBxEHE5N_eqHgUGHZ4rr4lKWB6d0QS98dEvyNFPDETZDIBpKPn7KtxwWrac5dl7Vi9PWTTUU1JT2aVaIQ-FWLJ_tJHWlVr7J1bCTPRBp6Iar767zmgMs9v0c9kk3b24MXmBOCqeNRuK_fk1pnQqmR7LRjCJhfrnoCLmu6KMy9zxA80r-VBAwoxm3-i05R1mQtYuzwaRJnA2pGJhRAqFdrdo5Kx4rsoN6lnxBnP2qmzaagxykUKVx0WoI54aUMsOGGBCjKElixo7YsByDxxX6ZXcIA1rvnd8UY1oKgZcfuBChn8Ha78Jii4nL7xqSpvv63YAmwunJgkeb7Kda98KfsglzRDX4i3IJ0SE437eQsJpP8nmU6Bke6CS50m5niGWXUuanu0DJJ0g0CuLHYlqECc2JQBfZue-BcNfQkgwYu601HPlgINA0_mV7J9Rjk0-UAgr65xZhYxJ4g6KI2SoU6FQdMTHgziUfRL5bJTD6Cyqnq7xb49YsoMfqKjyTLYuipb
h2
2915.1159999892
2922.8810002096
516
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
118.175
14.28
408.023
6.732
419.044
78.508
497.625
21.713
530.365
11.574
544.798
10.367
558.192
50.526
619.933
8.226
628.817
5.199
660.521
8.163
671.733
103.266
783.792
6.993
791.712
12.906
804.643
15.556
820.226
7.776
859.283
6.037
870.229
12.264
944.003
5.819
1168.988
5.407
1551.715
456.561
2009.531
8.295
2039.045
12.083
2061.927
10.262
2072.325
11.181
2114.779
32.217
2150.771
11.583
2163.14
11.625
2174.856
11.522
2186.433
13.312
2200.806
8.571
2213.308
33.925
2247.571
8.376
2256.971
24.301
2282.219
11.869
2294.935
20.309
2316.117
16.428
2334.883
12.313
2348.185
15.045
2364.337
11.655
2376.972
13.867
2894.923
10.875
2906.266
10.709
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.6 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 6.2 s
The time taken for the page to become fully interactive.
Largest Contentful Paint — 2.6 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 2.6 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused CSS — Potential savings of 36 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Paypou.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://paypou.com/webroot/css/bootstrap.min.css
25559
24848
https://paypou.com/webroot/css/all.min.css
11915
11793
Serve images in next-gen formats — Potential savings of 15 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://paypou.com/webroot/images/logo.png
15526
14934.25
Serve static assets with an efficient cache policy — 6 resources found
Paypou.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
14400000
17915
https://paypou.com/webroot/images/titleBorder.svg
14400000
1102
https://paypou.com/webroot/js/bootstrap.min.js
43200000
16207
https://paypou.com/webroot/css/all.min.css
43200000
11915
https://paypou.com/webroot/js/front.app.js
43200000
1360
https://paypou.com/webroot/images/logo.png
2592000000
16251

Metrics

Total Blocking Time — 1,400 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

Max Potential First Input Delay — 910 ms
Users could experience a delay when interacting with the page.

Other

Eliminate render-blocking resources — Potential savings of 1,850 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Paypou.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://paypou.com/webroot/css/bootstrap.min.css
25559
780
https://paypou.com/webroot/css/style.css
5291
150
https://fonts.googleapis.com/css?family=Open+Sans:300,300i,400,400i,600,600i,700,700i,800,800i|Roboto:100,100i,300,300i,400,400i,500,500i,700,700i,900,900i
2769
780
Reduce unused JavaScript — Potential savings of 130 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js?bust=31070606
119762
81562
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
56078
28979
https://paypou.com/webroot/js/jquery.min.js
32698
22968
Reduce JavaScript execution time — 3.9 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
1903.428
1811.944
8.268
https://tpc.googlesyndication.com/sodar/sodar2/225/runner.html
1039.176
976.188
12.488
http://paypou.com/
719.824
64.084
16.66
https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202210260101/show_ads_impl_fy2021.js?bust=31070606
445.092
408.3
25.372
Unattributable
282.568
8.428
0
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
211.612
187.38
14.74
https://pagead2.googlesyndication.com/bg/PTWQOrfCOp17EyrMcPeT6PfhP85_faJCCfTgkqMfTIQ.js
126.676
115.868
9.456
https://tpc.googlesyndication.com/sodar/sodar2.js
109.904
100.444
2.06
https://paypou.com/webroot/js/jquery.min.js
85.472
71.528
7.168
https://www.google.com/recaptcha/api2/aframe
61.24
16.98
6.944
https://googleads.g.doubleclick.net/pagead/html/r20221027/r20190131/zrt_lookup.html
58.5
22.04
10.544
Minimize main-thread work — 5.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
3824.448
Other
507.364
Style & Layout
459.364
Script Parsing & Compilation
125.88
Parse HTML & CSS
95.1
Rendering
94.384
Garbage Collection
78.488
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
4.874000325799
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
3.8430001586676
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.2790000550449
https://paypou.com/webroot/fonts/fa-brands-400.woff2
92.301999684423
https://paypou.com/webroot/fonts/fa-solid-900.woff2
79.258000012487
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
3.1619998626411
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
4.4639999978244
https://paypou.com/webroot/fonts/fa-solid-900.woff
130.35600027069
https://paypou.com/webroot/fonts/fa-brands-400.woff
626.04499980807
https://paypou.com/webroot/fonts/fa-solid-900.ttf
116.26200005412
https://paypou.com/webroot/fonts/fa-brands-400.ttf
841.72799997032
Reduce the impact of third-party code — Third-party code blocked the main thread for 590 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
226511
587.396
91079
0
1425
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://paypou.com/webroot/images/logo.png
First Contentful Paint (3G) — 5190 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
75

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of paypou.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Paypou.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Contrast

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
67

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that paypou.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.5.0
jQuery
3.5.1
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://paypou.com/webroot/js/bootstrap.min.js
https://paypou.com/webroot/js/bootstrap.min.js.map
https://pagead2.googlesyndication.com/bg/PTWQOrfCOp17EyrMcPeT6PfhP85_faJCCfTgkqMfTIQ.js
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 4 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://paypou.com/
Allowed
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1667361600
Allowed
http://paypou.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
Allowed
http://paypou.com/cdn-cgi/challenge-platform/h/b/cv/result/763a827f589c9c55
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://paypou.com/webroot/images/logo.png
40 x 40
40 x 40
80 x 80

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
`window.webkitStorageInfo` is deprecated. Please use `navigator.webkitTemporaryStorage` or `navigator.webkitPersistentStorage` instead.
...
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Access to font at 'https://paypou.com/webroot/fonts/fa-brands-400.ttf' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-brands-400.woff' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-brands-400.woff2' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-solid-900.ttf' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-solid-900.woff' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://paypou.com/webroot/fonts/fa-solid-900.woff2' from origin 'http://paypou.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for paypou.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of paypou.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 93% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
32x41

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
30

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of paypou.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of paypou.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 104.21.95.110
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: REDACTED FOR PRIVACY
Country: NZ
City: REDACTED FOR PRIVACY
State: Auckland District
Post Code: REDACTED FOR PRIVACY
Email: info@domain-contact.org
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Instra Corporation Pty Ltd. 104.18.22.137
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: paypou.com
Issued By: GTS CA 1P5
Valid From: 20th February, 2024
Valid To: 20th May, 2024
Subject: CN = paypou.com
Hash: ddd9df87
Issuer: CN = GTS CA 1P5
O = Google Trust Services LLC
S = US
Version: 2
Serial Number: 0xD87D5E7BDD1588B70EE6531F1E2006C6
Serial Number (Hex): D87D5E7BDD1588B70EE6531F1E2006C6
Valid From: 20th February, 2024
Valid To: 20th May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:D5:FC:9E:0D:DF:1E:CA:DD:08:97:97:6E:2B:C5:5F:C5:2B:F5:EC:B8
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://crls.pki.goog/gts1p5/UbXMIdXm_2k.crl

Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.11129.2.5.3

Authority Information Access: OCSP - URI:http://ocsp.pki.goog/s/gts1p5/CjlwYESphWA
CA Issuers - URI:http://pki.goog/repo/certs/gts1p5.der

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
Timestamp : Feb 20 18:48:58.135 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:FB:DA:4F:54:5B:A3:F4:BC:D1:99:04:
F2:5B:42:0B:42:34:B9:32:33:59:E4:7B:96:86:BC:C4:
41:90:D0:3F:CD:02:21:00:F7:11:38:81:9A:2B:5E:E6:
CE:C6:0A:1D:0E:88:11:06:1E:96:D0:DC:DE:02:FE:72:
A9:41:60:EE:50:20:77:AD
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DA:B6:BF:6B:3F:B5:B6:22:9F:9B:C2:BB:5C:6B:E8:70:
91:71:6C:BB:51:84:85:34:BD:A4:3D:30:48:D7:FB:AB
Timestamp : Feb 20 18:48:58.151 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:17:37:5C:5F:96:62:86:44:5E:70:82:65:
D4:F2:08:76:D4:0A:B4:66:1E:AA:E4:33:09:F8:6E:B2:
56:4F:B7:E0:02:20:23:7E:29:04:98:C3:70:C7:24:19:
EF:44:08:79:AA:B7:B2:43:41:B0:E5:0B:8D:BA:27:74:
8D:93:F7:D3:A7:88
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.paypou.com
DNS:paypou.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 12th April, 2024
Content-Type: text/html; charset=UTF-8
Server: cloudflare
Connection: keep-alive
Vary: Accept-Encoding
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=G6cUpDK6N1cg4WojoIqg72QRFva9orbMta9X9f2YqpJOB3gpsH9GJlbQXsbVo3tuashlDpUeVyToPJpRH9edhj3qcQafu7oLSPS0wrjQMxjxvG9rW75bXyIcXmNX"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 8732213b8d713928-IAD
alt-svc: h3=":443"; ma=86400

Whois Lookup

Created: 24th November, 2019
Changed: 17th September, 2023
Expires: 24th November, 2024
Registrar: Instra Corporation Pty Ltd.
Status: ok
Nameservers: lola.ns.cloudflare.com
simon.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: Auckland District
Owner Country: NZ
Owner Phone: REDACTED FOR PRIVACY
Owner Email: info@domain-contact.org
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: info@domain-contact.org
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: info@domain-contact.org
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Billing Post Code: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Email: info@domain-contact.org
Full Whois: Domain Name: paypou.com
Registry Domain ID: 2459068823_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.instra.net
Registrar URL: http://www.instra.com
Updated Date: 2023-09-17T18:04:37Z
Creation Date: 2019-11-24T16:20:36Z
Registrar Registration Expiration Date: 2024-11-24T16:20:36Z
Registrar: Instra Corporation Pty Ltd.
Registrar IANA ID: 1376
Registrar Abuse Contact Email: abuse@instra.com
Registrar Abuse Contact Phone: +61.397831800
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Auckland District
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: NZ
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: info@domain-contact.org
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: info@domain-contact.org
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: info@domain-contact.org
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Phone Ext: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Fax Ext: REDACTED FOR PRIVACY
Billing Email: info@domain-contact.org
Name Server: lola.ns.cloudflare.com
Name Server: simon.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: https://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-04-12T09:18:36Z <<<

For more information on Whois status codes, please visit https://www.icann.org/epp

To contact the registered registrant please proceed to:
https://www.domain-contact.org

Please register your domains at; http://www.instra.com
This data is provided by Instra Corporation Pty Ltd.
for information purposes, and to assist persons obtaining information
about or related to domain name registration records.
Instra Corporation Pty Ltd. does not guarantee its accuracy.
By submitting a WHOIS query, you agree that you will use this data
only for lawful purposes and that, under no circumstances, you will
use this data to
1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via E-mail
(spam) or
2) enable high volume, automated, electronic processes that apply
to this WHOIS server.
These terms may be changed without prior notice.
By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
lola.ns.cloudflare.com 173.245.58.132
simon.ns.cloudflare.com 172.64.33.232
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address