sattaking.in

sattaking.in is SSL secured

Free website and domain report on sattaking.in

Last Updated: 27th April, 2022 Update Now
Overview

Snoop Summary for sattaking.in

This is a free and comprehensive report about sattaking.in. The domain sattaking.in is currently hosted on a server located in United States with the IP address 172.67.168.104, where the local currency is USD and English is the local language. Sattaking.in has the potential to be earning an estimated $1 USD per day from advertising revenue. If sattaking.in was to be sold it would possibly be worth $980 USD (based on the daily revenue potential of the website over a 24 month period). Sattaking.in is somewhat popular with an estimated 466 daily unique visitors. This report was last updated 27th April, 2022.

About sattaking.in

Site Preview: sattaking.in sattaking.in
Title: Satta King 2022 | Satta Live Result | Satta Result | Sattaking
Description: Satta King (सट्टा किंग) popular in India since the 1970s is a kind of lottery game based on numbers from 00 to 99. Satta King 2022. Sattaking Live Result.
Keywords and Tags: games
Related Terms: 2021 satta matka, amar satta matka, dainik result, dj ashish king jaunpur, king stud, king wen, nagpur satta matka, qatar 2022, satta matkalucky number today, stephen king
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$980 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,684,350
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 466
Monthly Visitors: 14,184
Yearly Visitors: 170,090
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $40 USD
Yearly Revenue: $485 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: sattaking.in 12
Domain Name: sattaking 9
Extension (TLD): in 2

Page Speed Analysis

Average Load Time: 2.70 seconds
Load Time Comparison: Faster than 27% of sites

