Your Website Score is
SEO Rank : 5 Website URL: mytopguessing.in Last Updated: 2 months
Success
40% of passed verification steps
Warning
30% of total warning
Errors
30% of total errors, require fast action
Share
Estimation Traffic and Earnings
524
Unique Visits
Daily
969
Pages Views
Daily
$4
Income
Daily
14,672
Unique Visits
Monthly
27,617
Pages Views
Monthly
$100
Income
Monthly
169,776
Unique Visits
Yearly
325,584
Pages Views
Yearly
$1,056
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 18%
Domain Authority
Domain Authority 5%
Moz Rank
1.8/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
84 Characters
MY TOP GUESSING - SATTA KING CHART | SATTA GUESSES COMPANY | RAJA SATTA KING ROCKS
Meta Description
281 Characters
My Top Guessing is one of most popular reliable satta king Result provider website in all over India . We are the Satta Guesses Company of satta gali and disawar satta game, matka game are good all satta industry. Get sattaking result with satta bazar help Raja Satta King Rocks.
Effective URL
28 Characters
https://www.mytopguessing.in
Excerpt
Page content
Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home1/mytopf6z/public_html/tara/db/sql.php on line 6
My Top Guessing - Satta King Chart | Satta Guesses Company...
Meta Keywords
20 Detected
Google Preview
Your look like this in google search result
MY TOP GUESSING - SATTA KING CHART | SATTA GUESSES COMPANY
https://www.mytopguessing.in
My Top Guessing is one of most popular reliable satta king Result provider website in all over India . We are the Satta Guesses Company of satta gal
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~32.15 KB
Code Size: ~13.59 KB
Text Size: ~18.55 KB Ratio: 57.71%
Social Data
Desktop
Time to Interactive
1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time
70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Defer offscreen images
Potential savings of 2 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Eliminate render-blocking resources
Potential savings of 220 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Meaningful Paint
0.6 s
First Meaningful Paint measures when the primary content of a page is visible
Serve static assets with an efficient cache policy
17 resources found
A long cache lifetime can speed up repeat visits to your page
Remove unused CSS
Potential savings of 25 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Initial server response time was short
Root document took 540 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Minimize third-party usage
Third-party code blocked the main thread for 70 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
JavaScript execution time
0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Speed Index
1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid long main-thread tasks
2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Keep request counts low and transfer sizes small
101 requests • 662 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids enormous network payloads
Total size was 662 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minify CSS
Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Remove unused JavaScript
Potential savings of 85 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimizes main-thread work
1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid chaining critical requests
9 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle
1.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Largest Contentful Paint
0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Max Potential First Input Delay
100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Avoids an excessive DOM size
439 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Cumulative Layout Shift
1.044
Cumulative Layout Shift measures the movement of visible elements within the viewport
Mobile
First CPU Idle
7.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Largest Contentful Paint
2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy
17 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests
11 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Total Blocking Time
1,170 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize main-thread work
5.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused JavaScript
Potential savings of 84 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Contentful Paint (3G)
3060 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Keep request counts low and transfer sizes small
84 requests • 663 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids an excessive DOM size
431 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Avoid long main-thread tasks
16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Time to Interactive
8.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce initial server response time
Root document took 2,830 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint
1.6 s
First Contentful Paint marks the time at which the first text or image is painted
First Meaningful Paint
2.4 s
First Meaningful Paint measures when the primary content of a page is visible
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Eliminate render-blocking resources
Potential savings of 720 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce JavaScript execution time
3.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift
0.013
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,150 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Estimated Input Latency
160 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS
Potential savings of 25 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Avoids enormous network payloads
Total size was 663 KiB
Large network payloads cost users real money and are highly correlated with long load times
Defer offscreen images
Potential savings of 2 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Minify CSS
Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Speed Index
8.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay
460 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links
View links
| First 11 Links | Relationship | HTTP Status |
| होम पेज | Internal Link | 301 |
| फ्री फोरम | Internal Link | 301 |
| विजनिस फोरम | Internal Link | 301 |
| गोल्ड फोरम | Internal Link | 301 |
| चेटिन्ग फोरम | Internal Link | 301 |
| नई I.D. बनायें | Internal Link | 301 |
| लॉगिन करें | Internal Link | 301 |
| पॉइंट टेबल | Internal Link | 301 |
| सभी सट्टा रिज़ल्ट चार्ट | Internal Link | 301 |
| Registration | Internal Link | 301 |
| Booking Forum | Internal Link | 301 |
Alexa Rank
45,590
Local Rank: IN / Users: 100.0% / PageViews: 100.0%350,278
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| mytopguessing.co | Available Buy Now! |
| mytopguessing.us | Available Buy Now! |
| mytopguessing.com | Already Registered |
| mytopguessing.org | Available Buy Now! |
| mytopguessing.net | Available Buy Now! |
| mtopguessing.in | Available Buy Now! |
| jytopguessing.in | Available Buy Now! |
| iytopguessing.in | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Thu, 06 Aug 2020 14:53:14 GMT
server: Apache
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
pragma: no-cache
set-cookie: PHPSESSID=53dd33b5432fdf6b4a4593a9f4c7a2e3; path=/
content-type: text/html; charset=UTF-8
Click to Add/Show Comments