pepco.com website information.
pepco.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.
Following name servers are specified for pepco.com domain:
- ns1-08.azure-dns.com
- ns2-08.azure-dns.net
- ns3-08.azure-dns.org
- ns4-08.azure-dns.info
and probably website pepco.com is hosted by Aruba S.p.A. web hosting company. Check the complete list of other most popular websites hosted by Aruba S.p.A. hosting company.
According to Alexa traffic rank the highest website pepco.com position was 106793 (in the world). The lowest Alexa rank position was 197604. Now website pepco.com ranked in Alexa database as number 197428 (in the world).
Website pepco.com Desktop speed measurement score (80/100) is better than the results of 69.89% of other sites and shows that the page is performing great on desktop computers.
pepco.com Mobile usability score (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of pepco.com (53/100) is better than the results of 39.51% 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 |
|---|---|---|
| Apr-25-2024 | 197,428 | 0 |
| Apr-24-2024 | 197,428 | 0 |
| Apr-23-2024 | 197,428 | 176 |
| Apr-22-2024 | 197,604 | -945 |
| Apr-21-2024 | 196,659 | -1,201 |
| Apr-20-2024 | 195,458 | 0 |
| Apr-19-2024 | 195,458 | 232 |
Advertisement
pepco.com 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.
pepco.com 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: PEPCO.COM
Registry Domain ID: 1956013_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.corporatedomains.com
Registrar URL: http://cscdbs.com
Updated Date: 2020-10-27T05:08:39Z
Creation Date: 1994-11-01T05:00:00Z
Registry Expiry Date: 2021-10-31T04:00:00Z
Registrar: CSC Corporate Domains, Inc.
Registrar IANA ID: 299
Registrar Abuse Contact Email: domainabuse@cscglobal.com
Registrar Abuse Contact Phone: 8887802723
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1-08.AZURE-DNS.COM
Name Server: NS2-08.AZURE-DNS.NET
Name Server: NS3-08.AZURE-DNS.ORG
Name Server: NS4-08.AZURE-DNS.INFO
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-04-27T00:09:39Z
pepco.com server information
pepco.com desktop page speed rank
Last tested: 2016-09-14
pepco.com Desktop Speed Test Quick Summary
priority - 12 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 114.8KiB (74% reduction).
Compressing http://www.pepco.com/library/images/icons/about-us-0.png could save 14.4KiB (91% reduction).
Compressing http://www.pepco.com/library/images/icons/newsroom-0.png could save 14.3KiB (88% reduction).
Compressing http://www.pepco.com/library/images/common/logo-1.png could save 1.5KiB (28% reduction).
Compressing http://www.pepco.com/library/images/icons/education-and-safety-0.png could save 1.5KiB (59% reduction).
Compressing http://www.pepco.com/library/images/icons/education-and-safety-1.png could save 1.4KiB (55% reduction).
Compressing http://www.pepco.com/library/images/icons/connect-with-us-1.png could save 1.3KiB (30% reduction).
Compressing http://www.pepco.com/library/images/icons/outage-center-0.png could save 1.3KiB (37% reduction).
Compressing http://www.pepco.com/library/images/icons/community-commitment-0.png could save 1.3KiB (55% reduction).
Compressing http://www.pepco.com/library/images/icons/community-commitment-1.png could save 1.2KiB (53% reduction).
Compressing http://www.pepco.com/library/images/icons/contact-0.png could save 1.1KiB (51% reduction).
Compressing http://www.pepco.com/library/images/icons/my-home-0.png could save 1.1KiB (65% reduction).
Compressing http://www.pepco.com/library/images/icons/my-home-1.png could save 1.1KiB (64% reduction).
Compressing http://www.pepco.com/library/images/icons/connect-with-us-0.png could save 1KiB (25% reduction).
Compressing http://www.pepco.com/library/images/common/youtube.png could save 1,005B (58% reduction).
Compressing http://www.pepco.com/library/images/icons/manage-my-account-0.png could save 1,001B (54% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/manage-my-account-0.png could save 1,001B (54% reduction).
Compressing http://www.pepco.com/library/images/icons/manage-my-account-1.png could save 997B (53% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/manage-my-account-1.png could save 997B (53% reduction).
Compressing http://www.pepco.com/library/images/common/twitter.png could save 926B (67% reduction).
Compressing http://www.pepco.com/library/images/common/facebook.png could save 911B (68% reduction).
Compressing http://www.pepco.com/library/images/common/prev-new.png could save 863B (64% reduction).
Compressing http://www.pepco.com/library/images/icons/plus-0.png could save 856B (88% reduction).
Compressing http://www.pepco.com/library/images/common/latest-news-2.png could save 855B (69% reduction).
Compressing http://www.pepco.com/library/images/common/pause.png could save 851B (67% reduction).
Compressing http://www.pepco.com/library/images/common/overlay-bg.png could save 847B (89% reduction).
Compressing http://www.pepco.com/library/images/common/next-new.png could save 803B (63% reduction).
Compressing http://www.pepco.com/library/images/icons/leaf.png could save 791B (53% reduction).
Compressing http://www.pepco.com/library/images/icons/edit.png could save 767B (64% reduction).
Compressing http://www.pepco.com/library/images/icons/education-0.png could save 722B (54% reduction).
Compressing http://www.pepco.com/library/images/icons/my-business-0.png could save 603B (28% reduction).
Compressing http://www.pepco.com/library/images/icons/my-business-1.png could save 594B (28% reduction).
Compressing http://www.pepco.com/library/images/icons/search-0.png could save 517B (32% reduction).
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 7 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.pepco.com/WebResource.axd?d=v8qNdULY6PB…1&t=635802997220000000
http://www.pepco.com/ScriptResource.axd?d=Gwwzwu9l…kBcQmigJ4g1&t=5f9d5645
http://www.pepco.com/ScriptResource.axd?d=WHXvwQ_b…hlWbs5XGNK0&t=5f9d5645
http://www.pepco.com/library/javascript/modernizr.min.js
http://www.pepco.com/library/javascript/supersized.3.2.7.min.js
http://www.pepco.com/library/javascript/supersized.shutter.min.js
Optimize CSS Delivery of the following:
http://www.pepco.com/library/styles/supersized.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.
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.
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:
http://www.google-analytics.com/analytics.js (2 hours)
priority - 0 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 1.3KiB (57% reduction).
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 524B (12% reduction).
pepco.com Desktop Resources
| Total Resources | 59 |
| Number of Hosts | 6 |
| Static Resources | 4 |
| JavaScript Resources | 10 |
| CSS Resources | 2 |
pepco.com Desktop Resource Breakdown
pepco.com mobile page speed rank
Last tested: 2017-12-17
pepco.com Mobile Speed Test Quick Summary
priority - 53 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 519KiB (50% reduction).
Compressing http://www.pepco.com/uploadedImages/www.pepco.com/…TheSource-Homepage.jpg could save 58.5KiB (40% reduction).
Compressing http://www.pepco.com/library/images/common/logo-0.png could save 55KiB (89% reduction).
Compressing http://www.pepco.com/uploadedImages/www.pepco.com/…r/Pepco_Storm_2016.jpg could save 48.2KiB (25% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/…y%20Account.jpg?n=7295 could save 37KiB (85% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/…vingsRelease.jpg?n=769 could save 16.1KiB (71% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/_DSC0208a(1).jpg?n=2504 could save 11.7KiB (63% reduction).
Compressing http://www.pepco.com/library/images/icons/connect-with-us-1.png could save 1.4KiB (32% reduction).
Compressing http://www.pepco.com/library/images/icons/outage-center-0.png could save 1.2KiB (36% reduction).
Compressing http://www.pepco.com/library/images/icons/education-and-safety-1.png could save 1.1KiB (45% reduction).
Compressing http://www.pepco.com/library/images/common/logo-1.png could save 1KiB (19% reduction).
Compressing http://www.pepco.com/library/images/common/youtube.png could save 1,019B (59% reduction).
Compressing http://www.pepco.com/library/images/icons/education-and-safety-0.png could save 1,017B (40% reduction).
Compressing http://www.pepco.com/library/images/icons/manage-my-account-1.png could save 982B (53% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/manage-my-account-1.png could save 982B (53% reduction).
Compressing http://www.pepco.com/library/images/icons/my-home-1.png could save 980B (53% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/linkedin.png could save 966B (71% reduction).
Compressing http://www.pepco.com/library/images/icons/community-commitment-1.png could save 961B (41% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/facebook.png could save 953B (74% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/twitter.png could save 946B (68% reduction).
Compressing http://www.pepco.com/library/images/common/play.png could save 924B (70% reduction).
Compressing http://www.pepco.com/library/images/common/pause.png could save 922B (73% reduction).
Compressing http://www.pepco.com/library/images/icons/connect-with-us-0.png could save 921B (23% reduction).
Compressing http://www.pepco.com/library/images/icons/manage-my-account-0.png could save 921B (50% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/manage-my-account-0.png could save 921B (50% reduction).
Compressing http://www.pepco.com/library/images/common/next-home.png could save 910B (73% reduction).
Compressing http://www.pepco.com/library/images/common/prev-home.png could save 898B (72% reduction).
Compressing http://www.pepco.com/uploadedImages/SharedContent/instagram.png could save 896B (69% reduction).
Compressing http://www.pepco.com/library/images/icons/search-0.png could save 877B (52% reduction).
Compressing http://www.pepco.com/library/images/common/news-0.png could save 874B (84% reduction).
Compressing http://www.pepco.com/library/images/icons/plus-0.png could save 866B (89% reduction).
Compressing http://www.pepco.com/library/images/icons/my-home-0.png could save 859B (48% reduction).
Compressing http://www.pepco.com/library/images/common/overlay-bg.png could save 858B (90% reduction).
Compressing http://www.pepco.com/library/images/icons/my-business-1.png could save 848B (40% reduction).
Compressing http://www.pepco.com/library/images/icons/my-business-0.png could save 798B (37% reduction).
Compressing http://www.pepco.com/library/images/icons/community-commitment-0.png could save 790B (34% reduction).
priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 8 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.pepco.com/library/javascript/jquery-touch.js
http://www.pepco.com/WebResource.axd?d=v8qNdULY6PB…1&t=635802997220000000
http://www.pepco.com/ScriptResource.axd?d=Gwwzwu9l…kBcQmigJ4g1&t=5f9d5645
http://www.pepco.com/ScriptResource.axd?d=WHXvwQ_b…hlWbs5XGNK0&t=5f9d5645
http://www.pepco.com/library/javascript/modernizr.min.js
http://www.pepco.com/library/javascript/supersized.3.2.7.min.js
http://www.pepco.com/library/javascript/supersized.shutter.min.js
Optimize CSS Delivery of the following:
http://www.pepco.com/library/styles/supersized.css
priority - 8 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.
priority - 5 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://www.googletagmanager.com/gtm.js?id=GTM-K5PZ4L (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/441343…57274?v=2.8.6&r=stable (20 minutes)
https://connect.facebook.net/signals/plugins/iwl.js?v=2.8.6 (20 minutes)
http://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
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.8KiB (28% reduction).
Minifying http://www.pepco.com/library/javascript/jquery-touch.js could save 628B (45% reduction) after compression.
Minifying http://www.pepco.com/WebResource.axd?d=v8qNdULY6PB…1&t=635802997220000000 could save 524B (12% reduction) after compression.
pepco.com Mobile Resources
| Total Resources | 70 |
| Number of Hosts | 14 |
| Static Resources | 9 |
| JavaScript Resources | 19 |
| CSS Resources | 2 |
pepco.com Mobile Resource Breakdown
pepco.com mobile page usability
Last tested: 2017-12-17
pepco.com similar domains
www.pepco.net
www.pepco.org
www.pepco.info
www.pepco.biz
www.pepco.us
www.pepco.mobi
www.epco.com
www.pepco.com
www.oepco.com
www.poepco.com
www.opepco.com
www.lepco.com
www.plepco.com
www.lpepco.com
www.ppco.com
www.pwpco.com
www.pewpco.com
www.pwepco.com
www.pspco.com
www.pespco.com
www.psepco.com
www.pdpco.com
www.pedpco.com
www.pdepco.com
www.prpco.com
www.perpco.com
www.prepco.com
www.peco.com
www.peoco.com
www.pepoco.com
www.peopco.com
www.pelco.com
www.peplco.com
www.pelpco.com
www.pepo.com
www.pepxo.com
www.pepcxo.com
www.pepxco.com
www.pepdo.com
www.pepcdo.com
www.pepdco.com
www.pepfo.com
www.pepcfo.com
www.pepfco.com
www.pepvo.com
www.pepcvo.com
www.pepvco.com
www.pepc.com
www.pepci.com
www.pepcoi.com
www.pepcio.com
www.pepck.com
www.pepcok.com
www.pepcko.com
www.pepcl.com
www.pepcol.com
www.pepclo.com
www.pepcp.com
www.pepcop.com
www.pepcpo.com
www.pepco.con
pepco.com 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.
pepco.com 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.