Wikivoyage.org
Domain Summary
What is the traffic rank for Wikivoyage.org?
• Wikivoyage.org ranks 223,329 globally on HypeStat.
What percent of global Internet users visit Wikivoyage.org?
• 0.0023% of global Internet users visit Wikivoyage.org
How many people visit Wikivoyage.org each day?
• Wikivoyage.org receives approximately 46.2K visitors and 81,687 page impressions per day.
Which countries does Wikivoyage.org receive most of its visitors from?
• Wikivoyage.org is mostly visited by people located in United States,India,Russian Federation.
How much Wikivoyage.org can earn?
• Wikivoyage.org should earn about $292.16/day from advertising revenue.
What is Wikivoyage.org estimated value?
• Estimated value of Wikivoyage.org is $330,144.29.
What IP addresses does Wikivoyage.org resolve to?
• Wikivoyage.org resolves to the IP addresses 208.80.154.224.
Where are Wikivoyage.org servers located in?
• Wikivoyage.org has servers located in San Francisco, California, 94105, United States.
wikivoyage.org Profile
Title:Wikivoyage
Description:Ein freier, nicht kommerzieller Open-Source Reiseführer, zu dem jeder beitragen kann (Wiki-Prinzip).
Keywords:wikivoyage, the free, worldwide travel guide that anyone can edit.
About wikivoyage.org
Ein freier, nicht kommerzieller Open-Source Reiseführer, zu dem jeder beitragen kann (Wiki-Prinzip).
Wikivoyage, the free, worldwide travel guide that anyone can edit. Edit Site Info
Wikivoyage, the free, worldwide travel guide that anyone can edit. Edit Site Info
What technologies does wikivoyage.org use?
Last update was 86 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 wikivoyage.org in any way. Only publicly available statistics data are displayed.
wikivoyage.org Traffic Summary
Daily Visitors46.2K
3.96%
Monthly Visits1.4M
5.82%
Pages per Visit1.77
11.57%
Visit duration07:31
22.64%
Bounce Rate72.46%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 46,155
- Monthly Visits:
- 1,398,497
- Pages per Visit:
- 1.77
- Daily Pageviews:
- 81,687
- Avg. visit duration:
- 07:31
- Bounce rate:
- 72.46%
- Global Reach:
- 0.0023%
- HypeRank:
- 223,329
- SEMrush Rank:
- 883
- Monthly Visits (SEMrush):
- 4,532,157
- Monthly Unique Visitors (SEMrush):
- 3,237,816
- Monthly Visits (SimilarWeb):
- 1,370,954
Traffic sources
- Direct:
- 38.41%
- Referral:
- 5.36%
- Search:
- 56.15%
- Social:
- 0.07%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 34.35%
- Mobile:
- 65.65%
Visitors by country
- Users%Pageviews%Rank
- United States 30.3%46.4%21578
- India 8.0%10.2%49016
- Russian Federation 5.0%2.2%29217
- Iran 3.2%2.1%25832
- Malaysia 3.2%2.1%8523
Where do visitors go on wikivoyage.org?
- Reach%Pageviews%PerUser
- en.wikivoyage.org
- 60.11%73.01%3.0
- wikivoyage.org
- 11.41%4.60%1
- ru.wikivoyage.org
- 5.55%2.37%1
- es.wikivoyage.org
- 4.00%2.02%1
- bn.wikivoyage.org
- 2.03%0.99%1
- Domain:
- wikivoyage.org
- Rank:
(Rank based on keywords, cost and organic traffic) - 883
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 705,208
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 4,285,578
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $3,663,534.00
Backlinks Report ▼
- Total Backlinks:
- 67,077
- Follow Links:
- 51,603
- Nofollow Links:
- 15,473
- Referring Domains:
- 1,095
- Referring IPs:
- 1,014
- Authority Domain Score:
- 75
Backlinks by country
- Country
- Domains
- United States 604
- Singapore 142
- Germany 101
- France 46
- Netherlands 17
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 466
- .org
- 86
- .pw
- 80
- .edu
- 1
- .gov
- 0
Search Engine Indexes ▼
- Google Index:
- 955,000
- Bing Index:
- 16
Moz Data ▼
- Domain Authority:
- 70
- Page Authority:
- 57
- MozRank:
- 6
How much would wikivoyage.org make? ▼
- Daily Revenue:
- $292.16
- Monthly Revenue:
- $8,764.80
- Yearly Revenue:
- $106,638.40
Daily earning by country
- PageviewsEarning
- United States 37,903$183.07
- India 8,332$3.17
- Russian Federation 1,797$0.74
- Viet Nam 1,470$0.69
- Malaysia 1,715$0.50
- Iran 1,715$0.33
- Ukraine 490$0.23
- Pakistan 1,389$0.21
- Bangladesh 899$0.15
- Egypt 735$0.10
How much money does wikivoyage.org lose due to Adblock?
- Daily Revenue Loss:
- $34.11
- Monthly Revenue Loss:
- $1,023.21
- Yearly Revenue Loss:
- $12,449.12
- Daily Pageviews Blocked:
- 10,297
- Monthly Pageviews Blocked:
- 308,899
- Yearly Pageviews Blocked:
- 3,758,276
Daily revenue loss by country
- BlockedLost Money
- United States 6,822$32.95
- India 2,333$0.89
- Pakistan 444$0.07
- Iran 274$0.05
- Russian Federation 108$0.04
- Malaysia 137$0.04
- Ukraine 64$0.03
- Viet Nam 59$0.03
- Egypt 37$0.01
- Bangladesh 18$0.00
How much is wikivoyage.org worth?
- Website Value:
- $330,144.29
Ad Experience Report ▼
Summary of the ad experience rating of a site for a specific platform.
Mobile summary
- Root domain:
- wikivoyage.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
- Root domain:
- wikivoyage.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
Abusive Experience Report ▼
- Root domain:
- wikivoyage.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 wikivoyage.org hosted? ▼
- Server IP:
- 208.80.154.224
- ASN:
- AS14907
- ISP:
- Wikimedia Foundation, Inc.
- Server Location:
- San Francisco
California, CA
94105
United States, US
Other sites hosted on 208.80.154.224
How fast does wikivoyage.org load? ▼
- Average Load Time:
- 1044 ms
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a FAST 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)976ms
First Input Delay (FID)2ms
Origin Data
All pages served from this origin have an FAST 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)976ms
First Input Delay (FID)2ms
Lab Data
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
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
Speed Index 0.5 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
Largest Contentful Paint 0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
First Contentful Paint 0.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
First Meaningful Paint 0.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
Max Potential First Input Delay 50 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
Has a `` tag with `width` or `initial-scale`
A `` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more
A `` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input 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
Time to Interactive 0.6 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
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. 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
Avoids `unload` event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. 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
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more
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
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a FAST 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)1.3s
First Input Delay (FID)12ms
Origin Data
All pages served from this origin have an FAST 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)1.3s
First Input Delay (FID)12ms
Lab Data
Largest Contentful Paint 2.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
First Meaningful Paint 1.7 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
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
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
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
Has a `` tag with `width` or `initial-scale`
A `` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more
A `` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more
First Contentful Paint 1.7 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
Time to Interactive 1.7 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 Contentful Paint (3G) 3238 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
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
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more
Speed Index 1.7 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
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
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
Does wikivoyage.org use compression? ▼
wikivoyage.org use gzip compression.
Original size: 47.11 KB
Compressed size: 10.34 KB
File reduced by: 36.77 KB (78%)
Compressed size: 10.34 KB
File reduced by: 36.77 KB (78%)
Google Safe Browsing ▼
SSL Checker - SSL Certificate Verify ▼
wikivoyage.org supports HTTPS
Verifying SSL Support. Please wait...
Common Name: *.wikipedia.org
Organization:
Location:
Issuer: R3
Valid from: Dec 25 08:08:43 2022 GMT
Valid until: Mar 25 08:08:42 2023 GMT
Authority: CA:FALSE
Keysize:
Organization:
Location:
Issuer: R3
Valid from: Dec 25 08:08:43 2022 GMT
Valid until: Mar 25 08:08:42 2023 GMT
Authority: CA:FALSE
Keysize:
Common Name: R3
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Sep 4 00:00:00 2020 GMT
Valid until: Sep 15 16:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Sep 4 00:00:00 2020 GMT
Valid until: Sep 15 16:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: ISRG Root X1
Organization: Internet Security Research Group
Location: US
Issuer: DST Root CA X3
Valid from: Jan 20 19:14:03 2021 GMT
Valid until: Sep 30 18:14:03 2024 GMT
Authority: CA:TRUE
Keysize: 4096 Bits
Organization: Internet Security Research Group
Location: US
Issuer: DST Root CA X3
Valid from: Jan 20 19:14:03 2021 GMT
Valid until: Sep 30 18:14:03 2024 GMT
Authority: CA:TRUE
Keysize: 4096 Bits
Verify HTTP/2 Support ▼
wikivoyage.org supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...
Site Categories (dmoz) ▼
- Travel/Guides and Directories
- Reiseinformationen/Reiseführer
Http Header ▼
date: Sun, 01 Jan 2023 08:12:29 GMT
server: mw1414.eqiad.wmnet
location: https://www.wikivoyage.org/
cache-control: max-age=2592000
expires: Tue, 31 Jan 2023 08:12:29 GMT
content-length: 235
content-type: text/html; charset=iso-8859-1
vary: X-Forwarded-Proto
age: 86487
x-cache: cp1079 hit, cp1083 hit/148
x-cache-status: hit-front
server-timing: cache;desc="hit-front", host;desc="cp1083"
strict-transport-security: max-age=106384710; includeSubDomains; preload
report-to: { "group": "wm_nel", "max_age": 86400, "endpoints": [{ "url": "https://intake-logging.wikimedia.org/v1/events?stream=w3c.reportingapi.network_error&schema_uri=/w3c/reportingapi/network_error/1.0.0" }] }
nel: { "report_to": "wm_nel", "max_age": 86400, "failure_fraction": 0.05, "success_fraction": 0.0}
set-cookie: WMF-Last-Access=02-Jan-2023;Path=/;HttpOnly;secure;Expires=Fri, 03 Feb 2023 00:00:00 GMT
set-cookie: WMF-Last-Access-Global=02-Jan-2023;Path=/;Domain=.wikivoyage.org;HttpOnly;secure;Expires=Fri, 03 Feb 2023 00:00:00 GMT
accept-ch: Sec-CH-UA-Arch,Sec-CH-UA-Bitness,Sec-CH-UA-Full-Version-List,Sec-CH-UA-Model,Sec-CH-UA-Platform-Version
permissions-policy: interest-cohort=(),ch-ua-arch=(self "intake-analytics.wikimedia.org"),ch-ua-bitness=(self "intake-analytics.wikimedia.org"),ch-ua-full-version-list=(self "intake-analytics.wikimedia.org"),ch-ua-model=(self "intake-analytics.wikimedia.org"),ch-ua-platform-version=(self "intake-analytics.wikimedia.org")
x-client-ip: 67.212.187.106
set-cookie: GeoIP=US:::37.75:-97.82:v4; Path=/; secure; Domain=.wikivoyage.org
HTTP/2 200
date: Mon, 02 Jan 2023 06:40:01 GMT
cache-control: s-maxage=86400, must-revalidate, max-age=3600
server: ATS/9.1.3
etag: W/"bc74-5ef9f179b3a70"
last-modified: Mon, 12 Dec 2022 10:37:38 GMT
content-type: text/html
content-encoding: gzip
vary: Accept-Encoding
age: 5634
x-cache: cp1079 hit, cp1083 hit/15
x-cache-status: hit-front
server-timing: cache;desc="hit-front", host;desc="cp1083"
strict-transport-security: max-age=106384710; includeSubDomains; preload
report-to: { "group": "wm_nel", "max_age": 86400, "endpoints": [{ "url": "https://intake-logging.wikimedia.org/v1/events?stream=w3c.reportingapi.network_error&schema_uri=/w3c/reportingapi/network_error/1.0.0" }] }
nel: { "report_to": "wm_nel", "max_age": 86400, "failure_fraction": 0.05, "success_fraction": 0.0}
set-cookie: WMF-Last-Access=02-Jan-2023;Path=/;HttpOnly;secure;Expires=Fri, 03 Feb 2023 00:00:00 GMT
set-cookie: WMF-Last-Access-Global=02-Jan-2023;Path=/;Domain=.wikivoyage.org;HttpOnly;secure;Expires=Fri, 03 Feb 2023 00:00:00 GMT
accept-ch: Sec-CH-UA-Arch,Sec-CH-UA-Bitness,Sec-CH-UA-Full-Version-List,Sec-CH-UA-Model,Sec-CH-UA-Platform-Version
permissions-policy: interest-cohort=(),ch-ua-arch=(self "intake-analytics.wikimedia.org"),ch-ua-bitness=(self "intake-analytics.wikimedia.org"),ch-ua-full-version-list=(self "intake-analytics.wikimedia.org"),ch-ua-model=(self "intake-analytics.wikimedia.org"),ch-ua-platform-version=(self "intake-analytics.wikimedia.org")
x-client-ip: 67.212.187.106
set-cookie: GeoIP=US:::37.75:-97.82:v4; Path=/; secure; Domain=.wikivoyage.org
accept-ranges: bytes
content-length: 10588
DNS Lookup ▼
Type | Ip | Target/Txt | TTL |
HINFO | 3600 | ||
A | 208.80.154.224 | 545 | |
NS | 3545 | ||
NS | 3545 | ||
NS | 3545 |
Whois Lookup ▼
- Domain Created:
- 2006-11-17
- Domain Expires:
- 2023-11-17
- Domain Updated:
- 2022-10-21
- Domain Age:
- 16 years 4 months 12 days
- Domain Registrar:
- MarkMonitor Inc.
- Domain Owner:
- Wikimedia Foundation, Inc.
- WhoIs: