betpawa.com

betpawa.com is SSL secured

Free website and domain report on betpawa.com

Last Updated: 10th October, 2023 Update Now
Overview

Snoop Summary for betpawa.com

This is a free and comprehensive report about betpawa.com. The domain betpawa.com is currently hosted on a server located in Germany with the IP address 167.233.8.194, where the local currency is EUR and German is the local language. Our records indicate that betpawa.com is owned/operated by Identity Protection Service. Betpawa.com has the potential to be earning an estimated $5 USD per day from advertising revenue. If betpawa.com was to be sold it would possibly be worth $3,339 USD (based on the daily revenue potential of the website over a 24 month period). Betpawa.com receives an estimated 1,600 unique visitors every day - a large amount of traffic! This report was last updated 10th October, 2023.

About betpawa.com

Site Preview: betpawa.com betpawa.com
Title: betPawa.com | Online sports betting
Description: The best online sports betting! betPawa.com is licensed by the Lotteries
Keywords and Tags: betpawa, betpawa com, betpawa kenya, betpawa kenya paybill number, betpawa login, betpawa ng, betpawa ug, betpawa ug login, pawabet, pawabet ug, sports, www betpawa com, www betpawa com login page, www pawa com
Related Terms: lotteries, oz lotteries
Fav Icon:
Age: Over 9 years old
Domain Created: 21st April, 2014
Domain Updated: 21st December, 2022
Domain Expires: 21st April, 2023
Review

Snoop Score

2/5

Valuation

$3,339 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 496,270
Alexa Reach:
SEMrush Rank (US): 760,669
SEMrush Authority Score: 37
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 255 0
Traffic: 1,277 0
Cost: $3,848 USD $0 USD
Traffic

Visitors

Daily Visitors: 1,600
Monthly Visitors: 48,699
Yearly Visitors: 584,000
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $5 USD
Monthly Revenue: $139 USD
Yearly Revenue: $1,664 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 498
Referring Domains: 134
Referring IPs: 125
Betpawa.com has 498 backlinks according to SEMrush. 23% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve betpawa.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
99% of betpawa.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://soccerbettingtipsandpredictions.com/2020/04/01/best-soccer-bets-wed-sat-6/
Target: https://www.ke.betpawa.com/accept-odds-changes

2
Source: http://lire.me/search/Zulu-bet.com::%7C::Password/doc/1
Target: https://www.betpawa.com/

3
Source: https://kenyanbets.co.ke/
Target: https://www.ke.betpawa.com/

4
Source: http://betpawa.com.vlink88.com/goto/
Target: http://betpawa.com/

5
Source: http://betpawa.com.vlink88.com/goto/
Target: http://betpawa.com/

Top Ranking Keywords (US)

1
Keyword: betpawa
Ranked Page: https://www.betpawa.com/

2
Keyword: www betpawa com
Ranked Page: https://www.betpawa.com/

3
Keyword: betpawa ug
Ranked Page: https://www.betpawa.com/

4
Keyword: betpawa com
Ranked Page: https://www.betpawa.com/

5
Keyword: pawabet
Ranked Page: https://www.betpawa.com/

Domain Analysis

Value Length
Domain: betpawa.com 11
Domain Name: betpawa 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 72
Performance 100
Accessibility 66
Best Practices 92
SEO 82
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
100

Performance

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

Metrics

First Contentful Paint — 0.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.3 s
The time taken for the page to become fully interactive.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 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.6 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.045
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.3 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://betpawa.com/
http/1.1
0
252.95800017193
226
0
301
text/html
https://betpawa.com/
h2
253.29999998212
611.5970001556
2505
8795
200
text/html
Document
https://betpawa.com/style.css
h2
617.93399997987
975.74699996039
1376
3990
200
text/css
Stylesheet
https://betpawa.com/images/logo_monochrome.png
h2
618.09900007211
975.33100005239
2574
2219
200
image/png
Image
https://static.betpawa.com/fonts/Roboto_italic_fonts
h2
976.91600001417
1170.8410000429
10090
9225
200
binary/octet-stream
Stylesheet
https://betpawa.com/api/brand/v1/countries/betpawa
h2
981.67899996042
1227.8760001063
453
1465
200
application/json
XHR
https://betpawa.com/images/my-betpawa.jpg
h2
982.78099996969
1228.2780001406
15101
14744
200
image/jpeg
Image
https://betpawa.com/images/betpawa-uganda.png
h2
1230.5570000317
1565.1559999678
3203
2848
200
image/png
Image
https://betpawa.com/images/betpawa-nigeria.png
h2
1230.6600001175
1348.466000054
1472
1117
200
image/png
Image
https://betpawa.com/images/betpawa-kenya.png
h2
1230.9970001224
1565.671000164
3653
3298
200
image/png
Image
https://betpawa.com/images/betpawa-tanzania.png
h2
1231.306000147
1349.1950000171
3629
3274
200
image/png
Image
https://betpawa.com/images/betpawa-zambia.png
h2
1231.514000101
1671.6760001145
3119
2764
200
image/png
Image
https://betpawa.com/images/betpawa-ghana.png
h2
1231.722000055
1344.7249999736
2900
2545
200
image/png
Image
https://betpawa.com/images/betpawa-cameroon.png
h2
1232.093000086
1347.7100001182
2380
2025
200
image/png
Image
https://betpawa.com/images/betpawa-drc.png
h2
1232.3060000781
1348.1690001208
1971
1616
200
image/png
Image
https://betpawa.com/images/betpawa-rwanda.png
h2
1232.6110000722
1671.280000126
2942
2587
200
image/png
Image
https://betpawa.com/images/betpawa-malawi.png
h2
1232.9639999662
1346.908000065
3865
3510
200
image/png
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)
615.821
7.866
982.53
8.874
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

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Betpawa.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Betpawa.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Betpawa.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Betpawa.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Betpawa.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Betpawa.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 8 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.betpawa.com/fonts/Roboto_italic_fonts
9225
8456
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 360 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)
https://betpawa.com/
359.293
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Betpawa.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://betpawa.com/
190
https://betpawa.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Betpawa.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.
URL Potential Savings (Ms)
https://betpawa.com/images/my-betpawa.jpg
0
Avoids enormous network payloads — Total size was 60 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://betpawa.com/images/my-betpawa.jpg
15101
https://static.betpawa.com/fonts/Roboto_italic_fonts
10090
https://betpawa.com/images/betpawa-malawi.png
3865
https://betpawa.com/images/betpawa-kenya.png
3653
https://betpawa.com/images/betpawa-tanzania.png
3629
https://betpawa.com/images/betpawa-uganda.png
3203
https://betpawa.com/images/betpawa-zambia.png
3119
https://betpawa.com/images/betpawa-rwanda.png
2942
https://betpawa.com/images/betpawa-ghana.png
2900
https://betpawa.com/images/logo_monochrome.png
2574
Avoids an excessive DOM size — 39 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
39
Maximum DOM Depth
5
Maximum Child Elements
10
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Betpawa.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
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.
Minimizes main-thread work — 0.1 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)
Other
23.611
Script Evaluation
11.267
Style & Layout
9.964
Rendering
5.135
Parse HTML & CSS
1.961
Script Parsing & Compilation
1.747
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 17 requests • 60 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
17
61459
Image
12
46809
Stylesheet
2
11466
Document
1
2505
Other
2
679
Media
0
0
Font
0
0
Script
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.044314569666108
0.00031455212707948
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
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 betpawa.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.

Other

Serve static assets with an efficient cache policy — 14 resources found
Betpawa.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)
https://betpawa.com/images/my-betpawa.jpg
0
15101
https://static.betpawa.com/fonts/Roboto_italic_fonts
0
10090
https://betpawa.com/images/betpawa-malawi.png
0
3865
https://betpawa.com/images/betpawa-kenya.png
0
3653
https://betpawa.com/images/betpawa-tanzania.png
0
3629
https://betpawa.com/images/betpawa-uganda.png
0
3203
https://betpawa.com/images/betpawa-zambia.png
0
3119
https://betpawa.com/images/betpawa-rwanda.png
0
2942
https://betpawa.com/images/betpawa-ghana.png
0
2900
https://betpawa.com/images/logo_monochrome.png
0
2574
https://betpawa.com/images/betpawa-cameroon.png
0
2380
https://betpawa.com/images/betpawa-drc.png
0
1971
https://betpawa.com/images/betpawa-nigeria.png
0
1472
https://betpawa.com/style.css
0
1376

Other

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://betpawa.com/images/logo_monochrome.png
66

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of betpawa.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.
Heading elements appear 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.
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"]`
Betpawa.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that betpawa.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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request 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://betpawa.com/
Allowed
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for betpawa.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 betpawa.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.

Crawling and Indexing