PageSpeed Insights

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

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 90 ms
Users could experience a delay when interacting with the page.
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://sattaking.in/
http/1.1
0
75.856999959797
711
0
301
text/plain
https://sattaking.in/
h2
76.344000000972
511.25299994601
35314
153750
200
text/html
Document
https://sattaking.in/wp-content/astra-local-fonts/oswald/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiZQ.woff2
h2
527.47599995928
877.13199999416
16962
16016
200
font/woff2
Font
https://sattaking.in/wp-content/litespeed/css/93739cfaa45b5e4b4d40d0d6ef9301ee.css?ver=106d0
h2
527.83799997997
974.66599999461
13175
71718
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/200d830a30185f9093708b9acb9fd730.css?ver=c1d67
h2
528.46499998122
675.00099999597
1372
1676
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/dcd716a031be105b24a01a5feeca56e3.css?ver=af4fa
h2
529.14099994814
774.35799996601
12287
83140
200
text/css
Stylesheet
https://sattaking.in/wp-includes/js/wp-emoji-release.min.js?ver=5.9.3
h2
991.24000000302
1094.2749999813
5717
18181
200
application/x-javascript
Script
https://sattaking.in/wp-content/litespeed/css/dbe543bb54654390c315512b6179ce96.css?ver=4d664
h2
595.33599996939
775.11399996001
4758
19416
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/f7a423836b865226902f67686786827e.css?ver=5b9e3
h2
595.73000000091
777.38699998008
1770
13805
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/f38f93e88b2129cdae723283a9b912c2.css?ver=efe73
h2
596.02199995425
804.17999997735
21200
163227
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/cd677a18d23c70689d5fd01f55b4a86b.css?ver=19dc1
h2
596.46400000202
719.20499997213
1371
1452
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/185ea73c0af57470350821e4d235f8d5.css?ver=f608e
h2
596.85299999546
977.3779999814
13852
60316
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/a68b28ff52484dbbb53b43cab7781940.css?ver=0f249
h2
597.16399997706
865.95799995121
5131
26702
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/0402f63800a48183265e032db68906a9.css?ver=93bec
h2
597.55599999335
976.43199999584
2481
10933
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/f6e290095b588c2fb2320773b865bf46.css?ver=6f4ca
h2
597.80299995327
775.89499996975
14081
95615
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto+Slab%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CAlfa+Slab+One%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic&display=auto&ver=5.9.3
h2
598.20199996466
612.35099995974
2458
44917
200
text/css
Stylesheet
https://sattaking.in/wp-content/plugins/elementor/assets/lib/font-awesome/js/v4-shims.min.js?ver=3.6.4
h2
598.57899998315
976.85300000012
5177
15055
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/ninja-tables/assets/fonts/ninja-tables.woff2?1a82860cb5286f7833a2c33fbdd1d76c
h2
598.9759999793
975.28299997794
3632
2688
200
font/woff2
Font
https://sattaking.in/wp-content/litespeed/css/ad6685ae673257721cdfb15d02c3c323.css?ver=45821
h2
603.73099998105
702.57799996762
3595
18456
200
text/css
Stylesheet
https://sattaking.in/wp-content/themes/astra/assets/js/minified/style.min.js?ver=3.7.10
h2
604.1199999745
776.84499998577
3673
10398
200
application/x-javascript
Script
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
h2
604.52100000111
722.33999997843
32901
89521
200
application/x-javascript
Script
https://sattaking.in/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2
h2
604.88599998644
775.47999995295
5226
11224
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/ninja-tables/public/libs/footable/js/footable.min.js?ver=3.1.5
h2
605.2689999924
1010.5259999982
21479
82971
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/ninja-tables/assets/js/ninja-tables-footable.3.1.0.js?ver=4.1.14
h2
605.63999996521
776.43299999181
18081
53549
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/js/webpack.runtime.min.js?ver=3.6.4
h2
606.01799999131
777.11699996144
3114
4960
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.6.4
h2
606.39899998205
724.78199994657
5695
14277
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/lib/waypoints/waypoints.min.js?ver=4.0.2
h2
606.56299995026
1106.7219999968
4112
12198
200
application/x-javascript
Script
https://sattaking.in/wp-includes/js/jquery/ui/core.min.js?ver=1.13.1
h2
606.82999994606
975.65999999642
7970
20714
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/lib/swiper/swiper.min.js?ver=5.3.6
h2
607.23899997538
777.68099994864
37345
139153
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/lib/share-link/share-link.min.js?ver=3.6.4
h2
607.43899998488
717.14099997189
2064
2578
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/lib/dialog/dialog.min.js?ver=4.9.0
h2
607.85999998916
976.05800000019
4450
10682
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.6.4
h2
608.64299995592
728.50399999879
12353
37741
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/js/preloaded-modules.min.js?ver=3.6.4
h2
609.50999998022
977.8449999867
14187
43392
200
application/x-javascript
Script
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
991.38799996581
1074.8840000015
5618
13970
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1096.2259999942
1099.7619999689
11976
11048
200
font/woff2
Font
https://sattaking.in/cdn-cgi/rum?
h2
1707.9109999468
1774.3449999834
407
0
200
text/plain
XHR
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)
604.374
9.533
618.202
65.225
691.911
5.182
955.526
8.522
1075.946
9.69
1085.648
214.887
1305.294
80.821
1389.607
110.578
1500.411
64.104
1565.164
26.055
1591.422
88.535
1687.263
10.909
1700.267
11.681
1711.96
81.058
1799.698
8.449
1814.742
49.148
1864.884
7.26
1880.28
8.795
1903.646
69.695
2019.354
45.315
2319.013
44.666
2398.836
13.233
2618.372
49.177
2693.043
5.775
2701.592
5.834
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. Sattaking.in 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. Sattaking.in should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Sattaking.in should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Sattaking.in should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Sattaking.in should consider minifying JS files.
Reduce unused CSS — Potential savings of 70 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Sattaking.in should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://sattaking.in/wp-content/litespeed/css/f38f93e88b2129cdae723283a9b912c2.css?ver=efe73
21200
20606
https://sattaking.in/wp-content/litespeed/css/185ea73c0af57470350821e4d235f8d5.css?ver=f608e
13852
13852
https://sattaking.in/wp-content/litespeed/css/f6e290095b588c2fb2320773b865bf46.css?ver=6f4ca
14081
13204
https://sattaking.in/wp-content/litespeed/css/93739cfaa45b5e4b4d40d0d6ef9301ee.css?ver=106d0
13175
12265
https://sattaking.in/wp-content/litespeed/css/dcd716a031be105b24a01a5feeca56e3.css?ver=af4fa
12287
12230
Reduce unused JavaScript — Potential savings of 33 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://sattaking.in/wp-content/plugins/elementor/assets/lib/swiper/swiper.min.js?ver=5.3.6
37345
33537
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
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 440 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://sattaking.in/
435.899
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Sattaking.in should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://sattaking.in/
190
https://sattaking.in/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Sattaking.in 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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://sattaking.in/wp-content/plugins/ninja-tables/assets/js/ninja-tables-footable.3.1.0.js?ver=4.1.14
56
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 347 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://sattaking.in/wp-content/plugins/elementor/assets/lib/swiper/swiper.min.js?ver=5.3.6
37345
https://sattaking.in/
35314
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
32901
https://sattaking.in/wp-content/plugins/ninja-tables/public/libs/footable/js/footable.min.js?ver=3.1.5
21479
https://sattaking.in/wp-content/litespeed/css/f38f93e88b2129cdae723283a9b912c2.css?ver=efe73
21200
https://sattaking.in/wp-content/plugins/ninja-tables/assets/js/ninja-tables-footable.3.1.0.js?ver=4.1.14
18081
https://sattaking.in/wp-content/astra-local-fonts/oswald/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiZQ.woff2
16962
https://sattaking.in/wp-content/plugins/elementor/assets/js/preloaded-modules.min.js?ver=3.6.4
14187
https://sattaking.in/wp-content/litespeed/css/f6e290095b588c2fb2320773b865bf46.css?ver=6f4ca
14081
https://sattaking.in/wp-content/litespeed/css/185ea73c0af57470350821e4d235f8d5.css?ver=f608e
13852
Uses efficient cache policy on static assets — 1 resource found
Sattaking.in 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://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5618
Avoids an excessive DOM size — 503 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
503
Maximum DOM Depth
30
Maximum Child Elements
71
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Sattaking.in 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.6 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://sattaking.in/
653.338
138.777
3.63
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
414.837
341.284
2.23
https://sattaking.in/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.6.4
68.567
67.96
0.607
Unattributable
60.973
3.696
0.191
Minimizes main-thread work — 1.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)
Script Evaluation
599.62
Style & Layout
425.739
Parse HTML & CSS
106.586
Other
84.44
Rendering
26.706
Script Parsing & Compilation
14.286
Keep request counts low and transfer sizes small — 36 requests • 347 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
36
355695
Script
17
189162
Stylesheet
13
97531
Document
1
35314
Font
3
32570
Other
2
1118
Image
0
0
Media
0
0
Third-party
3
20052
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
14434
0
5618
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.024319001182033
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 — 7 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://sattaking.in/
445
107
https://sattaking.in/wp-content/plugins/elementor/assets/lib/waypoints/waypoints.min.js?ver=4.0.2
1100
89
https://sattaking.in/wp-content/themes/astra/assets/js/minified/style.min.js?ver=3.7.10
820
81
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
1239
70
https://sattaking.in/
380
65
https://sattaking.in/
700
64
https://sattaking.in/
552
55
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 sattaking.in on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

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

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
3.5359999747016
95

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<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 `[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.
`<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"]`
Sattaking.in 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

Navigation

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

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 sattaking.in 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
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.6.0
jQuery UI
1.13.1
WordPress
5.9.3
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://sattaking.in/
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for sattaking.in. 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 sattaking.in 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

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 sattaking.in. 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 sattaking.in 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) 76
Performance 61
Accessibility 95
Best Practices 92
SEO 100
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://sattaking.in/
Updated: 27th April, 2022

3.56 seconds
First Contentful Paint (FCP)
28%
35%
37%

0.02 seconds
First Input Delay (FID)
93%
5%
2%

Simulate loading on mobile
61

Performance

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

Metrics

Speed Index — 2.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.5 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Sattaking.in should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Sattaking.in should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Sattaking.in should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Sattaking.in should consider minifying JS files.
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
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 210 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://sattaking.in/
211.661
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Sattaking.in should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://sattaking.in/
630
https://sattaking.in/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Sattaking.in 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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://sattaking.in/wp-content/plugins/ninja-tables/assets/js/ninja-tables-footable.3.1.0.js?ver=4.1.14
56
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 348 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://sattaking.in/wp-content/plugins/elementor/assets/lib/swiper/swiper.min.js?ver=5.3.6
37349
https://sattaking.in/
36185
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
32905
https://sattaking.in/wp-content/plugins/ninja-tables/public/libs/footable/js/footable.min.js?ver=3.1.5
21486
https://sattaking.in/wp-content/litespeed/css/f38f93e88b2129cdae723283a9b912c2.css?ver=efe73
21204
https://sattaking.in/wp-content/plugins/ninja-tables/assets/js/ninja-tables-footable.3.1.0.js?ver=4.1.14
18077
https://sattaking.in/wp-content/astra-local-fonts/oswald/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiZQ.woff2
16967
https://sattaking.in/wp-content/plugins/elementor/assets/js/preloaded-modules.min.js?ver=3.6.4
14179
https://sattaking.in/wp-content/litespeed/css/f6e290095b588c2fb2320773b865bf46.css?ver=6f4ca
14077
https://sattaking.in/wp-content/litespeed/css/185ea73c0af57470350821e4d235f8d5.css?ver=f608e
13854
Uses efficient cache policy on static assets — 1 resource found
Sattaking.in 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://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5618
Avoids an excessive DOM size — 503 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
503
Maximum DOM Depth
30
Maximum Child Elements
71
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Sattaking.in should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 36 requests • 348 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
36
356783
Script
17
189179
Stylesheet
13
97712
Document
1
36185
Font
3
32577
Other
2
1130
Image
0
0
Media
0
0
Third-party
3
20186
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
14568
0
5618
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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 — 20 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
4260
687
https://sattaking.in/
1539
427
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
3510
361
https://sattaking.in/wp-content/themes/astra/assets/js/minified/style.min.js?ver=3.7.10
3060
320
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
3871
315
https://sattaking.in/
1260
279
Unattributable
630
234
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
5343
228
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
6281
222
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
5834
221
https://sattaking.in/
2020
209
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
5638
193
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
5160
183
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
6121
160
https://sattaking.in/
864
79
https://sattaking.in/wp-content/plugins/elementor/assets/lib/swiper/swiper.min.js?ver=5.3.6
4947
74
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
6055
66
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
4186
55
https://sattaking.in/
1966
54
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
5571
54
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 sattaking.in on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://sattaking.in/
http/1.1
0
75.363999989349
723
0
301
text/plain
https://sattaking.in/
h2
75.8569999889
286.53300000587
36185
158378
200
text/html
Document
https://sattaking.in/wp-content/astra-local-fonts/oswald/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiZQ.woff2
h2
303.97400000948
429.57400000887
16967
16016
200
font/woff2
Font
https://sattaking.in/wp-content/litespeed/css/93739cfaa45b5e4b4d40d0d6ef9301ee.css?ver=106d0
h2
304.55299999448
451.10000000568
13175
71718
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/200d830a30185f9093708b9acb9fd730.css?ver=c1d67
h2
305.30800000997
473.46599999582
1379
1676
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/dcd716a031be105b24a01a5feeca56e3.css?ver=af4fa
h2
306.07600000803
475.40799999842
12295
83140
200
text/css
Stylesheet
https://sattaking.in/wp-includes/js/wp-emoji-release.min.js?ver=5.9.3
h2
486.03599998751
574.8859999876
5715
18181
200
application/x-javascript
Script
https://sattaking.in/wp-content/litespeed/css/dbe543bb54654390c315512b6179ce96.css?ver=4d664
h2
376.91399999312
576.70800000778
4756
19416
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/f7a423836b865226902f67686786827e.css?ver=5b9e3
h2
377.17600000906
496.77500000689
1777
13805
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/f38f93e88b2129cdae723283a9b912c2.css?ver=efe73
h2
377.54699998186
517.68099999754
21204
163227
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/cd677a18d23c70689d5fd01f55b4a86b.css?ver=19dc1
h2
377.99400000949
776.87299999525
1371
1452
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/185ea73c0af57470350821e4d235f8d5.css?ver=f608e
h2
378.28599999193
577.68600000418
13854
60316
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/a68b28ff52484dbbb53b43cab7781940.css?ver=0f249
h2
378.53300001007
487.66899999464
5137
26702
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/0402f63800a48183265e032db68906a9.css?ver=93bec
h2
378.80400000722
493.09499998344
2492
10933
200
text/css
Stylesheet
https://sattaking.in/wp-content/litespeed/css/f6e290095b588c2fb2320773b865bf46.css?ver=6f4ca
h2
379.19000000693
596.36100000353
14077
95615
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto+Slab%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CAlfa+Slab+One%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic&display=auto&ver=5.9.3
h2
379.56999999005
390.5509999895
2592
51294
200
text/css
Stylesheet
https://sattaking.in/wp-content/plugins/elementor/assets/lib/font-awesome/js/v4-shims.min.js?ver=3.6.4
h2
379.75299998652
474.07399999793
5177
15055
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/ninja-tables/assets/fonts/ninja-tables.woff2?1a82860cb5286f7833a2c33fbdd1d76c
h2
380.0699999847
490.63799998839
3634
2688
200
font/woff2
Font
https://sattaking.in/wp-content/litespeed/css/ad6685ae673257721cdfb15d02c3c323.css?ver=45821
h2
385.67799999146
699.49800000177
3603
18456
200
text/css
Stylesheet
https://sattaking.in/wp-content/themes/astra/assets/js/minified/style.min.js?ver=3.7.10
h2
385.96700000926
700.07600000827
3679
10398
200
application/x-javascript
Script
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
h2
386.29799999762
585.35700000357
32905
89521
200
application/x-javascript
Script
https://sattaking.in/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2
h2
386.72000000952
577.07100000698
5226
11224
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/ninja-tables/public/libs/footable/js/footable.min.js?ver=3.1.5
h2
387.0969999989
575.90199998231
21486
82971
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/ninja-tables/assets/js/ninja-tables-footable.3.1.0.js?ver=4.1.14
h2
387.51000000047
501.93399999989
18077
53549
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/js/webpack.runtime.min.js?ver=3.6.4
h2
387.9489999963
498.10699999216
3120
4960
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.6.4
h2
388.2680000097
485.28299998725
5708
14277
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/lib/waypoints/waypoints.min.js?ver=4.0.2
h2
388.60800000839
576.33700000588
4104
12198
200
application/x-javascript
Script
https://sattaking.in/wp-includes/js/jquery/ui/core.min.js?ver=1.13.1
h2
388.97100000759
502.56200000877
7970
20714
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/lib/swiper/swiper.min.js?ver=5.3.6
h2
389.3129999924
582.00200001011
37349
139153
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/lib/share-link/share-link.min.js?ver=3.6.4
h2
389.72199999262
574.06700000865
2056
2578
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/lib/dialog/dialog.min.js?ver=4.9.0
h2
390.12799999909
497.56799999159
4455
10682
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.6.4
h2
391.19900000514
575.48500000848
12355
37741
200
application/x-javascript
Script
https://sattaking.in/wp-content/plugins/elementor/assets/js/preloaded-modules.min.js?ver=3.6.4
h2
392.78799999738
777.46399998432
14179
43392
200
application/x-javascript
Script
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
486.49599999771
525.9950000036
5618
13970
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
894.78699999745
899.0899999917
11976
11048
200
font/woff2
Font
https://sattaking.in/cdn-cgi/rum?
h2
1529.1769999894
1596.0029999842
407
0
200
text/plain
XHR
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)
398.146
9.495
411.854
69.743
490.546
6.734
587.142
7.898
595.064
213.493
821.657
58.375
887.622
19.763
921.076
160.176
1081.265
26.898
1108.941
171.79
1281.615
18.405
1310.151
8.005
1320.166
90.304
1410.508
104.463
1520.891
78.626
1599.543
27.26
1634.588
45.745
1680.937
7.463
1699.751
7.106
1723.508
56.952
1789.66
13.525
2031.401
48.36
2125.339
55.191
2284.958
16.554
2340.501
39.875
2525.75
55.592
2581.352
6.047
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.5 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 6.5 s
The time taken for the page to become fully interactive.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 150 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Sattaking.in should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://sattaking.in/wp-content/plugins/elementor/assets/lib/font-awesome/js/v4-shims.min.js?ver=3.6.4
5177
150
Reduce unused CSS — Potential savings of 70 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Sattaking.in should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://sattaking.in/wp-content/litespeed/css/f38f93e88b2129cdae723283a9b912c2.css?ver=efe73
21204
20595
https://sattaking.in/wp-content/litespeed/css/185ea73c0af57470350821e4d235f8d5.css?ver=f608e
13854
13854
https://sattaking.in/wp-content/litespeed/css/f6e290095b588c2fb2320773b865bf46.css?ver=6f4ca
14077
13200
https://sattaking.in/wp-content/litespeed/css/dcd716a031be105b24a01a5feeca56e3.css?ver=af4fa
12295
12237
https://sattaking.in/wp-content/litespeed/css/93739cfaa45b5e4b4d40d0d6ef9301ee.css?ver=106d0
13175
12149
Reduce unused JavaScript — Potential savings of 33 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://sattaking.in/wp-content/plugins/elementor/assets/lib/swiper/swiper.min.js?ver=5.3.6
37349
33540
Reduce JavaScript execution time — 2.9 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://sattaking.in/
2404.472
351.86
15.252
https://sattaking.in/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
2326.76
2031.74
6.892
https://sattaking.in/wp-content/themes/astra/assets/js/minified/style.min.js?ver=3.7.10
641.496
198.372
0.796
Unattributable
445.708
12.372
0.484
https://sattaking.in/wp-includes/js/jquery/ui/core.min.js?ver=1.13.1
269.94
268.704
1.236

