Your Website Score is

Similar Ranking

14
PLAYTAMILHD.COM | PLAYTAMIL, TAMILPLAY 2020 TAMIL FULL MOVIES DOWNLOAD TAMIL HD MP4 FULL MOVIES FREE DOWNLOAD
xplaytamil.buzz
14
0123MOVIES.LA -&NBSPTHIS WEBSITE IS FOR SALE! -&NBSP0123MOVIES RESOURCES AND INFORMATION.
0123movies.la
14
9XMOVIE.BEST - REGISTERED AT NAMECHEAP.COM
9xmovie.best
14
9XMOVIES.VIP - REGISTERED AT NAMECHEAP.COM
9xmovies.vip
14
BEST BOOKS OF ALL TIME - READ NOVELS ONLINE
allnovel.net
14
WELCOME TO AMIA!
amiaworld.net
14
403 FORBIDDEN
andypioneer.com

Latest Sites

14
SARKARIYOJNAPLUS : LATEST SARKARI RESULTS | LATEST ONLINE FORM | LATEST GOVT SCHEMES - SAKARIYOJNAPLUS : PROVIDES INFORMATION LIKE, LATEST GOVT SCHEMES, LATEST GOVT RESULTS, LATEST GOVT JOBS, ADMIT CA
sarkariyojnaplus.com
10
IPDBSE - INSTANT PAYMENT EXCHANGE WALLET | SIGN IN
ipdbse.com
60
MP3JUICES - FREE MP3 DOWNLOADS
mp3juices.cc
38
IPKO – BANKOWOŚĆ ELEKTRONICZNA PKO BANKU POLSKIEGO
ipko.pl
23
INFOSTREAM SIGN IN / INFOSTREAM SE CONNECTER
infostream.toyota.ca
1
animephase.com Website SEO Rank Analysis by SEOWebsiteRank.com
animephase.com
6
BLAST | EARN FREE MONEY!
buxblast.com

Top Technologies

Apache.png
Apache
Web Servers
Google%20Font%20API.png
Google Font API
Font Scripts
CloudFlare.png
CloudFlare
CDN
Nginx.png
Nginx
Web Servers
Font%20Awesome.png
Font Awesome
Font Scripts
WordPress.png
WordPress
CMS
Twitter%20Bootstrap.png
Twitter Bootstrap
Web Frameworks
Microsoft.png
Windows Server
Operating Systems

SEO Rank : 14 Website URL: dreamlifeindia.biz Last Updated: 2 weeks

Success 55% of passed verification steps
Warning 15% of total warning
Errors 30% of total errors, require fast action

Estimation Traffic and Earnings

270
Unique Visits
Daily
499
Pages Views
Daily
$0
Income
Daily
7,560
Unique Visits
Monthly
14,222
Pages Views
Monthly
$0
Income
Monthly
87,480
Unique Visits
Yearly
167,664
Pages Views
Yearly
$0
Income
Yearly

Desktop

Mobile

Performance Desktop Score 70%
Best Practices Desktop Score 64%
SEO Desktop Score 73%
Progressive Web App Desktop Score 19%
Performance Mobile Score 38%
Best Practices Mobile Score 57%
SEO Mobile Score 74%
Progressive Web App Mobile Score 21%

Moz Authority Rank

Page Authority Authority 28%
Domain Authority Domain Authority 1%
Moz Rank 2.8/10
Bounce Rate Rate 0%

Meta Data

Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 16 Characters
DREAM LIFE INDIA
Meta Description 0 Characters
NO DATA
Effective URL 26 Characters
https://dreamlifeindia.biz
Excerpt Page content
DREAM LIFE INDIA Disclaimer Before venturing into our website, it is hereby inf...
Keywords Cloud Density
company14 business11 amity11 more9 direct8 website7 support7 does6 customer5 made4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
company 14
business 11
amity 11
more 9
direct 8
website 7
support 7
does 6
customer 5
made 4
Google Preview Your look like this in google search result
DREAM LIFE INDIA
https://dreamlifeindia.biz
DREAM LIFE INDIA Disclaimer Before venturing into our website, it is hereby inf...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~26.8 KB
Code Size: ~13.29 KB
Text Size: ~13.51 KB Ratio: 50.41%

Social Data

