Your Website Score is

Similar Ranking

29
BDMUSIC23 | BDMUSIC,HDMUSIC23,BDMUSIC99,BDMUSIC 99,BD MUSIC,9XMOVIE,9KMOVIE,7STARHD
bdmusic23.com
29
首頁QDRAMA線上看
dramasq.com
29
MP3JUICES MUSIC DOWNLOADS MP3 FREE
imp3juices.com
29
403 FORBIDDEN
indianhotcomics.com
29
KALITE18.XYZ -&NBSPKALITE18 RESOURCES AND INFORMATION.
kalite18.xyz
29
MEJORTORRENT - DESCARGAR TORRENTS DE PELICULAS SERIES Y ESTRENOS
mejortorrent1.com
29
WORDPRESS › ERROR
myknowpega.com

Latest Sites

24
마이비누닷컴:::MYBINOO -최신영화,한국영화,미드 다시보기 스트리밍 사이트
mybinoo.com
22
INFORMATION WORLDS
informationworlds.in
41
WATCH HD MOVIES, TV SERIES ONLINE FREE - NOVAMOVIE.NET
novamovie.net
38
HEARTBEATSK.COM ALL INFORMATIONS IN HINDI
heartbeatsk.com
15
HINDI MARATHI SMS | SMS IN HINDI & MARATHI FONT ONLY
hindimarathisms.com
30
DRAWASAURUS - MULTIPLAYER DRAWING & GUESSING GAME!
drawasaurus.org
29
LEARN EVERYTHING ABOUT AGILE AND AGILITY- AGILEMANIA
agilemania.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 : 29 Website URL: dollarrupee.in Last Updated: 1 month

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

Estimation Traffic and Earnings

1,318
Unique Visits
Daily
2,438
Pages Views
Daily
$6
Income
Daily
36,904
Unique Visits
Monthly
69,483
Pages Views
Monthly
$150
Income
Monthly
427,032
Unique Visits
Yearly
819,168
Pages Views
Yearly
$1,584
Income
Yearly

Desktop

Mobile

Performance Desktop Score 88%
Best Practices Desktop Score 64%
SEO Desktop Score 91%
Progressive Web App Desktop Score 22%
Performance Mobile Score 44%
Best Practices Mobile Score 71%
SEO Mobile Score 91%
Progressive Web App Mobile Score 25%

Moz Authority Rank

Page Authority Authority 37%
Domain Authority Domain Authority 22%
Moz Rank 3.7/10
Bounce Rate Rate 0%

Meta Data

Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 94 Characters
DOLLAR TO RUPEE - USD TO INR TODAY AND FORECAST FOR TOMORROW, WEEK, MONTH, 2020, 2021 IN INDIA
Meta Description 155 Characters
USD to INR now, FORECAST, converter. Dollar to Rupee (USD to INR) forecast for tomorrow, week, month, 2020 and 2021. Should I BUY or SELL Dollars and when?
Effective URL 21 Characters
http://dollarrupee.in
Excerpt Page content
DOLLAR TO RUPEE - USD TO INR TODAY AND FORECAST FOR TOMORROW, WEEK, MONTH, 2020, 2021 IN INDIA INDIAN RUPEE THE ECONOMY FORECAST AGENCY ...
Keywords Cloud Density
rate59 forecast55 exchange35 rupees34 minimum33 maximum33 dollar33 month25 rupee24 september19
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
rate 59
forecast 55
exchange 35
rupees 34
minimum 33
maximum 33
dollar 33
month 25
rupee 24
september 19
Google Preview Your look like this in google search result
DOLLAR TO RUPEE - USD TO INR TODAY AND FORECAST FOR TOMORROW
http://dollarrupee.in
USD to INR now, FORECAST, converter. Dollar to Rupee (USD to INR) forecast for tomorrow, week, month, 2020 and 2021. Should I BUY or SELL Dollars and
Robots.txt File Detected
Sitemap.xml File Detected
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 2018-05-09 / 2 years
Create on: 2015-05-24 / 5 years
Expires on: 2019-05-24 / 17 months 5 days

eNom, Inc. ,RU
Registrar URL: www.enom.com

Nameservers
NS1.C16290.SGVPS.NET
NS2.C16290.SGVPS.NET
Page Size Code & Text Ratio
Document Size: ~76.5 KB
Code Size: ~53.28 KB
Text Size: ~23.22 KB Ratio: 30.35%

Social Data

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

Technologies

PWA - Manifest

DollarRupee DollarRupee DollarRupee

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)
Param name
DollarRupee
Param short name
DollarRupee
Param theme color
#ffffff
Param background color
#ffffff
Manifest is not valid
Your manifest are missing some important params, read more in Web App Manifest

Desktop

Desktop Screenshot
Remove unused CSS Potential savings of 32 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
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
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 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
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize main-thread work 3.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Does not use HTTPS 23 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
Initial server response time was short Root document took 310 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Serve images in next-gen formats Potential savings of 137 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
Minimize third-party usage Third-party code blocked the main thread for 180 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
Efficiently encode images Potential savings of 5 KiB
Optimized images load faster and consume less cellular data
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
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
Reduce JavaScript execution time 1.6 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.122
Cumulative Layout Shift measures the movement of visible elements within the viewport
Keep request counts low and transfer sizes small 137 requests • 1,455 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids enormous network payloads Total size was 1,455 KiB
Large network payloads cost users real money and are highly correlated with long load times
Time to Interactive 3.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time 170 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Remove unused JavaScript Potential savings of 412 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Estimated Input Latency 30 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
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve static assets with an efficient cache policy 42 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint 0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 14.0 s
A fast page load over a cellular network ensures a good mobile user experience
Minify CSS Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes
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
First CPU Idle 2.9 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/).
Avoid an excessive DOM size 1,146 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)

Mobile

Mobile Screenshot
First Contentful Paint 2.4 s
First Contentful Paint marks the time at which the first text or image is painted
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
User Timing marks and measures 3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Serve static assets with an efficient cache policy 25 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources Potential savings of 1,820 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Tap targets are not sized appropriately 89% 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
First CPU Idle 10.8 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/).
Time to Interactive 12.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Remove unused CSS Potential savings of 32 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
Remove unused JavaScript Potential savings of 407 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids enormous network payloads Total size was 1,041 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 0.331
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 2.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint (3G) 4612.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Max Potential First Input Delay 240 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minify CSS Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes
Estimated Input Latency 90 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Reduce JavaScript execution time 5.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint 2.4 s
First Meaningful Paint measures when the primary content of a page is visible
Page load is not fast enough on mobile networks Interactive at 12.3 s
A fast page load over a cellular network ensures a good mobile user experience
Does not use HTTPS 27 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
Minimize main-thread work 11.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
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 large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
Total Blocking Time 1,640 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Avoid an excessive DOM size 1,100 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)
Keep request counts low and transfer sizes small 106 requests • 1,041 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Speed Index 8.5 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Document uses legible font sizes 99.78% 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
Initial server response time was short Root document took 60 ms
Keep the server response time for the main document short because all other requests depend on it

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
Warning! Your website is not SSL secured (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
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

19,437

Local Rank: IN / Users: 53.3% / PageViews: 54.5%

99,357

Global Rank

Domain Available

Domain (TDL) and Typo Status
dollarrupee.co Already Registered
dollarrupee.us Already Registered
dollarrupee.com Already Registered
dollarrupee.org Already Registered
dollarrupee.net Already Registered
dllarrupee.in Already Registered
eollarrupee.in Already Registered
collarrupee.in Already Registered

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 12 Sep 2020 00:07:05 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
X-Cache-Enabled: True
Expires: Sat, 12 Sep 2020 00:22:05 GMT
Set-Cookie: 87cd3ec329289c7494c86c6f696bf020=0f39093921a364fcaa6cf790c5c59caf; path=/; HttpOnly
X-Content-Type-Options: nosniff
X-Httpd: 1
Host-Header: 8441280b0c35cbc1147f8ba998a563a7
X-Proxy-Cache-Info: DT:1
Content-Encoding: gzip

View DNS Records

DNS Records DNS Resource Records associated with a hostname
Type Name Value Class TTL
A dollarrupee.in 35.208.157.92 IN 543
NS dollarrupee.in ns2.c16290.sgvps.net IN 86400
NS dollarrupee.in ns1.c16290.sgvps.net IN 86400
MX dollarrupee.in mx10.mailspamprotection.com IN 14400
MX dollarrupee.in mx30.mailspamprotection.com IN 14400
MX dollarrupee.in mx20.mailspamprotection.com IN 14400
TXT dollarrupee.in v=spf1 ip4:35.208.157.92 +a +mx +ip4:216.172.189.75 +ip4:108.175.159.162 include:_spf.mailspamprotection.com ~all IN 86400

Comments

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