Your Website Score is
SEO Rank : 28 Website URL: canadanepal.info Last Updated: 2 months
Success
47% of passed verification steps
Warning
30% of total warning
Errors
23% of total errors, require fast action
Share
Estimation Traffic and Earnings
0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 39%
Domain Authority
Domain Authority 26%
Moz Rank
3.9/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
127 Characters
CANADA NEPAL, NEPALI TOP SITE WITH NEPALI VIDEO ,NEPALI NEWS AND MUCH MORE-CANADANEPAL VISIT US ANYTIME HTTP://CANADANEPAL.NET
Meta Description
126 Characters
Canada Nepal, Nepali Top site with nepali video ,nepali News and Much More-CanadaNepal visit us anytime http://canadanepal.net
Effective URL
26 Characters
http://www.canadanepal.net
Excerpt
Page content
Canada Nepal, Nepali Top site with nepali video ,nepali News and Much More-CanadaNepal visit us anytime http://canadanepal.net
Index
Online TV
Video Page
Online FM
News Blog
Daily News
Type in Nepali
Contact Us
ह...
Google Preview
Your look like this in google search result
CANADA NEPAL, NEPALI TOP SITE WITH NEPALI VIDEO ,NEPALI NEW
http://www.canadanepal.net
Canada Nepal, Nepali Top site with nepali video ,nepali News and Much More-CanadaNepal visit us anytime http://canadanepal.net
Robots.txt
File No Found
Sitemap.xml
File No Found
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: 2020-02-12 / 11 months
Create on: 2010-03-15 / 11 years
Expires on: 2021-03-15 / 1 months 21 days
GoDaddy.com, LLC ,NP
Registrar Whois Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Nameservers
NS19.DOMAINCONTROL.COM
NS20.DOMAINCONTROL.COM
Page Size
Code & Text Ratio
Document Size: ~52.8 KB
Code Size: ~33.32 KB
Text Size: ~19.49 KB Ratio: 36.90%
Social Data
Delicious
Total: 0
Facebook
Total: 7,045
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
Reduce initial server response time
Root document took 1,190 ms
Keep the server response time for the main document short because all other requests depend on it
Serve images in next-gen formats
Potential savings of 1,256 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
Minimizes main-thread work
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Speed Index
1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive
0.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Remove unused JavaScript
Potential savings of 23 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid chaining critical requests
1 chain 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
Keep request counts low and transfer sizes small
70 requests • 6,035 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Max Potential First Input Delay
30 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid enormous network payloads
Total size was 6,035 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Serve static assets with an efficient cache policy
10 resources found
A long cache lifetime can speed up repeat visits to your page
Links do not have descriptive text
92 links found
Descriptive link text helps search engines understand your content
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Does not use HTTPS
68 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
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid long main-thread tasks
1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
First Meaningful Paint
0.5 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids an excessive DOM size
719 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)
Largest Contentful Paint
1.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Cumulative Layout Shift
0.007
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
First CPU Idle
0.5 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/).
Properly size images
Potential savings of 4,967 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
JavaScript execution time
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images
Potential savings of 72 KiB
Optimized images load faster and consume less cellular data
Mobile
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Efficiently encode images
Potential savings of 72 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint
1.5 s
First Contentful Paint marks the time at which the first text or image is painted
Links do not have descriptive text
92 links found
Descriptive link text helps search engines understand your content
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
Avoid chaining critical requests
1 chain 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
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Eliminate render-blocking resources
Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids an excessive DOM size
719 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 static assets with an efficient cache policy
10 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint (3G)
2653 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Remove unused JavaScript
Potential savings of 23 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Cumulative Layout Shift
0.019
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
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
JavaScript execution time
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Tap targets are not sized appropriately
67% 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
2.4 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/).
Keep request counts low and transfer sizes small
70 requests • 6,033 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid long main-thread tasks
4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimizes main-thread work
1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time
30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Max Potential First Input Delay
80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed Index
2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Serve images in next-gen formats
Potential savings of 1,478 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
Document uses legible font sizes
75.87% 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
2.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint
27.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint
1.5 s
First Meaningful Paint measures when the primary content of a page is visible
Does not use HTTPS
68 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
Avoid enormous network payloads
Total size was 6,033 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce initial server response time
Root document took 1,120 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize third-party usage
Third-party code blocked the main thread for 20 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
Properly size images
Potential savings of 3,922 KiB
Serve images that are appropriately-sized to save cellular data and improve load 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
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not 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
Congratulations! Your Domain Authority is good
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 20 Links | Relationship | HTTP Status |
| रत्नपार्क जंगिए भोकाहरु | Internal Link | 200 |
| Binod Anita Khadka | Internal Link | 200 |
| Keshav Kumar Sharma & Bhim Prasad Dhakal | Internal Link | 200 |
| A Mero Hajur 3 | Internal Link | 200 |
| BHARAT DAHAL | Internal Link | 200 |
| Bhim Rawal | Internal Link | 200 |
| सुरेन्द्र केसीको खुलासा | Internal Link | 200 |
| AAJ KA KHILADI 2 | Internal Link | 200 |
| Pralay The Destroyer | Internal Link | 200 |
| Besan ko Laddu | Internal Link | 200 |
| अनरसा | Internal Link | 200 |
| DAMAULI MANUNGKOT | Internal Link | 200 |
| First Impressions | Internal Link | 200 |
| Click Here | Internal Link | 200 |
| Click Here | Internal Link | 200 |
| Click Here | Internal Link | 200 |
| Click Here | Internal Link | 200 |
| Click Here | Internal Link | 200 |
| Click Here | Internal Link | 200 |
| Click Here | Internal Link | 200 |
Alexa Rank
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| canadanepal.co | Already Registered |
| canadanepal.us | Already Registered |
| canadanepal.com | Already Registered |
| canadanepal.org | Already Registered |
| canadanepal.net | Already Registered |
| cnadanepal.info | Already Registered |
| danadanepal.info | Already Registered |
| ranadanepal.info | 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
Date: Mon, 23 Nov 2020 00:05:03 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Set-Cookie: __cfduid=ddf4a77b738cf356e6ecee73d0e7b95701606089901; expires=Wed, 23-Dec-20 00:05:01 GMT; path=/; domain=.canadanepal.net; HttpOnly; SameSite=Lax
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
Vary: Accept-Encoding,User-Agent
Set-Cookie: ci_session=hav3h34l64r64ng6m41fl0gbr9o543gl; expires=Mon, 23-Nov-2020 02:05:02 GMT; Max-Age=7200; path=/; HttpOnly
CF-Cache-Status: DYNAMIC
cf-request-id: 0694041f290000e5165ca91000000001
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=bzUaCm3sVE94A4HiJvrjAJ%2FVpC2uHwZ7EshIr3yR6jaqw38J%2F82vHgIGPGB6%2FEqsdkOIZOWkA2YXUw%2BkwSGONnqqWAPsorhgvoDpONiMVb8szA4R"}],"group":"cf-nel","max_age":604800}
NEL: {"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 5f66a2deae74e516-LAX
Content-Encoding: gzip
Click to Add/Show Comments