robots.txt is not valid — 339 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE html>
Syntax not understood
2
<html>
Syntax not understood
3
<head>
Syntax not understood
4
<meta charset="UTF-8">
Syntax not understood
5
<link href='https://static.betpawa.com/fonts/Roboto_italic_fonts' rel='stylesheet' type='text/css'
Unknown directive
6
media="none"
Syntax not understood
7
onload="if(media!='all')media='all'">
Syntax not understood
8
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
Syntax not understood
9
<meta name="viewport" content="width=device-width, initial-scale=1">
Syntax not understood
10
<title>betPawa.com | Online sports betting</title>
Syntax not understood
11
<meta name="description" content="The best online sports betting! betPawa.com is licensed by the Lotteries">
Syntax not understood
12
<link rel="icon" type="image/png" sizes="16x16" href="./images/favicon.png">
Syntax not understood
13
<link href="./style.css" rel="stylesheet" type="text/css">
Syntax not understood
14
<script>
Syntax not understood
15
preinit();
Syntax not understood
17
function preinit() {
Syntax not understood
18
var isBack = window.location.pathname === '/return';
Syntax not understood
19
if (isBack) {
Syntax not understood
20
setCookie('');
Syntax not understood
21
} else {
Syntax not understood
22
var domain = getCookie();
Syntax not understood
23
if (domain) {
Syntax not understood
24
window.location.href = domain;
Syntax not understood
25
}
Syntax not understood
26
}
Syntax not understood
27
}
Syntax not understood
29
function getCookie() {
Syntax not understood
30
var cVal = document.cookie.match('(?:^|;) ?BetpawaCountry=([^;]*)(?:;|$)');
Unknown directive
31
if (!cVal) {
Syntax not understood
32
return null;
Syntax not understood
33
} else {
Syntax not understood
34
return cVal[1];
Syntax not understood
35
}
Syntax not understood
36
}
Syntax not understood
38
function setCookie(cvalue) {
Syntax not understood
39
var d = new Date();
Syntax not understood
40
d.setTime(d.getTime() + (365 * 24 * 60 * 60 * 1000));
Syntax not understood
41
var expires = "expires=" + d.toUTCString();
Syntax not understood
42
document.cookie = "BetpawaCountry=" + cvalue + "; " + expires;
Syntax not understood
43
}
Syntax not understood
44
</script>
Syntax not understood
45
</head>
Syntax not understood
46
<body>
Syntax not understood
47
<section class="intro">
Syntax not understood
48
<!--<div class="container">-->
Syntax not understood
49
<!--<div class="column first">-->
Syntax not understood
50
<!--<img class="logo" src="https://static.betpawa.com/img/landing/logo_color.png">-->
Unknown directive
51
<!--<p>Bet small win BIG</p>-->
Syntax not understood
52
<!--</div>-->
Syntax not understood
53
<!--<div class="column second"></div>-->
Syntax not understood
54
<!--</div>-->
Syntax not understood
55
</section>
Syntax not understood
56
<div class="gallery">
Syntax not understood
57
<h3>Select your country</h3>
Syntax not understood
58
<div id="country-select" class="container"></div>
Syntax not understood
59
</div>
Syntax not understood
61
<footer>
Syntax not understood
62
<img src="./images/logo_monochrome.png">
Syntax not understood
63
<div>&copy; betPawa <span id="js-year">2019</span>. All Rights reserved</div>
Syntax not understood
64
</footer>
Syntax not understood
65
</body>
Syntax not understood
66
<script type="text/javascript">
Syntax not understood
67
var $countrySelect = window.document.getElementById('country-select');
Syntax not understood
68
var $year = window.document.getElementById('js-year');
Syntax not understood
69
var countries = [
Syntax not understood
70
{
Syntax not understood
71
countryIso2Code: 'DZ',
Unknown directive
72
countryName: 'Algeria'
Unknown directive
73
},
Syntax not understood
74
{
Syntax not understood
75
countryIso2Code: 'AO',
Unknown directive
76
countryName: 'Angola'
Unknown directive
77
},
Syntax not understood
78
{
Syntax not understood
79
countryIso2Code: 'BJ',
Unknown directive
80
countryName: 'Benin'
Unknown directive
81
},
Syntax not understood
82
{
Syntax not understood
83
countryIso2Code: 'BW',
Unknown directive
84
countryName: 'Botswana'
Unknown directive
85
},
Syntax not understood
86
{
Syntax not understood
87
countryIso2Code: 'BF',
Unknown directive
88
countryName: 'Burkina Faso'
Unknown directive
89
},
Syntax not understood
90
{
Syntax not understood
91
countryIso2Code: 'BI',
Unknown directive
92
countryName: 'Burundi'
Unknown directive
93
},
Syntax not understood
94
{
Syntax not understood
95
countryIso2Code: 'CM',
Unknown directive
96
countryName: 'Cameroon'
Unknown directive
97
},
Syntax not understood
98
{
Syntax not understood
99
countryIso2Code: 'CV',
Unknown directive
100
countryName: 'Cape Verde'
Unknown directive
101
},
Syntax not understood
102
{
Syntax not understood
103
countryIso2Code: 'CF',
Unknown directive
104
countryName: 'Central African Republic'
Unknown directive
105
},
Syntax not understood
106
{
Syntax not understood
107
countryIso2Code: 'TD',
Unknown directive
108
countryName: 'Chad'
Unknown directive
109
},
Syntax not understood
110
{
Syntax not understood
111
countryIso2Code: 'KM',
Unknown directive
112
countryName: 'Comoros'
Unknown directive
113
},
Syntax not understood
114
{
Syntax not understood
115
countryIso2Code: 'CG',
Unknown directive
116
countryName: 'Congo'
Unknown directive
117
},
Syntax not understood
118
{
Syntax not understood
119
countryIso2Code: 'CD',
Unknown directive
120
countryName: 'DR Congo'
Unknown directive
121
},
Syntax not understood
122
{
Syntax not understood
123
countryIso2Code: 'CI',
Unknown directive
124
countryName: 'Cote d’Ivoire'
Unknown directive
125
},
Syntax not understood
126
{
Syntax not understood
127
countryIso2Code: 'DJ',
Unknown directive
128
countryName: 'Djibouti'
Unknown directive
129
},
Syntax not understood
130
{
Syntax not understood
131
countryIso2Code: 'EG',
Unknown directive
132
countryName: 'Egypt'
Unknown directive
133
},
Syntax not understood
134
{
Syntax not understood
135
countryIso2Code: 'GQ',
Unknown directive
136
countryName: 'Equatorial Guinea'
Unknown directive
137
},
Syntax not understood
138
{
Syntax not understood
139
countryIso2Code: 'ER',
Unknown directive
140
countryName: 'Eritrea'
Unknown directive
141
},
Syntax not understood
142
{
Syntax not understood
143
countryIso2Code: 'ET',
Unknown directive
144
countryName: 'Ethiopia'
Unknown directive
145
},
Syntax not understood
146
{
Syntax not understood
147
countryIso2Code: 'GA',
Unknown directive
148
countryName: 'Gabon'
Unknown directive
149
},
Syntax not understood
150
{
Syntax not understood
151
countryIso2Code: 'GM',
Unknown directive
152
countryName: 'Gambia'
Unknown directive
153
},
Syntax not understood
154
{
Syntax not understood
155
countryIso2Code: 'GH',
Unknown directive
156
countryName: 'Ghana'
Unknown directive
157
},
Syntax not understood
158
{
Syntax not understood
159
countryIso2Code: 'GN',
Unknown directive
160
countryName: 'Guinea'
Unknown directive
161
},
Syntax not understood
162
{
Syntax not understood
163
countryIso2Code: 'GW',
Unknown directive
164
countryName: 'Guinea-Bissau'
Unknown directive
165
},
Syntax not understood
166
{
Syntax not understood
167
countryIso2Code: 'KE',
Unknown directive
168
countryName: 'Kenya'
Unknown directive
169
},
Syntax not understood
170
{
Syntax not understood
171
countryIso2Code: 'LS',
Unknown directive
172
countryName: 'Lesotho'
Unknown directive
173
},
Syntax not understood
174
{
Syntax not understood
175
countryIso2Code: 'LR',
Unknown directive
176
countryName: 'Liberia'
Unknown directive
177
},
Syntax not understood
178
{
Syntax not understood
179
countryIso2Code: 'LY',
Unknown directive
180
countryName: 'Libyan Arab Jamahiriya'
Unknown directive
181
},
Syntax not understood
182
{
Syntax not understood
183
countryIso2Code: 'MG',
Unknown directive
184
countryName: 'Madagascar'
Unknown directive
185
},
Syntax not understood
186
{
Syntax not understood
187
countryIso2Code: 'ML',
Unknown directive
188
countryName: 'Mali'
Unknown directive
189
},
Syntax not understood
190
{
Syntax not understood
191
countryIso2Code: 'MW',
Unknown directive
192
countryName: 'Malawi'
Unknown directive
193
},
Syntax not understood
194
{
Syntax not understood
195
countryIso2Code: 'MR',
Unknown directive
196
countryName: 'Mauritania'
Unknown directive
197
},
Syntax not understood
198
{
Syntax not understood
199
countryIso2Code: 'MU',
Unknown directive
200
countryName: 'Mauritius'
Unknown directive
201
},
Syntax not understood
202
{
Syntax not understood
203
countryIso2Code: 'YT',
Unknown directive
204
countryName: 'Mayotte'
Unknown directive
205
},
Syntax not understood
206
{
Syntax not understood
207
countryIso2Code: 'MA',
Unknown directive
208
countryName: 'Morocco'
Unknown directive
209
},
Syntax not understood
210
{
Syntax not understood
211
countryIso2Code: 'MZ',
Unknown directive
212
countryName: 'Mozambique'
Unknown directive
213
},
Syntax not understood
214
{
Syntax not understood
215
countryIso2Code: 'NA',
Unknown directive
216
countryName: 'Namibia'
Unknown directive
217
},
Syntax not understood
218
{
Syntax not understood
219
countryIso2Code: 'NE',
Unknown directive
220
countryName: 'Niger'
Unknown directive
221
},
Syntax not understood
222
{
Syntax not understood
223
countryIso2Code: 'NG',
Unknown directive
224
countryName: 'Nigeria'
Unknown directive
225
},
Syntax not understood
226
{
Syntax not understood
227
countryIso2Code: 'RE',
Unknown directive
228
countryName: 'Reunion Island'
Unknown directive
229
},
Syntax not understood
230
{
Syntax not understood
231
countryIso2Code: 'RW',
Unknown directive
232
countryName: 'Rwanda'
Unknown directive
233
},
Syntax not understood
234
{
Syntax not understood
235
countryIso2Code: 'ST',
Unknown directive
236
countryName: 'Sao Tome and Principe'
Unknown directive
237
},
Syntax not understood
238
{
Syntax not understood
239
countryIso2Code: 'SN',
Unknown directive
240
countryName: 'Senegal'
Unknown directive
241
},
Syntax not understood
242
{
Syntax not understood
243
countryIso2Code: 'SC',
Unknown directive
244
countryName: 'Seychelles'
Unknown directive
245
},
Syntax not understood
246
{
Syntax not understood
247
countryIso2Code: 'SL',
Unknown directive
248
countryName: 'Sierra Leone'
Unknown directive
249
},
Syntax not understood
250
{
Syntax not understood
251
countryIso2Code: 'SO',
Unknown directive
252
countryName: 'Somalia'
Unknown directive
253
},
Syntax not understood
254
{
Syntax not understood
255
countryIso2Code: 'ZA',
Unknown directive
256
countryName: 'South Africa'
Unknown directive
257
},
Syntax not understood
258
{
Syntax not understood
259
countryIso2Code: 'SS',
Unknown directive
260
countryName: 'South Sudan'
Unknown directive
261
},
Syntax not understood
262
{
Syntax not understood
263
countryIso2Code: 'SD',
Unknown directive
264
countryName: 'Sudan'
Unknown directive
265
},
Syntax not understood
266
{
Syntax not understood
267
countryIso2Code: 'SZ',
Unknown directive
268
countryName: 'Swaziland'
Unknown directive
269
},
Syntax not understood
270
{
Syntax not understood
271
countryIso2Code: 'TZ',
Unknown directive
272
countryName: 'Tanzania'
Unknown directive
273
},
Syntax not understood
274
{
Syntax not understood
275
countryIso2Code: 'TG',
Unknown directive
276
countryName: 'Togo'
Unknown directive
277
},
Syntax not understood
278
{
Syntax not understood
279
countryIso2Code: 'TN',
Unknown directive
280
countryName: 'Tunisia'
Unknown directive
281
},
Syntax not understood
282
{
Syntax not understood
283
countryIso2Code: 'UG',
Unknown directive
284
countryName: 'Uganda'
Unknown directive
285
},
Syntax not understood
286
{
Syntax not understood
287
countryIso2Code: 'EH',
Unknown directive
288
countryName: 'Western Sahara'
Unknown directive
289
},
Syntax not understood
290
{
Syntax not understood
291
countryIso2Code: 'ZM',
Unknown directive
292
countryName: 'Zambia'
Unknown directive
293
},
Syntax not understood
294
{
Syntax not understood
295
countryIso2Code: 'ZW',
Unknown directive
296
countryName: 'Zimbabwe'
Unknown directive
297
},
Syntax not understood
298
];
Syntax not understood
300
init();
Syntax not understood
302
function init() {
Syntax not understood
303
$year.innerText = (new Date()).getFullYear().toString();
Syntax not understood
304
loadJurisdictions(renderCountries);
Syntax not understood
305
}
Syntax not understood
307
function renderCountries(data) {
Syntax not understood
308
var html = '';
Syntax not understood
309
for (var i = 0; i < data.length; i++) {
Syntax not understood
310
if (!data[i].landingPageActive) continue;
Syntax not understood
312
var country;
Syntax not understood
313
for (var j = 0; j < countries.length; j++) {
Syntax not understood
314
if (countries[j].countryIso2Code === data[i].countryIso2Code) {
Syntax not understood
315
country = countries[j];
Syntax not understood
316
}
Syntax not understood
317
}
Syntax not understood
319
html +=
Syntax not understood
320
'<a href="https://www.' + data[i].rootDomain + '" class="thumbnail" onclick="return clickLink(\'https://www.' + data[i].rootDomain + '\')">' +
Unknown directive
321
'<img src="./images/' + data[i].brandIdentifier + '.png">' +
Syntax not understood
322
'<h4>' + country.countryName + '</h4>' +
Syntax not understood
323
'</a>';
Syntax not understood
324
}
Syntax not understood
325
$countrySelect.innerHTML = html;
Syntax not understood
326
}
Syntax not understood
328
function clickLink(url) {
Syntax not understood
329
setCookie(url);
Syntax not understood
330
window.location.href = url;
Syntax not understood
331
return false;
Syntax not understood
332
}
Syntax not understood
334
function loadJurisdictions(callbackFn) {
Syntax not understood
335
var xmlhttp = new XMLHttpRequest();
Syntax not understood
336
var url = "/api/brand/v1/countries/betpawa";
Syntax not understood
338
xmlhttp.onreadystatechange = function (result) {
Syntax not understood
339
if (this.readyState === 4 && this.status === 200) {
Syntax not understood
340
try {
Syntax not understood
341
callbackFn(JSON.parse(result.currentTarget.response));
Syntax not understood
342
} catch (e) {
Syntax not understood
343
}
Syntax not understood
344
}
Syntax not understood
345
};
Syntax not understood
347
xmlhttp.open("GET", url, true);
Syntax not understood
348
xmlhttp.setRequestHeader('accept', 'application/json');
Syntax not understood
349
xmlhttp.send();
Syntax not understood
350
}
Syntax not understood
351
</script>
Syntax not understood
352
</html>
Syntax not understood

Content Best Practices

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 betpawa.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 betpawa.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) 72
Performance 98
Accessibility 66
Best Practices 83
SEO 85
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://betpawa.com/
Updated: 3rd January, 2023

5.46 seconds
First Contentful Paint (FCP)
30%
25%
45%

0.04 seconds
First Input Delay (FID)
83%
11%
6%

Simulate loading on mobile
98

Performance

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

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Speed Index — 2.4 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 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 — 1.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.093
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.1 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://betpawa.com/
http/1.1
0
242.35900002532
226
0
301
text/html
https://betpawa.com/
h2
242.77500004973
633.93899996299
2505
8795
200
text/html
Document
https://betpawa.com/style.css
h2
645.46699996572
996.04100000579
1376
3990
200
text/css
Stylesheet
https://betpawa.com/images/logo_monochrome.png
h2
645.70100000128
778.79300003406
2574
2219
200
image/png
Image
https://static.betpawa.com/fonts/Roboto_italic_fonts
h2
780.74199997354
1164.4350000424
10113
9225
200
binary/octet-stream
Stylesheet
https://betpawa.com/api/brand/v1/countries/betpawa
h2
1002.6960000396
1153.1670000404
453
1465
200
application/json
XHR
https://betpawa.com/images/my-betpawa.jpg
h2
1005.8539999882
1449.3520000251
15101
14744
200
image/jpeg
Image
https://betpawa.com/images/betpawa-uganda.png
h2
1156.4879999496
1365.7710000407
3203
2848
200
image/png
Image
https://betpawa.com/images/betpawa-nigeria.png
h2
1156.9300000556
1448.6480000196
1472
1117
200
image/png
Image
https://betpawa.com/images/betpawa-kenya.png
h2
1157.2490000399
1265.0979999453
3653
3298
200
image/png
Image
https://betpawa.com/images/betpawa-tanzania.png
h2
1157.9950000159
1265.8300000476
3629
3274
200
image/png
Image
https://betpawa.com/images/betpawa-zambia.png
h2
1158.1680000527
1266.6889999527
3119
2764
200
image/png
Image
https://betpawa.com/images/betpawa-ghana.png
h2
1158.4690000163
1449.0259999875
2900
2545
200
image/png
Image
https://betpawa.com/images/betpawa-cameroon.png
h2
1158.7270000018
1265.5660000164
2380
2025
200
image/png
Image
https://betpawa.com/images/betpawa-drc.png
h2
1158.9420000091
1293.8899999717
1971
1616
200
image/png
Image
https://betpawa.com/images/betpawa-rwanda.png
h2
1159.2360000359
1366.165000014
2942
2587
200
image/png
Image
https://betpawa.com/images/betpawa-malawi.png
h2
1159.8610000219
1449.6969999745
3865
3510
200
image/png
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)
638.196
11.598
1003.549
14.456
1154.958
5.854
1160.83
5.044
1458.942
6.029
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

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Betpawa.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Betpawa.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Betpawa.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Betpawa.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Betpawa.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Betpawa.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 8 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.betpawa.com/fonts/Roboto_italic_fonts
9225
8456
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 390 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)
https://betpawa.com/
392.16
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Betpawa.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://betpawa.com/
630
https://betpawa.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Betpawa.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.
URL Potential Savings (Ms)
https://betpawa.com/images/my-betpawa.jpg
0
Avoids enormous network payloads — Total size was 60 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://betpawa.com/images/my-betpawa.jpg
15101
https://static.betpawa.com/fonts/Roboto_italic_fonts
10113
https://betpawa.com/images/betpawa-malawi.png
3865
https://betpawa.com/images/betpawa-kenya.png
3653
https://betpawa.com/images/betpawa-tanzania.png
3629
https://betpawa.com/images/betpawa-uganda.png
3203
https://betpawa.com/images/betpawa-zambia.png
3119
https://betpawa.com/images/betpawa-rwanda.png
2942
https://betpawa.com/images/betpawa-ghana.png
2900
https://betpawa.com/images/logo_monochrome.png
2574
Avoids an excessive DOM size — 39 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
39
Maximum DOM Depth
5
Maximum Child Elements
10
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Betpawa.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.1 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)
https://betpawa.com/
239.84
47.976
7.736
Unattributable
75.292
8.768
0
Minimizes main-thread work — 0.3 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)
Other
128.124
Rendering
69.288
Script Evaluation
56.744
Style & Layout
51.9
Parse HTML & CSS
8.504
Script Parsing & Compilation
7.736
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 17 requests • 60 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
17
61482
Image
12
46809
Stylesheet
2
11489
Document
1
2505
Other
2
679
Media
0
0
Font
0
0
Script
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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.
Element
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.09296875
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
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 betpawa.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.
First Contentful Paint (3G) — 2193 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

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.

Other

Serve static assets with an efficient cache policy — 14 resources found
Betpawa.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)
https://betpawa.com/images/my-betpawa.jpg
0
15101
https://static.betpawa.com/fonts/Roboto_italic_fonts
0
10113
https://betpawa.com/images/betpawa-malawi.png
0
3865
https://betpawa.com/images/betpawa-kenya.png
0
3653
https://betpawa.com/images/betpawa-tanzania.png
0
3629
https://betpawa.com/images/betpawa-uganda.png
0
3203
https://betpawa.com/images/betpawa-zambia.png
0
3119
https://betpawa.com/images/betpawa-rwanda.png
0
2942
https://betpawa.com/images/betpawa-ghana.png
0
2900
https://betpawa.com/images/logo_monochrome.png
0
2574
https://betpawa.com/images/betpawa-cameroon.png
0
2380
https://betpawa.com/images/betpawa-drc.png
0
1971
https://betpawa.com/images/betpawa-nigeria.png
0
1472
https://betpawa.com/style.css
0
1376

Other

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://betpawa.com/images/logo_monochrome.png
66

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of betpawa.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.
Heading elements appear 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.
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"]`
Betpawa.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that betpawa.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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request 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://betpawa.com/
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://betpawa.com/images/betpawa-ghana.png
60 x 60
108 x 108
120 x 120
https://betpawa.com/images/betpawa-kenya.png
60 x 60
108 x 108
120 x 120
https://betpawa.com/images/betpawa-nigeria.png
60 x 60
108 x 108
120 x 120
https://betpawa.com/images/betpawa-tanzania.png
60 x 60
108 x 108
120 x 120
https://betpawa.com/images/betpawa-zambia.png
60 x 60
108 x 108
120 x 120
https://betpawa.com/images/betpawa-uganda.png
60 x 60
108 x 110
120 x 120
85

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for betpawa.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 betpawa.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
Tap targets are sized appropriately — 100% 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.

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.

Crawling and Indexing

robots.txt is not valid — 339 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE html>
Syntax not understood
2
<html>
Syntax not understood
3
<head>
Syntax not understood
4
<meta charset="UTF-8">
Syntax not understood
5
<link href='https://static.betpawa.com/fonts/Roboto_italic_fonts' rel='stylesheet' type='text/css'
Unknown directive
6
media="none"
Syntax not understood
7
onload="if(media!='all')media='all'">
Syntax not understood
8
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
Syntax not understood
9
<meta name="viewport" content="width=device-width, initial-scale=1">
Syntax not understood
10
<title>betPawa.com | Online sports betting</title>
Syntax not understood
11
<meta name="description" content="The best online sports betting! betPawa.com is licensed by the Lotteries">
Syntax not understood
12
<link rel="icon" type="image/png" sizes="16x16" href="./images/favicon.png">
Syntax not understood
13
<link href="./style.css" rel="stylesheet" type="text/css">
Syntax not understood
14
<script>
Syntax not understood
15
preinit();
Syntax not understood
17
function preinit() {
Syntax not understood
18
var isBack = window.location.pathname === '/return';
Syntax not understood
19
if (isBack) {
Syntax not understood
20
setCookie('');
Syntax not understood
21
} else {
Syntax not understood
22
var domain = getCookie();
Syntax not understood
23
if (domain) {
Syntax not understood
24
window.location.href = domain;
Syntax not understood
25
}
Syntax not understood
26
}
Syntax not understood
27
}
Syntax not understood
29
function getCookie() {
Syntax not understood
30
var cVal = document.cookie.match('(?:^|;) ?BetpawaCountry=([^;]*)(?:;|$)');
Unknown directive
31
if (!cVal) {
Syntax not understood
32
return null;
Syntax not understood
33
} else {
Syntax not understood
34
return cVal[1];
Syntax not understood
35
}
Syntax not understood
36
}
Syntax not understood
38
function setCookie(cvalue) {
Syntax not understood
39
var d = new Date();
Syntax not understood
40
d.setTime(d.getTime() + (365 * 24 * 60 * 60 * 1000));
Syntax not understood
41
var expires = "expires=" + d.toUTCString();
Syntax not understood
42
document.cookie = "BetpawaCountry=" + cvalue + "; " + expires;
Syntax not understood
43
}
Syntax not understood
44
</script>
Syntax not understood
45
</head>
Syntax not understood
46
<body>
Syntax not understood
47
<section class="intro">
Syntax not understood
48
<!--<div class="container">-->
Syntax not understood
49
<!--<div class="column first">-->
Syntax not understood
50
<!--<img class="logo" src="https://static.betpawa.com/img/landing/logo_color.png">-->
Unknown directive
51
<!--<p>Bet small win BIG</p>-->
Syntax not understood
52
<!--</div>-->
Syntax not understood
53
<!--<div class="column second"></div>-->
Syntax not understood
54
<!--</div>-->
Syntax not understood
55
</section>
Syntax not understood
56
<div class="gallery">
Syntax not understood
57
<h3>Select your country</h3>
Syntax not understood
58
<div id="country-select" class="container"></div>
Syntax not understood
59
</div>
Syntax not understood
61
<footer>
Syntax not understood
62
<img src="./images/logo_monochrome.png">
Syntax not understood
63
<div>&copy; betPawa <span id="js-year">2019</span>. All Rights reserved</div>
Syntax not understood
64
</footer>
Syntax not understood
65
</body>
Syntax not understood
66
<script type="text/javascript">
Syntax not understood
67
var $countrySelect = window.document.getElementById('country-select');
Syntax not understood
68
var $year = window.document.getElementById('js-year');
Syntax not understood
69
var countries = [
Syntax not understood
70
{
Syntax not understood
71
countryIso2Code: 'DZ',
Unknown directive
72
countryName: 'Algeria'
Unknown directive
73
},
Syntax not understood
74
{
Syntax not understood
75
countryIso2Code: 'AO',
Unknown directive
76
countryName: 'Angola'
Unknown directive
77
},
Syntax not understood
78
{
Syntax not understood
79
countryIso2Code: 'BJ',
Unknown directive
80
countryName: 'Benin'
Unknown directive
81
},
Syntax not understood
82
{
Syntax not understood
83
countryIso2Code: 'BW',
Unknown directive
84
countryName: 'Botswana'
Unknown directive
85
},
Syntax not understood
86
{
Syntax not understood
87
countryIso2Code: 'BF',
Unknown directive
88
countryName: 'Burkina Faso'
Unknown directive
89
},
Syntax not understood
90
{
Syntax not understood
91
countryIso2Code: 'BI',
Unknown directive
92
countryName: 'Burundi'
Unknown directive
93
},
Syntax not understood
94
{
Syntax not understood
95
countryIso2Code: 'CM',
Unknown directive
96
countryName: 'Cameroon'
Unknown directive
97
},
Syntax not understood
98
{
Syntax not understood
99
countryIso2Code: 'CV',
Unknown directive
100
countryName: 'Cape Verde'
Unknown directive
101
},
Syntax not understood
102
{
Syntax not understood
103
countryIso2Code: 'CF',
Unknown directive
104
countryName: 'Central African Republic'
Unknown directive
105
},
Syntax not understood
106
{
Syntax not understood
107
countryIso2Code: 'TD',
Unknown directive
108
countryName: 'Chad'
Unknown directive
109
},
Syntax not understood
110
{
Syntax not understood
111
countryIso2Code: 'KM',
Unknown directive
112
countryName: 'Comoros'
Unknown directive
113
},
Syntax not understood
114
{
Syntax not understood
115
countryIso2Code: 'CG',
Unknown directive
116
countryName: 'Congo'
Unknown directive
117
},
Syntax not understood
118
{
Syntax not understood
119
countryIso2Code: 'CD',
Unknown directive
120
countryName: 'DR Congo'
Unknown directive
121
},
Syntax not understood
122
{
Syntax not understood
123
countryIso2Code: 'CI',
Unknown directive
124
countryName: 'Cote d’Ivoire'
Unknown directive
125
},
Syntax not understood
126
{
Syntax not understood
127
countryIso2Code: 'DJ',
Unknown directive
128
countryName: 'Djibouti'
Unknown directive
129
},
Syntax not understood
130
{
Syntax not understood
131
countryIso2Code: 'EG',
Unknown directive
132
countryName: 'Egypt'
Unknown directive
133
},
Syntax not understood
134
{
Syntax not understood
135
countryIso2Code: 'GQ',
Unknown directive
136
countryName: 'Equatorial Guinea'
Unknown directive
137
},
Syntax not understood
138
{
Syntax not understood
139
countryIso2Code: 'ER',
Unknown directive
140
countryName: 'Eritrea'
Unknown directive
141
},
Syntax not understood
142
{
Syntax not understood
143
countryIso2Code: 'ET',
Unknown directive
144
countryName: 'Ethiopia'
Unknown directive
145
},
Syntax not understood
146
{
Syntax not understood
147
countryIso2Code: 'GA',
Unknown directive
148
countryName: 'Gabon'
Unknown directive
149
},
Syntax not understood
150
{
Syntax not understood
151
countryIso2Code: 'GM',
Unknown directive
152
countryName: 'Gambia'
Unknown directive
153
},
Syntax not understood
154
{
Syntax not understood
155
countryIso2Code: 'GH',
Unknown directive
156
countryName: 'Ghana'
Unknown directive
157
},
Syntax not understood
158
{
Syntax not understood
159
countryIso2Code: 'GN',
Unknown directive
160
countryName: 'Guinea'
Unknown directive
161
},
Syntax not understood
162
{
Syntax not understood
163
countryIso2Code: 'GW',
Unknown directive
164
countryName: 'Guinea-Bissau'
Unknown directive
165
},
Syntax not understood
166
{
Syntax not understood
167
countryIso2Code: 'KE',
Unknown directive
168
countryName: 'Kenya'
Unknown directive
169
},
Syntax not understood
170
{
Syntax not understood
171
countryIso2Code: 'LS',
Unknown directive
172
countryName: 'Lesotho'
Unknown directive
173
},
Syntax not understood
174
{
Syntax not understood
175
countryIso2Code: 'LR',
Unknown directive
176
countryName: 'Liberia'
Unknown directive
177
},
Syntax not understood
178
{
Syntax not understood
179
countryIso2Code: 'LY',
Unknown directive
180
countryName: 'Libyan Arab Jamahiriya'
Unknown directive
181
},
Syntax not understood
182
{
Syntax not understood
183
countryIso2Code: 'MG',
Unknown directive
184
countryName: 'Madagascar'
Unknown directive
185
},
Syntax not understood
186
{
Syntax not understood
187
countryIso2Code: 'ML',
Unknown directive
188
countryName: 'Mali'
Unknown directive
189
},
Syntax not understood
190
{
Syntax not understood
191
countryIso2Code: 'MW',
Unknown directive
192
countryName: 'Malawi'
Unknown directive
193
},
Syntax not understood
194
{
Syntax not understood
195
countryIso2Code: 'MR',
Unknown directive
196
countryName: 'Mauritania'
Unknown directive
197
},
Syntax not understood
198
{
Syntax not understood
199
countryIso2Code: 'MU',
Unknown directive
200
countryName: 'Mauritius'
Unknown directive
201
},
Syntax not understood
202
{
Syntax not understood
203
countryIso2Code: 'YT',
Unknown directive
204
countryName: 'Mayotte'
Unknown directive
205
},
Syntax not understood
206
{
Syntax not understood
207
countryIso2Code: 'MA',
Unknown directive
208
countryName: 'Morocco'
Unknown directive
209
},
Syntax not understood
210
{
Syntax not understood
211
countryIso2Code: 'MZ',
Unknown directive
212
countryName: 'Mozambique'
Unknown directive
213
},
Syntax not understood
214
{
Syntax not understood
215
countryIso2Code: 'NA',
Unknown directive
216
countryName: 'Namibia'
Unknown directive
217
},
Syntax not understood
218
{
Syntax not understood
219
countryIso2Code: 'NE',
Unknown directive
220
countryName: 'Niger'
Unknown directive
221
},
Syntax not understood
222
{
Syntax not understood
223
countryIso2Code: 'NG',
Unknown directive
224
countryName: 'Nigeria'
Unknown directive
225
},
Syntax not understood
226
{
Syntax not understood
227
countryIso2Code: 'RE',
Unknown directive
228
countryName: 'Reunion Island'
Unknown directive
229
},
Syntax not understood
230
{
Syntax not understood
231
countryIso2Code: 'RW',
Unknown directive
232
countryName: 'Rwanda'
Unknown directive
233
},
Syntax not understood
234
{
Syntax not understood
235
countryIso2Code: 'ST',
Unknown directive
236
countryName: 'Sao Tome and Principe'
Unknown directive
237
},
Syntax not understood
238
{
Syntax not understood
239
countryIso2Code: 'SN',
Unknown directive
240
countryName: 'Senegal'
Unknown directive
241
},
Syntax not understood
242
{
Syntax not understood
243
countryIso2Code: 'SC',
Unknown directive
244
countryName: 'Seychelles'
Unknown directive
245
},
Syntax not understood
246
{
Syntax not understood
247
countryIso2Code: 'SL',
Unknown directive
248
countryName: 'Sierra Leone'
Unknown directive
249
},
Syntax not understood
250
{
Syntax not understood
251
countryIso2Code: 'SO',
Unknown directive
252
countryName: 'Somalia'
Unknown directive
253
},
Syntax not understood
254
{
Syntax not understood
255
countryIso2Code: 'ZA',
Unknown directive
256
countryName: 'South Africa'
Unknown directive
257
},
Syntax not understood
258
{
Syntax not understood
259
countryIso2Code: 'SS',
Unknown directive
260
countryName: 'South Sudan'
Unknown directive
261
},
Syntax not understood
262
{
Syntax not understood
263
countryIso2Code: 'SD',
Unknown directive
264
countryName: 'Sudan'
Unknown directive
265
},
Syntax not understood
266
{
Syntax not understood
267
countryIso2Code: 'SZ',
Unknown directive
268
countryName: 'Swaziland'
Unknown directive
269
},
Syntax not understood
270
{
Syntax not understood
271
countryIso2Code: 'TZ',
Unknown directive
272
countryName: 'Tanzania'
Unknown directive
273
},
Syntax not understood
274
{
Syntax not understood
275
countryIso2Code: 'TG',
Unknown directive
276
countryName: 'Togo'
Unknown directive
277
},
Syntax not understood
278
{
Syntax not understood
279
countryIso2Code: 'TN',
Unknown directive
280
countryName: 'Tunisia'
Unknown directive
281
},
Syntax not understood
282
{
Syntax not understood
283
countryIso2Code: 'UG',
Unknown directive
284
countryName: 'Uganda'
Unknown directive
285
},
Syntax not understood
286
{
Syntax not understood
287
countryIso2Code: 'EH',
Unknown directive
288
countryName: 'Western Sahara'
Unknown directive
289
},
Syntax not understood
290
{
Syntax not understood
291
countryIso2Code: 'ZM',
Unknown directive
292
countryName: 'Zambia'
Unknown directive
293
},
Syntax not understood
294
{
Syntax not understood
295
countryIso2Code: 'ZW',
Unknown directive
296
countryName: 'Zimbabwe'
Unknown directive
297
},
Syntax not understood
298
];
Syntax not understood
300
init();
Syntax not understood
302
function init() {
Syntax not understood
303
$year.innerText = (new Date()).getFullYear().toString();
Syntax not understood
304
loadJurisdictions(renderCountries);
Syntax not understood
305
}
Syntax not understood
307
function renderCountries(data) {
Syntax not understood
308
var html = '';
Syntax not understood
309
for (var i = 0; i < data.length; i++) {
Syntax not understood
310
if (!data[i].landingPageActive) continue;
Syntax not understood
312
var country;
Syntax not understood
313
for (var j = 0; j < countries.length; j++) {
Syntax not understood
314
if (countries[j].countryIso2Code === data[i].countryIso2Code) {
Syntax not understood
315
country = countries[j];
Syntax not understood
316
}
Syntax not understood
317
}
Syntax not understood
319
html +=
Syntax not understood
320
'<a href="https://www.' + data[i].rootDomain + '" class="thumbnail" onclick="return clickLink(\'https://www.' + data[i].rootDomain + '\')">' +
Unknown directive
321
'<img src="./images/' + data[i].brandIdentifier + '.png">' +
Syntax not understood
322
'<h4>' + country.countryName + '</h4>' +
Syntax not understood
323
'</a>';
Syntax not understood
324
}
Syntax not understood
325
$countrySelect.innerHTML = html;
Syntax not understood
326
}
Syntax not understood
328
function clickLink(url) {
Syntax not understood
329
setCookie(url);
Syntax not understood
330
window.location.href = url;
Syntax not understood
331
return false;
Syntax not understood
332
}
Syntax not understood
334
function loadJurisdictions(callbackFn) {
Syntax not understood
335
var xmlhttp = new XMLHttpRequest();
Syntax not understood
336
var url = "/api/brand/v1/countries/betpawa";
Syntax not understood
338
xmlhttp.onreadystatechange = function (result) {
Syntax not understood
339
if (this.readyState === 4 && this.status === 200) {
Syntax not understood
340
try {
Syntax not understood
341
callbackFn(JSON.parse(result.currentTarget.response));
Syntax not understood
342
} catch (e) {
Syntax not understood
343
}
Syntax not understood
344
}
Syntax not understood
345
};
Syntax not understood
347
xmlhttp.open("GET", url, true);
Syntax not understood
348
xmlhttp.setRequestHeader('accept', 'application/json');
Syntax not understood
349
xmlhttp.send();
Syntax not understood
350
}
Syntax not understood
351
</script>
Syntax not understood
352
</html>
Syntax not understood

Content Best Practices

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 betpawa.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 betpawa.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: 167.233.8.194
Continent: Europe
Country: Germany
Germany Flag
Region:
City:
Longitude: 9.491
Latitude: 51.2993
Currencies: EUR
Languages: German

Web Hosting Provider

Name IP Address
Akamai Technologies
Registration

Domain Registrant

Private Registration: No
Name: On behalf of betpawa.com owner
Organization: Identity Protection Service
Country: GB
City: Hayes
State: Middlesex
Post Code: UB3 9TR
Email: 6595e3fb-4885-4d77-875e-bedbd98a5b48@identity-protect.org
Phone: +44.1483307527
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Amazon Registrar, Inc. 3.162.3.39
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: www.betpawa.com
Issued By: R3
Valid From: 28th January, 2023
Valid To: 28th April, 2023
Subject: CN = www.betpawa.com
Hash: cc39cfad
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04825E83BE51926D9B0D01EC54D244DABF8B
Serial Number (Hex): 04825E83BE51926D9B0D01EC54D244DABF8B
Valid From: 28th January, 2024
Valid To: 28th April, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Jan 28 08:55:05.512 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E3:84:8C:5B:88:E2:74:C1:4D:99:6C:
48:7F:7F:D7:CC:BA:16:AE:80:82:0B:FF:E0:D8:AB:BA:
96:20:31:1F:46:02:21:00:A4:4C:DF:37:D7:7E:87:3B:
7C:57:42:8A:2F:54:45:09:3E:B1:ED:B1:AA:29:07:6B:
6C:7B:15:29:6B:5F:CE:75
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Jan 28 08:55:05.525 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:17:B3:3F:68:F0:A5:3C:16:38:12:43:1A:
EC:15:67:BA:2B:5C:BD:F9:E1:99:38:83:9F:D8:E8:E1:
2C:BB:35:09:02:21:00:AA:7C:B9:96:2F:51:6D:3A:2D:
14:C3:D7:EA:08:2C:52:82:6C:EE:6F:E4:2F:B3:F2:B6:
9F:33:A0:DA:A0:C8:F4
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:betpawa.com
DNS:www.betpawa.co
DNS:www.betpawa.com
DNS:betpawa.co
Technical

DNS Lookup

A Records

Host IP Address Class TTL
betpawa.com. 2.18.49.224 IN 60

NS Records

Host Nameserver Class TTL
betpawa.com. ns-1357.awsdns-41.org. IN 21600
betpawa.com. ns-1887.awsdns-43.co.uk. IN 21600
betpawa.com. ns-47.awsdns-05.com. IN 21600
betpawa.com. ns-560.awsdns-06.net. IN 21600

MX Records

Priority Host Server Class TTL
1 betpawa.com. aspmx.l.google.com. IN 3600
10 betpawa.com. alt3.aspmx.l.google.com. IN 3600
10 betpawa.com. alt4.aspmx.l.google.com. IN 3600
5 betpawa.com. alt1.aspmx.l.google.com. IN 3600
5 betpawa.com. alt2.aspmx.l.google.com. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
betpawa.com. ns-47.awsdns-05.com. awsdns-hostmaster.amazon.com. 60

TXT Records

Host Value Class TTL
betpawa.com. 1password-site-verification=FSLD3OXI4NCWFD3RU7DNGDTWKE IN 60
betpawa.com. ahrefs-site-verification_e8c7f4032defab07da53ba273e57c5ff361344947695f7397894ad2c88cd2e4a IN 60
betpawa.com. facebook-domain-verification=22m6ozkpqkfsz5s8w1xqe0vaxw0lu7 IN 60
betpawa.com. google-site-verification=a5hYxItbwzMaHKrvtb4VtEz6ruDLUOvcIot_w-YJYoY IN 60
betpawa.com. google-site-verification=v3FwM-fiZCXdp793Cg5gN-Knu7qL-4HIzGJlTg68yRI IN 60
betpawa.com. google-site-verification=zzhAkmjaOeXrE6YN4ElbfDDnrOq8UgxAwvSH8tC6GtI IN 60
betpawa.com. v=spf1 IN 60

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 28th February, 2023
Content-Type: text/html
Content-Length: 8795
Connection: keep-alive
Vary: Accept-Encoding
x-amz-id-2: Rtd80QugPV/8pvsbNUr1Hj1oDaOiHy7Cd4HNfMTr3fGzhhFptEcR0iXvG+HUsRRp+jq9IAhSb0c=
x-amz-request-id: AYWX9H1J1M45MBFR
Last-Modified: 1st February, 2023
ETag: "a8a65f8a2eb8f73aae64852efcf5a413"
x-amz-server-side-encryption: AES256
X-Cache-Status: HIT
Accept-Ranges: bytes

Whois Lookup

Created: 21st April, 2014
Changed: 21st December, 2022
Expires: 21st April, 2023
Registrar: Amazon Registrar, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
Nameservers: damian.ns.cloudflare.com
isla.ns.cloudflare.com
Owner Name: On behalf of betpawa.com owner
Owner Organization: Identity Protection Service
Owner Street: PO Box 786
Owner Post Code: UB3 9TR
Owner City: Hayes
Owner State: Middlesex
Owner Country: GB
Owner Phone: +44.1483307527
Owner Email: 6595e3fb-4885-4d77-875e-bedbd98a5b48@identity-protect.org
Admin Name: On behalf of betpawa.com owner
Admin Organization: Identity Protection Service
Admin Street: PO Box 786
Admin Post Code: UB3 9TR
Admin City: Hayes
Admin State: Middlesex
Admin Country: GB
Admin Phone: +44.1483307527
Admin Email: 6595e3fb-4885-4d77-875e-bedbd98a5b48@identity-protect.org
Tech Name: On behalf of betpawa.com owner
Tech Organization: Identity Protection Service
Tech Street: PO Box 786
Tech Post Code: UB3 9TR
Tech City: Hayes
Tech State: Middlesex
Tech Country: GB
Tech Phone: +44.1483307527
Tech Email: 6595e3fb-4885-4d77-875e-bedbd98a5b48@identity-protect.org
Full Whois: Domain Name: betpawa.com
Registry Domain ID: 1855551641_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: https://registrar.amazon.com
Updated Date: 2022-12-21T06:36:39Z
Creation Date: 2014-04-21T10:22:29Z
Registrar Registration Expiration Date: 2023-04-21T10:22:29Z
Registrar: Amazon Registrar, Inc.
Registrar IANA ID: 468
Registrar Abuse Contact Email: abuse@amazonaws.com
Registrar Abuse Contact Phone: +1.2067406200
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: On behalf of betpawa.com owner
Registrant Organization: Identity Protection Service
Registrant Street: PO Box 786
Registrant City: Hayes
Registrant State/Province: Middlesex
Registrant Postal Code: UB3 9TR
Registrant Country: GB
Registrant Phone: +44.1483307527
Registrant Phone Ext:
Registrant Fax: +44.1483304031
Registrant Fax Ext:
Registrant Email: 6595e3fb-4885-4d77-875e-bedbd98a5b48@identity-protect.org
Registry Admin ID: Not Available From Registry
Admin Name: On behalf of betpawa.com owner
Admin Organization: Identity Protection Service
Admin Street: PO Box 786
Admin City: Hayes
Admin State/Province: Middlesex
Admin Postal Code: UB3 9TR
Admin Country: GB
Admin Phone: +44.1483307527
Admin Phone Ext:
Admin Fax: +44.1483304031
Admin Fax Ext:
Admin Email: 6595e3fb-4885-4d77-875e-bedbd98a5b48@identity-protect.org
Registry Tech ID: Not Available From Registry
Tech Name: On behalf of betpawa.com owner
Tech Organization: Identity Protection Service
Tech Street: PO Box 786
Tech City: Hayes
Tech State/Province: Middlesex
Tech Postal Code: UB3 9TR
Tech Country: GB
Tech Phone: +44.1483307527
Tech Phone Ext:
Tech Fax: +44.1483304031
Tech Fax Ext:
Tech Email: 6595e3fb-4885-4d77-875e-bedbd98a5b48@identity-protect.org
Name Server: ISLA.NS.CLOUDFLARE.COM
Name Server: DAMIAN.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-02-28T17:15:04Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

By submitting a query to the Amazon Registrar, Inc. WHOIS database, you
agree to abide by the following terms. The data in Amazon Registrar, Inc.'s
WHOIS database is provided by Amazon Registrar, Inc. for the sole purpose of
assisting you in obtaining information about domain name accuracy. You agree
to use this data only for lawful purposes and further agree not to use this
data for any unlawful purpose or to: (1) enable, allow, or otherwise support
the transmission by email, telephone, or facsimile of commercial advertising
or unsolicited bulk email, or (2) enable high volume, automated, electronic
processes to collect or compile this data for any purpose, including mining
this data for your own personal or commercial purposes. Amazon Registrar, Inc.
reserves the right to restrict or terminate your access to the data if you fail
to abide by these terms of use. Amazon Registrar, Inc. reserves the right
to modify these terms at any time.

Visit Amazon Registrar, Inc. at https://registrar.amazon.com

Contact information available here:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-contact-support.html

© 2020, Amazon.com, Inc., or its affiliates

Nameservers

Name IP Address
damian.ns.cloudflare.com 108.162.195.50
isla.ns.cloudflare.com 108.162.192.119
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$4,009 USD 2/5
0/5
0/5
$30,409 USD 2/5

Sites hosted on the same IP address