WP.ME WordPress.com: Create a free website or blog


wp.me website information.

wp.me domain name is registered by .ME top-level domain registry. See the other sites registred in .ME domain zone.

No name server records were found.

and probably website wp.me is hosted by YANDEX LLC web hosting company. Check the complete list of other most popular websites hosted by YANDEX LLC hosting company.

According to Alexa traffic rank the highest website wp.me position was 808 (in the world). The lowest Alexa rank position was 992556. Now website wp.me ranked in Alexa database as number 852 (in the world).

Website wp.me Desktop speed measurement score (81/100) is better than the results of 71.91% of other sites and shows that the page is performing great on desktop computers.

wp.me Mobile usability score (93/100) is better than the results of 34.93% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of wp.me (64/100) is better than the results of 64.03% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
May-03-2024 852-6
May-02-2024 8466
May-01-2024 85215
Apr-30-2024 867-7
Apr-29-2024 8600
Apr-28-2024 860-13
Apr-27-2024 8473

Advertisement

wp.me 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.



wp.me 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: WP.ME
Registry Domain ID: D108500000000768577-AGRS
Registrar WHOIS Server:
Registrar URL: http://www.markmonitor.com
Updated Date: 2020-06-22T09:18:20Z
Creation Date: 2009-07-24T13:21:02Z
Registry Expiry Date: 2022-07-24T13:21:02Z
Registrar Registration Expiration Date:
Registrar: MarkMonitor Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895740
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization: Automattic, Inc.
Registrant State/Province: CA
Registrant Country: US
Name Server: NS1.WORDPRESS.COM
Name Server: NS2.WORDPRESS.COM
Name Server: NS3.WORDPRESS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2021-05-06T00:03:16Z

wp.me server information

Servers Location

IP Address
Country
Region
City

wp.me desktop page speed rank

Last tested: 2017-05-21


Desktop Speed Medium
81/100

wp.me Desktop Speed Test Quick Summary


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

Your page has 2 blocking script resources and 3 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://s1.wp.com/home.logged-out/page-domain-only…bundle.js?v=1494322199
https://www.googleadservices.com/pagead/conversion_async.js

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Noto+Serif…t,latin-ext,vietnamese
https://fonts.googleapis.com/css?family=Noto+Sans
https://s1.wp.com/home.logged-out/page-domain-only…tyles.css?v=1494329862

priority - 4 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://d3ir0rz7vxwgq5.cloudfront.net/mwData.min.js (expiration not specified)
https://getrockerbox.com/assets/xyz.js (expiration not specified)
https://snap.licdn.com/li.lms-analytics/insight.min.js (expiration not specified)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/823166884443641?v=2.7.10 (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://secure.leadback.advertising.com/adcedge/lb…sprlb_1472760452[8760] (60 minutes)
https://secure.leadback.advertising.com/adcedge/lb…sprlb_1487351090[8760] (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 3 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 28.9KiB (69% reduction).

Compressing https://d3ir0rz7vxwgq5.cloudfront.net/mwData.min.js could save 28KiB (70% reduction).
Compressing https://dis.us.criteo.com/dis/dis.aspx?p=31321&cb=…&sc_r=1024x768&sc_d=24 could save 831B (53% reduction).

priority - 3 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 26.9KiB (17% reduction).

Compressing https://s1.wp.com/home.logged-out/page-domain-only/img/website-scene.jpg could save 14.8KiB (17% reduction).
Compressing https://s1.wp.com/home.logged-out/page-domain-only/img/blog-scene.jpg could save 12.1KiB (16% reduction).

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.

Only about 12% of the final above-the-fold content could be rendered with the full HTML response.

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 630B (79% reduction).

Minifying https://connect.facebook.net/signals/config/823166884443641?v=2.7.10 could save 630B (79% reduction) after compression.

wp.me Desktop Resources

Total Resources65
Number of Hosts39
Static Resources24
JavaScript Resources15
CSS Resources3

wp.me Desktop Resource Breakdown

wp.me mobile page speed rank

Last tested: 2017-05-21


Mobile Speed Bad
64/100

wp.me Mobile Speed Test Quick Summary


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

Your page has 2 blocking script resources and 3 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://s1.wp.com/home.logged-out/page-domain-only…bundle.js?v=1494322199
https://www.googleadservices.com/pagead/conversion_async.js

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Noto+Serif…t,latin-ext,vietnamese
https://fonts.googleapis.com/css?family=Noto+Sans
https://s1.wp.com/home.logged-out/page-domain-only…tyles.css?v=1494329862

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.

Only about 12% of the final above-the-fold content could be rendered with the full HTML response.

priority - 6 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://d3ir0rz7vxwgq5.cloudfront.net/mwData.min.js (expiration not specified)
https://getrockerbox.com/assets/xyz.js (expiration not specified)
https://snap.licdn.com/li.lms-analytics/insight.min.js (expiration not specified)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/823166884443641?v=2.7.10 (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://secure.leadback.advertising.com/adcedge/lb…sprlb_1472760452[8760] (60 minutes)
https://secure.leadback.advertising.com/adcedge/lb…sprlb_1487351090[8760] (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 3 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 28.8KiB (69% reduction).

Compressing https://d3ir0rz7vxwgq5.cloudfront.net/mwData.min.js could save 28KiB (70% reduction).
Compressing https://dis.us.criteo.com/dis/dis.aspx?p=31321&cb=…32&sc_d=24&site_type=m could save 818B (52% 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 630B (79% reduction).

Minifying https://connect.facebook.net/signals/config/823166884443641?v=2.7.10 could save 630B (79% reduction) after compression.

wp.me Mobile Resources

Total Resources64
Number of Hosts40
Static Resources23
JavaScript Resources17
CSS Resources3

wp.me Mobile Resource Breakdown

wp.me mobile page usability

Last tested: 2017-05-21


Mobile Usability Good
93/100

wp.me Mobile Usability Test Quick Summary


priority - 6 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.

The tap target <a href="https://wordpr….com/features/">Features</a> and 16 others are close to other tap targets.

wp.me similar domains

Similar domains:
www.wp.com
www.wp.net
www.wp.org
www.wp.info
www.wp.biz
www.wp.us
www.wp.mobi
www.p.me
www.wp.me
www.qp.me
www.wqp.me
www.qwp.me
www.ap.me
www.wap.me
www.awp.me
www.sp.me
www.wsp.me
www.swp.me
www.ep.me
www.wep.me
www.ewp.me
www.w.me
www.wo.me
www.wpo.me
www.wop.me
www.wl.me
www.wpl.me
www.wlp.me

wp.me 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.


wp.me 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.