coquitlam.ca website information.
coquitlam.ca domain name is registered by .CA top-level domain registry. See the other sites registred in .CA domain zone.
Following name servers are specified for coquitlam.ca domain:
- ns4.coquitlam.ca
- ns3.coquitlam.ca
and probably website coquitlam.ca is hosted by GOOGLE - Google LLC, US web hosting company. Check the complete list of other most popular websites hosted by GOOGLE - Google LLC, US hosting company.
According to Alexa traffic rank the highest website coquitlam.ca position was 118367 (in the world). The lowest Alexa rank position was 155570. Now website coquitlam.ca ranked in Alexa database as number 129559 (in the world).
Website coquitlam.ca Desktop speed measurement score (40/100) is better than the results of 14.88% of other sites shows that the page desktop performance can be improved.
coquitlam.ca Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of coquitlam.ca (46/100) is better than the results of 27.13% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Jan-16-2025 | 129,559 | 1,284 |
| Jan-15-2025 | 130,843 | -1,879 |
| Jan-14-2025 | 128,964 | -1,164 |
| Jan-13-2025 | 127,800 | 2,208 |
| Jan-12-2025 | 130,008 | -1,196 |
| Jan-11-2025 | 128,812 | -1,441 |
| Jan-10-2025 | 127,371 | 987 |
Advertisement
coquitlam.ca Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
coquitlam.ca whois
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, but is also used for a wider range of other information.
Domain Name: coquitlam.ca
Registry Domain ID: D120554-CIRA
Registrar WHOIS Server: whois.ca.fury.ca
Registrar URL: http://www.caregistration.com
Updated Date: 2024-07-24T04:01:56Z
Creation Date: 2002-07-30T23:32:56Z
Registry Expiry Date: 2032-07-24T04:00:00Z
Registrar: (CAregistration.com) Add Value International Inc.
Registrar IANA ID: not applicable
Registrar Abuse Contact Email: danny@addvalue.com
Registrar Abuse Contact Phone: +1.4168292290
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: R95815-CIRA
Registrant Name: City of Coquitlam
Registrant Organization:
Registrant Street: 3000 Guildford Way
Registrant City: Coquitlam
Registrant State/Province: BC
Registrant Postal Code: V3B7N2
Registrant Country: CA
Registrant Phone: +1.6049273614
Registrant Phone Ext:
Registrant Fax: +1.6049273615
Registrant Fax Ext:
Registrant Email: dbrowett@coquitlam.ca
Registry Admin ID: C1026151-CIRA
Admin Name: Darlene Soque
Admin Organization: City of Coquitlam
Admin Street: 3000 Guildford Way
Admin City: Coquitlam
Admin State/Province: BC
Admin Postal Code: V3B7N2
Admin Country: CA
Admin Phone: +1.6049273627
Admin Phone Ext:
Admin Fax: +1.6049273615
Admin Fax Ext:
Admin Email: dsoque@coquitlam.ca
Registry Tech ID: C1349971-CIRA
Tech Name: Jeffrey Kwon
Tech Organization: City of Coquitlam
Tech Street: 3000 Guildford
Tech City: Coquitlam
Tech State/Province: BC
Tech Postal Code: V3B7N2
Tech Country: CA
Tech Phone: +1.6049273629
Tech Phone Ext:
Tech Fax: +1.6049273615
Tech Fax Ext:
Tech Email: jkwon@coquitlam.ca
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: ns1.he.net
Name Server: ns2.he.net
Name Server: ns3.coquitlam.ca
Name Server: ns4.coquitlam.ca
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-10-20T02:17:02Z
coquitlam.ca server information
coquitlam.ca desktop page speed rank
Last tested: 2019-01-09
coquitlam.ca Desktop Speed Test Quick Summary
priority - 105 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1MiB (68% reduction).
Compressing https://www.coquitlam.ca/images/default-source/new…rs/2018JingleBells.jpg could save 280.8KiB (74% reduction).
Compressing https://www.coquitlam.ca/images/default-source/new…anners/eNewsletter.jpg could save 153.6KiB (75% reduction).
Compressing https://www.coquitlam.ca/images/default-source/new…curbsidecollection.jpg could save 36.9KiB (21% reduction).
Compressing https://www.coquitlam.ca/imgs/home/cta_program-registration.png could save 9.2KiB (31% reduction).
Compressing https://www.coquitlam.ca/images/default-source/cit…s/citizen.png?sfvrsn=2 could save 5.3KiB (31% reduction).
Compressing https://www.coquitlam.ca/images/default-source/pub…ges/urban.jpg?sfvrsn=0 could save 4.4KiB (27% reduction).
Compressing https://www.coquitlam.ca/imgs/home/footer-bg.png could save 3.3KiB (39% reduction).
Compressing https://www.coquitlam.ca/imgs/home/utility_contact-us.jpg could save 2.6KiB (60% reduction).
Compressing https://www.coquitlam.ca/images/default-source/cit…mages/TDS.jpg?sfvrsn=0 could save 2.5KiB (24% reduction).
Compressing https://www.coquitlam.ca/imgs/home/car-next.png could save 1.1KiB (64% reduction).
Compressing https://www.coquitlam.ca/imgs/home/car-prev.png could save 1.1KiB (63% reduction).
Compressing https://www.coquitlam.ca/imgs/skin/nav/nav06_why-coquitlam.png could save 1,009B (23% reduction).
Compressing https://www.coquitlam.ca/imgs/home/bg-caption.png could save 996B (92% reduction).
Compressing https://www.coquitlam.ca/imgs/home/arrow_teal-right.png could save 986B (48% reduction).
Compressing https://www.coquitlam.ca/imgs/home/arrow_skyblue-right.png could save 964B (48% reduction).
Compressing https://www.coquitlam.ca/imgs/skin/bg/bg_sub-nav-repeat.png could save 939B (92% reduction).
Compressing https://www.coquitlam.ca/imgs/home/utility_help.png could save 864B (59% reduction).
Compressing https://www.coquitlam.ca/images/default-source/why…ages/QNet.png?sfvrsn=2 could save 647B (40% reduction).
Compressing https://www.coquitlam.ca/images/default-source/icons/linkedin.png could save 521B (40% reduction).
Compressing https://www.coquitlam.ca/imgs/home/logo.png could save 418B (15% reduction).
Compressing https://www.coquitlam.ca/images/default-source/icons/rss.png?sfvrsn=0 could save 361B (22% reduction).
priority - 31 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 299.4KiB (85% reduction).
Compressing https://www.coquitlam.ca/imgs/skin/nav/bg-mainnav.png could save 139.3KiB (85% reduction).
Compressing https://www.coquitlam.ca/css/home.css could save 7.7KiB (75% reduction).
Compressing https://www.coquitlam.ca/js/jquery.hoverIntent.minified.js could save 842B (57% reduction).
Compressing https://www.coquitlam.ca/css/core.css could save 660B (50% reduction).
Compressing https://www.coquitlam.ca/css/skin.css could save 406B (55% reduction).
Compressing https://www.coquitlam.ca/css/print.css could save 328B (46% reduction).
priority - 22 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 9 blocking script resources and 8 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:
https://www.coquitlam.ca/js/jquery.cycle.min.js
https://www.coquitlam.ca/js/jquery.tools.min.js
https://www.coquitlam.ca/js/jquery.hoverIntent.minified.js
https://www.coquitlam.ca/js/jquery-ui/js/jquery-ui-1.7.2.custom.min.js
https://www.coquitlam.ca/js/cufon-yui.js
https://www.coquitlam.ca/js/TheSans-Plain_500-TheS…Bold-Plain_500.font.js
https://www.coquitlam.ca/js/site-functions.js
https://www.coquitlam.ca/Telerik.Web.UI.WebResourc…2d07f25d934%3a41f6c3a7
Optimize CSS Delivery of the following:
https://www.coquitlam.ca/css/sitefinity.css
https://www.coquitlam.ca/js/jquery-ui/css/ui-light…ry-ui-1.7.2.custom.css
https://www.coquitlam.ca/css/main.css
https://www.coquitlam.ca/css/skin.css
https://www.coquitlam.ca/css/content.css
https://www.coquitlam.ca/css/listing-styles.css
https://www.coquitlam.ca/css/home.css
priority - 2 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.
71.3KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. However, if the HTML response were compressed, then the HTML required to render the above-the-fold content could be delivered in just 2 network round-trips. Enable compression for the HTML response in order to prioritize the visible content for this page.
priority - 1 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:
https://connect.facebook.net/signals/config/208328…9851?v=2.8.37&r=stable (20 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
priority - 1 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 9.5KiB (22% reduction).
Minifying https://www.coquitlam.ca/css/main.css could save 1.7KiB (25% reduction) after compression.
Minifying https://www.coquitlam.ca/js/jquery-ui/css/ui-light…ry-ui-1.7.2.custom.css could save 1.1KiB (23% reduction) after compression.
Minifying https://www.coquitlam.ca/css/home.css could save 1.1KiB (12% reduction).
Minifying https://www.coquitlam.ca/css/content.css could save 1.1KiB (24% reduction) after compression.
Minifying https://www.coquitlam.ca/css/sitefinity.css could save 592B (22% reduction) after compression.
Minifying https://www.coquitlam.ca/css/core.css could save 380B (29% reduction).
Minifying https://www.coquitlam.ca/css/listing-styles.css could save 360B (14% reduction) after compression.
Minifying https://www.coquitlam.ca/css/print.css could save 104B (15% reduction).
priority - 1 Reduce server response time
In our test, your server responded in 0.28 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.
priority - 0 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 1.7KiB (31% reduction).
Minifying https://www.coquitlam.ca/js/jquery.hoverIntent.minified.js could save 332B (23% reduction).
coquitlam.ca Desktop Resources
| Total Resources | 69 |
| Number of Hosts | 5 |
| Static Resources | 63 |
| JavaScript Resources | 12 |
| CSS Resources | 10 |
coquitlam.ca Desktop Resource Breakdown
coquitlam.ca mobile page speed rank
Last tested: 2019-01-09
coquitlam.ca Mobile Speed Test Quick Summary
priority - 105 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1,020.8KiB (68% reduction).
Compressing https://www.coquitlam.ca/images/default-source/new…rs/2018JingleBells.jpg could save 280.8KiB (74% reduction).
Compressing https://www.coquitlam.ca/images/default-source/new…anners/eNewsletter.jpg could save 153.6KiB (75% reduction).
Compressing https://www.coquitlam.ca/images/default-source/new…curbsidecollection.jpg could save 36.9KiB (21% reduction).
Compressing https://www.coquitlam.ca/imgs/home/cta_program-registration.png could save 9.2KiB (31% reduction).
Compressing https://www.coquitlam.ca/images/default-source/cit…s/citizen.png?sfvrsn=2 could save 5.3KiB (31% reduction).
Compressing https://www.coquitlam.ca/images/default-source/pub…ges/urban.jpg?sfvrsn=0 could save 4.4KiB (27% reduction).
Compressing https://www.coquitlam.ca/imgs/home/footer-bg.png could save 3.3KiB (39% reduction).
Compressing https://www.coquitlam.ca/images/default-source/cit…mages/TDS.jpg?sfvrsn=0 could save 2.5KiB (24% reduction).
Compressing https://www.coquitlam.ca/imgs/home/arrow_skyblue-right.png could save 964B (48% reduction).
Compressing https://www.coquitlam.ca/imgs/mobile/bg-footer.jpg could save 752B (16% reduction).
Compressing https://www.coquitlam.ca/images/default-source/why…ages/QNet.png?sfvrsn=2 could save 647B (40% reduction).
Compressing https://www.coquitlam.ca/images/default-source/icons/linkedin.png could save 521B (40% reduction).
Compressing https://www.coquitlam.ca/imgs/home/logo.png could save 418B (15% reduction).
Compressing https://www.coquitlam.ca/images/default-source/icons/rss.png?sfvrsn=0 could save 361B (22% reduction).
Compressing https://www.coquitlam.ca/imgs/mobile/btn-search.png could save 171B (12% reduction).
priority - 16 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 152.5KiB (85% reduction).
Compressing https://www.coquitlam.ca/js/jquery.hoverIntent.minified.js could save 842B (57% reduction).
Compressing https://www.coquitlam.ca/css/core.css could save 660B (50% reduction).
Compressing https://www.coquitlam.ca/css/skin.css could save 406B (55% reduction).
Compressing https://www.coquitlam.ca/css/print.css could save 328B (46% reduction).
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 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.
Optimize CSS Delivery of the following:
priority - 1 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:
https://ssl.google-analytics.com/ga.js (2 hours)
priority - 1 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 8.6KiB (24% reduction).
Minifying https://www.coquitlam.ca/css/main.css could save 1.7KiB (25% reduction) after compression.
Minifying https://www.coquitlam.ca/js/jquery-ui/css/ui-light…ry-ui-1.7.2.custom.css could save 1.1KiB (23% reduction) after compression.
Minifying https://www.coquitlam.ca/css/content.css could save 1.1KiB (24% reduction) after compression.
Minifying https://www.coquitlam.ca/css/sitefinity.css could save 592B (22% reduction) after compression.
Minifying https://www.coquitlam.ca/css/core.css could save 380B (29% reduction).
Minifying https://www.coquitlam.ca/css/listing-styles.css could save 360B (14% reduction) after compression.
Minifying https://www.coquitlam.ca/css/home.css could save 302B (13% reduction) after compression.
Minifying https://www.coquitlam.ca/css/print.css could save 104B (15% reduction).
priority - 1 Reduce server response time
In our test, your server responded in 0.25 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.
priority - 0 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 1.7KiB (31% reduction).
Minifying https://www.coquitlam.ca/js/jquery.hoverIntent.minified.js could save 332B (23% reduction).
coquitlam.ca Mobile Resources
| Total Resources | 59 |
| Number of Hosts | 5 |
| Static Resources | 53 |
| JavaScript Resources | 12 |
| CSS Resources | 10 |
coquitlam.ca Mobile Resource Breakdown
coquitlam.ca mobile page usability
Last tested: 2019-01-09
coquitlam.ca Mobile Usability Test Quick Summary
priority - 0 Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<input id="Search_T095464…_searchTextBox" type="text" name="ctl00$Search$T…$searchTextBox" class="search-bar"> is close to 1 other tap targets.coquitlam.ca similar domains
www.coquitlam.net
www.coquitlam.org
www.coquitlam.info
www.coquitlam.biz
www.coquitlam.us
www.coquitlam.mobi
www.oquitlam.ca
www.coquitlam.ca
www.xoquitlam.ca
www.cxoquitlam.ca
www.xcoquitlam.ca
www.doquitlam.ca
www.cdoquitlam.ca
www.dcoquitlam.ca
www.foquitlam.ca
www.cfoquitlam.ca
www.fcoquitlam.ca
www.voquitlam.ca
www.cvoquitlam.ca
www.vcoquitlam.ca
www.cquitlam.ca
www.ciquitlam.ca
www.coiquitlam.ca
www.cioquitlam.ca
www.ckquitlam.ca
www.cokquitlam.ca
www.ckoquitlam.ca
www.clquitlam.ca
www.colquitlam.ca
www.cloquitlam.ca
www.cpquitlam.ca
www.copquitlam.ca
www.cpoquitlam.ca
www.couitlam.ca
www.coauitlam.ca
www.coqauitlam.ca
www.coaquitlam.ca
www.cowuitlam.ca
www.coqwuitlam.ca
www.cowquitlam.ca
www.coqitlam.ca
www.coqyitlam.ca
www.coquyitlam.ca
www.coqyuitlam.ca
www.coqhitlam.ca
www.coquhitlam.ca
www.coqhuitlam.ca
www.coqjitlam.ca
www.coqujitlam.ca
www.coqjuitlam.ca
www.coqiitlam.ca
www.coquiitlam.ca
www.coqiuitlam.ca
www.coqutlam.ca
www.coquutlam.ca
www.coquiutlam.ca
www.coquuitlam.ca
www.coqujtlam.ca
www.coquijtlam.ca
www.coquktlam.ca
www.coquiktlam.ca
www.coqukitlam.ca
www.coquotlam.ca
www.coquiotlam.ca
www.coquoitlam.ca
www.coquilam.ca
www.coquirlam.ca
www.coquitrlam.ca
www.coquirtlam.ca
www.coquiflam.ca
www.coquitflam.ca
www.coquiftlam.ca
www.coquiglam.ca
www.coquitglam.ca
www.coquigtlam.ca
www.coquiylam.ca
www.coquitylam.ca
www.coquiytlam.ca
www.coquitam.ca
www.coquitpam.ca
www.coquitlpam.ca
www.coquitplam.ca
www.coquitoam.ca
www.coquitloam.ca
www.coquitolam.ca
www.coquitkam.ca
www.coquitlkam.ca
www.coquitklam.ca
www.coquitlm.ca
www.coquitlqm.ca
www.coquitlaqm.ca
www.coquitlqam.ca
www.coquitlwm.ca
www.coquitlawm.ca
www.coquitlwam.ca
www.coquitlsm.ca
www.coquitlasm.ca
www.coquitlsam.ca
www.coquitlzm.ca
www.coquitlazm.ca
www.coquitlzam.ca
www.coquitla.ca
www.coquitlan.ca
www.coquitlamn.ca
www.coquitlanm.ca
www.coquitlaj.ca
www.coquitlamj.ca
www.coquitlajm.ca
www.coquitlak.ca
www.coquitlamk.ca
www.coquitlakm.ca
coquitlam.ca Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
coquitlam.ca TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.