W.org - Api.w.org
Domain Summary
What is the traffic rank for Api.w.org?
• Api.w.org ranks 14,316 globally on Alexa.
What percent of global Internet users visit Api.w.org?
• 0.00508% of global Internet users visit Api.w.org
How many people visit Api.w.org each day?
• Api.w.org receives approximately 250.4K visitors and 550,969 page impressions per day.
Which countries does Api.w.org receive most of its visitors from?
• Api.w.org is mostly visited by people located in India,United States,Brazil.
How much Api.w.org can earn?
• Api.w.org should earn about $976.50/day from advertising revenue.
What is Api.w.org estimated value?
• Estimated value of Api.w.org is $880,957.93.
What IP addresses does Api.w.org resolve to?
• Api.w.org resolves to the IP addresses 198.143.164.252.
Where are Api.w.org servers located in?
• Api.w.org has servers located in Atlanta, GA, 30303, United States.
About - api.w.org
The WordPress REST API provides an interface for applications to interact with your WordPress site by sending and receiving data as JSON…
Edit Site Info
What technologies does api.w.org use?
api.w.org Profile
Title: REST API Handbook | WordPress Developer Resources
Last update was 742 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not linking to, promoting or affiliated with w.org in any way. Only publicly available statistics data are displayed.
api.w.org Traffic Summary
250.4K daily visitors
Is this your site?
Verify your site's metrics.
Verify your site's metrics.
- Daily Unique Visitors:
- 250,440
- Monthly Visits:
- 7,738,596
- Pages per Visitor:
- 2.20
- Daily Pageviews:
- 550,969
- Alexa Rank:
- 14,316
- Alexa Reach:
- 0.00508% (of global internet users)
- Avg. visit duration:
- 02:29
- Bounce rate:
- 65.07%
Traffic sources
- Direct:
- 7.42%
- Referral:
- 91.06%
- Search:
- 0.82%
- Social:
- 0.17%
- Paid:
- 0.02%
Visitors by country
- Users%Pageviews%Rank
- India 24.1%24.5%4835
- United States 10.2%11.3%23097
- Brazil 8.4%8.8%6992
- Turkey 4.1%3.5%5953
- Iran 3.8%3.5%8163
- Mexico 3.2%3.6%8001
- Pakistan 2.4%2.1%7703
- Bangladesh 2.2%2.5%2727
- Nigeria 2.1%1.3%7687
- Egypt 2.0%2.5%7977
- Indonesia 1.8%1.7%8007
- Argentina 1.6%5.4%5770
- Saudi Arabia 1.5%1.1%9701
- Australia 1.3%1.2%15558
- Canada 1.3%1.0%22925
- Greece 1.3%1.1%9326
- Viet Nam 1.1%0.8%12325
- Thailand 1.0%1.0%7615
- Singapore 0.8%0.7%10889
- United Arab Emirates 0.8%1.0%7478
- Morocco 0.7%0.9%5437
- Algeria 0.6%0.4%13029
- Russian Federation 0.6%0.4%60215
- Tunisia 0.6%0.4%6145
Where do visitors go on api.w.org?
- Reach%Pageviews%PerUser
- ps.w.org
- 95.57%96.37%2.1
- ts.w.org
- 3.52%3.15%2
- s.w.org
- 0.96%0.46%1.0
- OTHER
- 0%0.02%0
Competitive Data
- Domain:
- api.w.org
- Rank:
(Rank based on keywords, cost and organic traffic) - 4,678,283
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 14
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 16
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $0.00
Backlinks Report
- Total Sites Linking In (Alexa):
- 217
- Total Backlinks:
- 54,468
- Follow Links:
- 52,638
- Nofollow Links:
- 1,830
- Referring Domains:
- 334
- Referring IPs:
- 357
- Authority Domain Score:
- 35
+ Moz Data
- Domain Authority:
- 40
- Page Authority:
- 37
- MozRank:
- n/a
+ How much would api.w.org make?
- Daily Revenue:
- $976.50
- Monthly Revenue:
- $29,295.00
- Yearly Revenue:
- $356,422.50
Daily earning by country
- PageviewsEarning
- United States 62,259$300.71
- Brazil 48,485$64.49
- India 134,987$51.30
- Canada 5,510$33.28
- Australia 6,612$31.87
- Argentina 29,752$7.44
- Singapore 3,857$7.25
- Nigeria 7,163$7.09
- Mexico 19,835$5.55
- United Arab Emirates 5,510$5.23
- Iran 19,284$3.66
- Turkey 19,284$3.66
- Saudi Arabia 6,061$3.45
- Morocco 4,959$2.98
- Bangladesh 13,774$2.34
- Greece 6,061$2.12
- Viet Nam 4,408$2.07
- Egypt 13,774$1.93
- Pakistan 11,570$1.74
- Thailand 5,510$1.16
- Algeria 2,204$1.08
- Indonesia 9,366$1.03
- Russian Federation 2,204$0.90
- Tunisia 2,204$0.31
How much money does api.w.org lose due to Adblock?
- Daily Revenue Loss:
- $95.59
- Monthly Revenue Loss:
- $2,867.69
- Yearly Revenue Loss:
- $34,890.26
- Daily Pageviews Blocked:
- 81,659
- Monthly Pageviews Blocked:
- 2,449,773
- Yearly Pageviews Blocked:
- 29,805,577
Daily revenue loss by country
- BlockedLost Money
- United States 11,207$54.13
- India 37,796$14.36
- Canada 1,377$8.32
- Australia 1,322$6.37
- Brazil 2,909$3.87
- Singapore 1,118$2.10
- Argentina 4,165$1.04
- Greece 2,364$0.83
- United Arab Emirates 771$0.73
- Saudi Arabia 1,273$0.73
- Indonesia 5,433$0.60
- Iran 3,085$0.59
- Pakistan 3,703$0.56
- Mexico 1,785$0.50
- Turkey 1,350$0.26
- Nigeria 143$0.14
- Egypt 689$0.10
- Viet Nam 176$0.08
- Thailand 331$0.07
- Morocco 99$0.06
- Russian Federation 132$0.05
- Algeria 110$0.05
- Bangladesh 275$0.05
- Tunisia 44$0.01
How much is api.w.org worth?
- Website Value:
- $880,957.93
+ Ad Experience Report
Summary of the ad experience rating of a site for a specific platform.
Mobile summary
- Root domain:
- w.org
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
Desktop summary
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
+ Abusive Experience Report
- Root domain:
- w.org
- Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.) - Off
- Status:
(The status of the site reviewed for the abusive experiences.) - Not reviewed
+ Where is api.w.org hosted?
- Server IP:
- 198.143.164.252
- ASN:
- AS32475
- ISP:
- SingleHop, Inc.
- Server Location:
- Atlanta
GA
30303
United States, US
Other sites hosted on 198.143.164.252
+ How fast does api.w.org load?
- Average Load Time:
- (307 ms) 99 % of sites are slower
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a AVERAGE 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.
First Contentful Paint (FCP)2.1s
First Input Delay (FID)3ms
Origin Data
All pages served from this origin have an AVERAGE 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.
First Contentful Paint (FCP)2.2s
First Input Delay (FID)3ms
Lab Data
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
First Contentful Paint 1.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
Timing budget
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.
Largest Contentful Paint 2.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint/)
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint/)
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Time to Interactive 1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Meaningful Paint 1.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
First Meaningful Paint measures when the primary content of a page is visible. 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.
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.
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a AVERAGE 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.
First Contentful Paint (FCP)2.7s
First Input Delay (FID)16ms
Origin Data
All pages served from this origin have an AVERAGE 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.
First Contentful Paint (FCP)2.8s
First Input Delay (FID)21ms
Lab Data
First Contentful Paint 5.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Largest Contentful Paint 6.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint/)
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint/)
First Contentful Paint (3G) 10862 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
First CPU Idle 6.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Time to Interactive 8.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Timing budget
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.
Speed Index 5.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First Meaningful Paint 5.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
First Meaningful Paint measures when the primary content of a page is visible. 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.
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 100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
+ Does api.w.org use compression?
api.w.org does not use compression.
Original size: n/a
Compressed size: n/a
File reduced by: n/a
Compressed size: n/a
File reduced by: n/a
+ Google Safe Browsing
+ SSL Checker - SSL Certificate Verify
api.w.org supports HTTPS
Verifying SSL Support. Please wait...
+ Verify HTTP/2 Support
api.w.org supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...
+ Http Header
Server: nginx
Date: Wed, 29 Jul 2020 01:38:45 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://api.wordpress.org/
HTTP/2 302
server: nginx
date: Wed, 29 Jul 2020 01:38:45 GMT
content-type: text/html; charset=utf-8
location: https://developer.wordpress.org/rest-api/
x-frame-options: SAMEORIGIN
HTTP/2 200
server: nginx
date: Wed, 29 Jul 2020 01:38:45 GMT
content-type: text/html; charset=utf-8
vary: Accept-Encoding
link: <https://developer.wordpress.org/wp-json/>; rel="https://api.w.org/"
link: <https://developer.wordpress.org/wp-json/wp/v2/rest-api-handbook/22832>; rel="alternate"; type="application/json"
link: <https://developer.wordpress.org/?p=22832>; rel=shortlink
x-olaf: ⛄
x-frame-options: SAMEORIGIN
x-nc: HIT ord 2
content-encoding: br
+ DNS Lookup
| Type | Ip | Target | TTL |
| CNAME | wordpress.org | 300 |