Metrics

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

Audits

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

Other

Minimize main-thread work — 6.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)
Script Evaluation
3064.244
Style & Layout
2099.592
Other
617.364
Parse HTML & CSS
370.168
Rendering
132.3
Script Parsing & Compilation
61.052
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
4.3029999942519
First Contentful Paint (3G) — 4860 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
95

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<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 `[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.
`<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"]`
Sattaking.in 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

Navigation

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

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 sattaking.in 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
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.6.0
jQuery UI
1.13.1
WordPress
5.9.3
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://sattaking.in/
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for sattaking.in. 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 sattaking.in on mobile screens.
Document uses legible font sizes — 69.06% 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
a, abbr, acronym, address, applet, big, blockquote, body, caption, cite, code, dd, del, dfn, div, dl, dt, em, fieldset, font, form, h1, h2, h3, h4, h5, h6, html, iframe, ins, kbd, label, legend, li, object, ol, p, pre, q, s, samp, small, span, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, ul, var
16.99%
11.856px
13.95%
< 12px
69.06%
≥ 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

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 sattaking.in. 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 sattaking.in 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: 172.67.168.104
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 21st April, 2022
Valid To: 21st April, 2023
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 17439579813070406777019898059197113429
Serial Number (Hex): 0D1EBDAB7CFAFEB526ECE1AF9C6DE455
Valid From: 21st April, 2024
Valid To: 21st April, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Apr 21 00:59:02.791 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:68:6A:C9:F4:96:D8:C7:7C:88:0C:97:4E:
EA:3F:2C:96:46:F5:1D:6D:FF:0C:5E:74:48:14:D4:F6:
D2:8A:B0:83:02:21:00:86:13:79:BA:B0:22:56:A1:F8:
D1:DC:F6:59:60:36:02:B6:FD:40:C3:8E:64:49:76:0E:
1F:73:03:BD:FE:6E:0F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Apr 21 00:59:02.833 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:7F:27:EE:D9:6A:89:B1:D8:4A:77:81:C2:
CA:E8:D5:88:58:1D:3B:CA:AC:C4:83:B1:AE:5A:15:AE:
DE:8A:65:FD:02:21:00:83:D4:F1:30:6A:B0:6E:AB:0A:
54:38:02:FA:9C:DE:B8:F1:E9:FD:3A:AA:F5:23:F8:FD:
E1:75:45:4D:89:A1:02
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Apr 21 00:59:02.896 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:73:81:15:0D:E1:0D:31:46:DB:C1:C1:9F:
8F:75:7D:DA:80:59:4E:ED:68:18:9E:D0:50:4A:4C:88:
A1:26:2F:8F:02:20:45:13:8E:51:D7:50:DF:2A:57:0B:
5E:CD:4E:DB:6C:4F:6B:42:2C:9F:87:6F:5B:90:B5:5A:
0F:5F:DE:E3:0F:90
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:sni.cloudflaressl.com
DNS:sattaking.in
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 27th April, 2022
Content-Type: text/html; charset=UTF-8
Server: cloudflare
Connection: keep-alive
x-powered-by: PHP/8.1.0
x-dns-prefetch-control: on
link: <https://sattaking.in/>; rel=shortlink
x-litespeed-cache: hit
content-security-policy: upgrade-insecure-requests
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
x-turbo-charged-by: LiteSpeed
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=9YYzRtlFFGbTWR66UMyodg82cMGGEnCKyjlSGBPHdKP4IdilW926sLNweEF1vnpNb01aq2BQ4SD9xTvEJqkUEXxsyf9KwHVduYVCvbayBWsVoVs4677FNvJ1CEINoaA%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 70268b496a06f031-EWR

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1.dns-parking.com
ns2.dns-parking.com
Full Whois:

Nameservers

Name IP Address
ns1.dns-parking.com 162.159.24.201
ns2.dns-parking.com 162.159.25.42
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
$224 USD
0/5
0/5

Sites hosted on the same IP address