Delicious Total: 0
Facebook Total: 157
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Serve images in next-gen formats Potential savings of 3,327 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Keep request counts low and transfer sizes small 86 requests • 4,953 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Eliminate render-blocking resources Potential savings of 560 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint 4.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Estimated Input Latency 20 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
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/).
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Avoid enormous network payloads Total size was 4,953 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Initial server response time was short Root document took 280 ms
Keep the server response time for the main document short because all other requests depend on it
Minimizes main-thread work 1.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 18.1 s
A fast page load over a cellular network ensures a good mobile user experience
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Time to Interactive 1.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Remove unused JavaScript Potential savings of 663 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Does not use HTTPS 5 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Remove unused CSS Potential savings of 38 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
Includes front-end JavaScript libraries with known security vulnerabilities 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoids an excessive DOM size 412 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 chaining critical requests 15 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 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize third-party usage Third-party code blocked the main thread for 0 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
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Minify JavaScript Potential savings of 33 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Properly size images Potential savings of 926 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
JavaScript execution time 1.0 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.311
Cumulative Layout Shift measures the movement of visible elements within the viewport
Max Potential First Input Delay 120 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
robots.txt is not valid 18 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
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
Efficiently encode images Potential savings of 2,434 KiB
Optimized images load faster and consume less cellular data
Serve static assets with an efficient cache policy 40 resources found
A long cache lifetime can speed up repeat visits to your page

Mobile

Mobile Screenshot
robots.txt is not valid 18 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
First Contentful Paint (3G) 5851 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Includes front-end JavaScript libraries with known security vulnerabilities 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid enormous network payloads Total size was 4,954 KiB
Large network payloads cost users real money and are highly correlated with long load times
Tap targets are not sized appropriately 75% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Avoid chaining critical requests 15 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
Max Potential First Input Delay 740 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 2.9 s
First Contentful Paint marks the time at which the first text or image is painted
Minimize main-thread work 7.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small 85 requests • 4,954 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Eliminate render-blocking resources Potential savings of 1,680 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve static assets with an efficient cache policy 40 resources found
A long cache lifetime can speed up repeat visits to your page
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Time to Interactive 17.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Remove unused CSS Potential savings of 19 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
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First CPU Idle 8.1 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/).
Page load is not fast enough on mobile networks Interactive at 17.6 s
A fast page load over a cellular network ensures a good mobile user experience
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Largest Contentful Paint 3.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Properly size images Potential savings of 723 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Does not use HTTPS 5 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Estimated Input Latency 250 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 JavaScript Potential savings of 767 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Meaningful Paint 3.0 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Efficiently encode images Potential savings of 2,434 KiB
Optimized images load faster and consume less cellular data
Total Blocking Time 1,390 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids an excessive DOM size 412 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)
Serve images in next-gen formats Potential savings of 3,327 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Speed Index 7.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce JavaScript execution time 4.9 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.889
Cumulative Layout Shift measures the movement of visible elements within the viewport
Defer offscreen images Potential savings of 1,853 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce the impact of third-party code Third-party code blocked the main thread for 930 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
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Minify JavaScript Potential savings of 33 KiB
Minifying JavaScript files can reduce payload sizes and script parse time

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
Congratulations! Your title is 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
Congratulations! You are using your H1 and H2 tags in your site
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

Alexa Rank

0

Local Rank: / Users: / PageViews:

864,329

Global Rank

Domain Available

Domain (TDL) and Typo Status
dreamlifeindia.co Already Registered
dreamlifeindia.us Already Registered
dreamlifeindia.com Already Registered
dreamlifeindia.org Already Registered
dreamlifeindia.net Already Registered
deamlifeindia.biz Already Registered
ereamlifeindia.biz Already Registered
creamlifeindia.biz Already Registered

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
cache-control: private
content-length: 27434
content-type: text/html
server: Microsoft-IIS/10.0
set-cookie: ASPSESSIONIDQGBTCAAS=GFDJLACDIPFCELGMKOBKAJIN; secure; path=/
x-powered-by: ASP.NET
x-powered-by-plesk: PleskWin
date: Wed, 14 Oct 2020 00:15:41 GMT

View DNS Records

DNS Records DNS Resource Records associated with a hostname
Type Name Value Class TTL
A dreamlifeindia.biz 67.227.166.160 IN 86301
NS dreamlifeindia.biz wns12.edns1.com IN 86400
NS dreamlifeindia.biz wns11.edns1.com IN 86400
NS dreamlifeindia.biz wns12.fastwebhost.com IN 86400
NS dreamlifeindia.biz wns11.fastwebhost.com IN 86400
MX dreamlifeindia.biz mail.dreamlifeindia.biz IN 86400

Comments

dreamlifeindia.biz Stats By Traffic Tips Alexa Server Meta Authority Technologies Pagespeed Pagespeed Stats Social Domain Available
Add extension to Chrome