Cmscanvas.Com - Website Report

Cmscanvas.Com

Traffic estimate for Cmscanvas.com is about N/A unique visits and N/A page views per day. Each unique visitor makes about N/A page views on average. According to traffic estimate, Cmscanvas.com should earn about N/A per day from the advertising revenue, which implies that this website is worth about N/A. Alexa Traffic Rank estimates that it is ranked number 0 in the world and less then 0.0001% of global Internet users are visiting Cmscanvas.com on a regular basis. Website hosting location for Cmscanvas.com is: Montreal, QC, H3A, Canada. Server IP address: 167.114.142.2


About - cmscanvas.com

Edit WebSite Info

Earnings Report

Website Value: N/A
Daily Revenue: N/A
Monthly Revenue: N/A
Yearly Revenue: N/A

Traffic Report

Daily Unique Visitors: N/A
Monthly Unique Visitors: N/A
Daily Pageviews: N/A (N/A per day)
Montly Pageviews: N/A
Daily PageViews Per User: N/A
Alexa Global Rank: 0
Alexa Reach: less then 0.0001% of global Internet users
Alexa Backlinks: 12
Average Page Load Time: 942

Country Report

Currently Not Available

Contributing Subdomains

Currently Not Available

Social Report


Hosting Info

cmscanvas.com Server Location
Server IP: 167.114.142.2
ASN: AS16276
ISP: OVH SAS
Server Location: Montreal QC H3A Canada

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Reputation / Confidence
Trustworthiness: N/A
Child safety: N/A
MyWOT Categories: N/A

Google PageSpeed Insights

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 6 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:
http://www.google.com/adsense/domains/caf.js
http://images.smartname.com/scripts/nmads_caf_20170727.js
http://images.smartname.com/scripts/frontend.js
http://images.smartname.com/scripts/cookies.js
http://images.smartname.com/scripts/nm_ga_top_20170727.js
http://images.smartname.com/scripts/nm_ga_bottom.js

Optimize CSS Delivery of the following:
http://images.smartname.com/styles/template/Simple2C_CAF.css
http://fonts.googleapis.com/css?family=Lato:400,700

Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://cmscanvas.com/
http://cmscanvas.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJqcyI6MX0.fADWc9hUOlh58R9UzufQBROmie3I7c7vE835oE6YmU4&uuid=a1fbe0a0-f84a-11e7-b562-5aa6b103665c
http://ww1.cmscanvas.com/

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://images.smartname.com/scripts/cookies.js (expiration not specified)
http://images.smartname.com/scripts/frontend.js (expiration not specified)
http://images.smartname.com/scripts/nm_ga_bottom.js (expiration not specified)
http://images.smartname.com/scripts/nm_ga_top_20170727.js (expiration not specified)
http://images.smartname.com/scripts/nmads_caf_20170727.js (expiration not specified)
http://images.smartname.com/styles/template/Simple2C_CAF.css (expiration not specified)
http://www.google.com/adsense/domains/caf.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)

Reduce server response time

In our test, your server responded in 0.57 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
None of the final above-the-fold content could be rendered even with the full HTML response.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 1.5KiB (28% reduction).
Minifying http://ww1.cmscanvas.com/ could save 1.5KiB (28% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 1KiB (34% reduction).
Minifying http://images.smartname.com/scripts/cookies.js could save 487B (52% reduction) after compression.
Minifying http://images.smartname.com/scripts/frontend.js could save 348B (26% reduction) after compression.
Minifying http://images.smartname.com/scripts/nmads_caf_20170727.js could save 126B (27% reduction) after compression.
Minifying http://images.smartname.com/scripts/nm_ga_top_20170727.js could save 110B (25% reduction) after compression.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 370B (18% reduction).
Minifying http://images.smartname.com/styles/template/Simple2C_CAF.css could save 370B (18% reduction) after compression.

Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 101B (18% reduction).
Compressing http://afs.googleusercontent.com/dp-namemedia/bullet-arrows-orange.png could save 101B (18% reduction).

Enable compression

You have compression enabled. Learn more about enabling compression.

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
Too many requests renders only 6 pixels tall (16 CSS pixels) final.

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
Configure a viewport for this page.

Size tap targets appropriately

All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.

Size content to viewport

The contents of your page fit within the viewport. Learn more about sizing content to the viewport.

Prioritize visible content

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

Optimize images

Your images are optimized. Learn more about optimizing images.

Eliminate render-blocking JavaScript and CSS in above-the-fold content

You have no render-blocking resources. Learn more about removing render-blocking resources.

Minify JavaScript

Your JavaScript content is minified. Learn more about minifying JavaScript.

Minify HTML

Your HTML is minified. Learn more about minifying HTML.

Minify CSS

Your CSS is minified. Learn more about minifying CSS.

Reduce server response time

Your server responded quickly. Learn more about server response time optimization.

Leverage browser caching

You have enabled browser caching. Learn more about browser caching recommendations.

Enable compression

You have compression enabled. Learn more about enabling compression.

Avoid plugins

Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.

Avoid landing page redirects

Your page has no redirects. Learn more about avoiding landing page redirects.

Http Header

Currently Not Available

DNS Lookup

Type Ip Target TTL
A 167.114.142.2 598
NS ns1.dnsnuts.com 598
NS ns2.dnsnuts.com 598
SOA 600

WhoIs Lookup

Domain Created: 2017-07-28
Domain Age: 6 months
WhoIs:
WhoIs lookup results from whois.verisign-grs.com server:

Domain Name: CMSCANVAS.COM
Registry Domain ID: 2147705265_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.web.com
Registrar URL: http://www.networksolutions.com
Updated Date: 2017-07-28T23:30:19Z
Creation Date: 2017-07-28T18:02:35Z
Registry Expiry Date: 2018-07-28T18:02:35Z
Registrar: ! #1 Host China, Inc.
Registrar IANA ID: 970
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8003337680
Domain Status: ok https://icann.org/epp#ok
Name Server: NS1.DNSNUTS.COM
Name Server: NS2.DNSNUTS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-01-13T10:14:48Z <<<
For more information on Whois status codes, please visit https://icann.

-------------
WhoIs lookup results for cmscanvas.com from whois.crsnic.net server:

Domain Name: CMSCANVAS.COM
Registry Domain ID: 2147705265_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.web.com
Registrar URL: http://www.networksolutions.com
Updated Date: 2017-07-28T23:30:19Z
Creation Date: 2017-07-28T18:02:35Z
Registry Expiry Date: 2018-07-28T18:02:35Z
Registrar: ! #1 Host China, Inc.
Registrar IANA ID: 970
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8003337680
Domain Status: ok https://icann.org/epp#ok
Name Server: NS1.DNSNUTS.COM
Name Server: NS2.DNSNUTS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-01-13T10:14:48Z <<<
For more information on Whois status codes, please visit https://icann.