Chmfire.Ca - Info receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Richmond Hill, Ontario, L4C, Canada and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

Font Scripts
Font Awesome
Web Servers
Yoast SEO
JavaScript Libraries
jQuery Migrate
Programming Languages
MySQL Profile

Title: HOME | CHM Fire
Last update was 55 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Server Location:
Richmond Hill
Ontario, ON
Canada, CA

Other sites hosted on

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
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. Learn more.
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. Learn more.
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 1,169 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

272 KB
215 KB
134 KB
110 KB
59 KB
59 KB
56 KB
53 KB
36 KB
32 KB
Minimizes main-thread work - 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Script Evaluation
283 ms
Style & Layout
116 ms
67 ms
65 ms
Parse HTML & CSS
30 ms
Script Parsing & Compilation
19 ms
Serve images in next-gen formats - Potential savings of 337 KB
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. Learn more.

SizePotential Savings
215 KB110 KB
110 KB79 KB
271 KB53 KB
59 KB40 KB
53 KB31 KB
36 KB24 KB
Avoids an excessive DOM size - 282 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Keep request counts low and transfer sizes small - 24 requests • 1,169 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
241169 KB
8750 KB
7181 KB
5144 KB
386 KB
18 KB
00 KB
00 KB
4128 KB
Eliminate render-blocking resources - Potential savings of 200 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
1 KB70
28 KB270
56 KB390
32 KB310
4 KB110
Efficiently encode images - Potential savings of 17 KB
Optimized images load faster and consume less cellular data. Learn more.

SizePotential Savings
110 KB10 KB
36 KB7 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms638 ms8 KB38 KB200text/htmlDocument
650 ms685 ms1 KB2 KB200text/cssStylesheet
650 ms728 ms28 KB192 KB200text/cssStylesheet
650 ms769 ms56 KB511 KB200text/cssStylesheet
651 ms720 ms32 KB95 KB200application/javascriptScript
651 ms719 ms4 KB10 KB200application/javascriptScript
651 ms687 ms3 KB3 KB200image/pngImage
652 ms751 ms2 KB1 KB200image/pngImage
688 ms722 ms4 KB14 KB200application/javascriptScript
723 ms759 ms1 KB1 KB200application/javascriptScript
752 ms828 ms134 KB564 KB200application/javascriptScript
760 ms795 ms1 KB1 KB200application/javascriptScript
812 ms864 ms4 KB12 KB200application/javascriptScript
828 ms897 ms59 KB59 KB200image/jpegImage
829 ms1027 ms272 KB271 KB200image/jpegImage
829 ms896 ms36 KB36 KB200image/jpegImage
829 ms867 ms110 KB110 KB200image/jpegImage
829 ms898 ms53 KB53 KB200image/jpegImage
832 ms836 ms18 KB26 KB200font/ttfFont
833 ms837 ms24 KB45 KB200font/ttfFont
833 ms929 ms16 KB16 KB200font/woffFont
834 ms839 ms26 KB53 KB200font/ttfFont
837 ms844 ms59 KB95 KB200font/ttfFont
1094 ms1257 ms215 KB215 KB200image/jpegImage
Serve static assets with an efficient cache policy - 19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
604800000 ms272 KB
604800000 ms215 KB
604800000 ms134 KB
604800000 ms110 KB
604800000 ms59 KB
604800000 ms56 KB
604800000 ms53 KB
604800000 ms36 KB
604800000 ms32 KB
604800000 ms28 KB
604800000 ms16 KB
604800000 ms4 KB
604800000 ms4 KB
604800000 ms4 KB
604800000 ms3 KB
604800000 ms2 KB
604800000 ms1 KB
604800000 ms1 KB
604800000 ms1 KB
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
661 ms
6 ms
669 ms
35 ms
749 ms
6 ms
792 ms
18 ms
809 ms
25 ms
835 ms
40 ms
885 ms
14 ms
904 ms
174 ms
1085 ms
11 ms
1100 ms
44 ms
1154 ms
9 ms
1295 ms
7 ms
1312 ms
13 ms
1325 ms
8 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
4 ms
5 ms
96 ms
6 ms
7 ms
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. Learn more.

Total CPU TimeScript EvaluationScript Parse
242 ms11 ms1 ms
183 ms155 ms2 ms
111 ms77 ms12 ms
Remove unused CSS - Potential savings of 81 KB
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. Learn more.

SizePotential Savings
56 KB54 KB
28 KB27 KB
Avoid chaining critical requests - 14 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 640 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

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. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

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. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Currently Not Available

+ Does use compression? use br compression.
Original size: 37.62 KB
Compressed size: 7.45 KB
File reduced by: 30.18 KB (80%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name:
Issuer: cPanel, Inc. Certification Authority
Valid from: Dec 16 00:00:00 2019 GMT
Valid until: Mar 15 23:59:59 2020 GMT

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Set-Cookie: wfvt_3953202846=5e08a40f84856; expires=Sun, 29-Dec-2019 13:33:11 GMT; Max-Age=1800; path=/; HttpOnly
Content-Type: text/html; charset=UTF-8
Link: <>; rel=""
Link: <>; rel=shortlink
Transfer-Encoding: chunked
Content-Encoding: br
Vary: Accept-Encoding
Date: Sun, 29 Dec 2019 13:03:11 GMT
Server: LiteSpeed
Connection: Keep-Alive

+ DNS Lookup

Type Ip Target TTL
MX 3600
SOA 3600
Serial Number 2019042905
Refresh 3600
Retry 1800
Expire 1209600
Minimum TTL 0
TXT 3600
TXT 3600
A 3559
NS 3558
NS 3558

+ Whois Lookup

Domain Created:
Domain Age:
8 years 1 months 29 days  

whois lookup at
Domain Name:
Registry Domain ID: 2752940-CIRA
Registrar WHOIS Server:
Registrar URL:
Updated Date: 2019-08-25T23:00:33Z
Creation Date: 2011-10-31T14:05:26Z
Registry Expiry Date: 2020-10-31T14:05:26Z
Registrar: HEXONET Services Inc.
Registrar IANA ID:
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: ok
Registry Registrant ID: 32601032-CIRA
Registrant Name: CHM Fire Consultants Ltd
Registrant Organization:
Registrant Street: 239 Glebe Ave.
Registrant City: Ottawa
Registrant State/Province: ON
Registrant Postal Code: K1S2C8
Registrant Country: CA
Registrant Phone: +1.6132345***
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID: 32601033-CIRA
Admin Name: Steven Craft
Admin Organization: CHM Fire Consultants Ltd
Admin Street: 239 Glebe Ave.
Admin City: Ottawa
Admin State/Province: ON
Admin Postal Code: K1S2C8
Admin Country: CA
Admin Phone: +1.6132345***
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: email
Registry Tech ID: 32601034-CIRA
Tech Name: Doma Ministrator
Tech Organization:
Tech Street: 11 Mary St, Suite 200
Tech City: Sudbury
Tech State/Province: ON
Tech Postal Code: P3C1B6
Tech Country: CA
Tech Phone: +1.6464010964
Tech Phone Ext:
Tech Fax: +1.8888821489
Tech Fax Ext:
Tech Email: email
Registry Billing ID:
Billing Name:
Billing Organization:
Billing Street:
Billing City:
Billing State/Province:
Billing Postal Code:
Billing Country:
Billing Phone:
Billing Phone Ext:
Billing Fax:
Billing Fax Ext:
Billing Email:
Name Server:
Name Server:
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form:
>>> Last update of WHOIS database: 2019-12-29T13:03:44Z <<<

For more information on Whois status codes, please visit

% Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal
% Notice, available at
% (c) 2019 Canadian Internet Registration Authority, (
Last update was 55 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites
44 secs
1 min
2 mins
2 mins
3 mins
4 mins
4 mins
4 mins
4 mins
5 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget