Swi-prolog.discourse.group
SWI-Prolog - Users and developers of SWI-Prolog, an implementation of the Prolog programming language
Domain Summary
What percent of global Internet users visit Swi-prolog.discourse.group?
• 7.2E-6% of global Internet users visit Swi-prolog.discourse.group
How many people visit Swi-prolog.discourse.group each day?
• Swi-prolog.discourse.group receives approximately 356 visitors and 792 page impressions per day.
Which countries does Swi-prolog.discourse.group receive most of its visitors from?
• Swi-prolog.discourse.group is mostly visited by people located in Poland,Canada,Romania.
How much Swi-prolog.discourse.group can earn?
• Swi-prolog.discourse.group should earn about $2.59/day from advertising revenue.
What is Swi-prolog.discourse.group estimated value?
• Estimated value of Swi-prolog.discourse.group is $2,373.13.
What IP addresses does Swi-prolog.discourse.group resolve to?
• Swi-prolog.discourse.group resolves to the IP addresses 216.66.8.75.
Where are Swi-prolog.discourse.group servers located in?
• Swi-prolog.discourse.group has servers located in Toronto, Ontario, M5A, Canada.
swi-prolog.discourse.group Profile
Title:SWI-Prolog - Users and developers of SWI-Prolog, an implementation of the Prolog programming language
Description:SWI-Prolog forum
What technologies does swi-prolog.discourse.group use?
These are the technologies used at swi-prolog.discourse.group. swi-prolog.discourse.group has a total of 6 technologies installed in 7 different categories.swi-prolog.discourse.group Traffic Analysis
This website is viewed by an estimated 356 visitors daily, generating a total of 792 pageviews. This equates to about 10.8K monthly visitors. Swi-prolog.discourse.group traffic has decreased by 38.96% compared to last month.Daily Visitors356
38.47%
Monthly Visits10.8K
38.96%
Pages per Visit2.22
46.31%
Visit duration00:26
22.95%
Bounce Rate70.62%
8.04%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 356
- Monthly Visits:
- 10,787
- Pages per Visit:
- 2.22
- Daily Pageviews:
- 792
- Avg. visit duration:
- 00:26
- Bounce rate:
- 70.62%
- Global Reach:
- 7.2E-6%
- Monthly Visits (SEMrush):
- 1,172
- Monthly Unique Visitors (SEMrush):
- 1,070
- Monthly Visits (SimilarWeb):
- 10,582
- HypeRank:
- n/a
- SEMrush Rank:
- 4,850,572
Traffic sources
- Direct:
- 0%
- Referral:
- 18.60%
- Search:
- 81.40%
- Social:
- 0%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 100.00%
- Mobile:
- 0%
Total Visits Last 3 Months
26.3K
SEP
17.7K
OCT
10.8K
NOV
Visitors by country
- Country
- Users%
- Poland 14.85%
- Canada 12.03%
- Romania 11.22%
- United Kingdom 9.32%
- United States 8.34%
Backlinks Report ▼
Swi-prolog.discourse.group has a total of 1,459 backlinks from 250 referring domains and most of them comes from United States.- Total Backlinks:
- 1,459
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 250
- Referring IPs:
- 280
- Authority Domain Score:
- 18
Backlinks by country
- Country
- Domains
- United States 99
- Germany 26
- France 12
- India 9
- Korea, Republic of 8
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 119
- .app
- 26
- .dev
- 18
- .edu
- 0
- .gov
- 0
Last update was 7 hours ago
This can take up to 60 seconds. Please wait...
Update will be available in 17 hours
This can take up to 60 seconds. Please wait...
Update will be available in 17 hours
*HypeStat.com is not promoting or affiliated with swi-prolog.discourse.group in any way. Only publicly available statistics data are displayed.
▼
SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.- Domain:
- swi-prolog.discourse.group
- Rank:
(Rank based on keywords, cost and organic traffic) - 4,850,572
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 337
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 49
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $0.00
Revenue report ▼
Google.com would generate approximately $2.6 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $77.7 and annual gross revenue of approximately $0.9K. Based on these figures, the site's net worth is estimated at around $2.4K.How much would swi-prolog.discourse.group make?
- Daily Revenue:
- $2.59
- Monthly Revenue:
- $77.70
- Yearly Revenue:
- $945.35
Daily earning by country
- CountryPageviewsEarning
- Canada 95$0.58
- United States 66$0.32
- United Kingdom 74$0.20
- Poland 118$0.05
- Romania 89$0.02
Loss of money due to Adblock?
- Daily Revenue Loss:
- $0.25
- Monthly Revenue Loss:
- $7.61
- Yearly Revenue Loss:
- $92.55
- Daily Pageviews Blocked:
- 105
- Monthly Pageviews Blocked:
- 3,150
- Yearly Pageviews Blocked:
- 38,327
Daily revenue loss by country
- CountryBlockedLost Money
- Canada 24$0.14
- United States 12$0.06
- United Kingdom 12$0.03
- Poland 39$0.02
- Romania 19$0.01
How much is swi-prolog.discourse.group worth?
- Website Value:
- $2.4K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- swi-prolog.discourse.group
- 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:
- swi-prolog.discourse.group
- 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 ▼
Summary of the abusive experience rating of a website.- Root domain:
- swi-prolog.discourse.group
- 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 swi-prolog.discourse.group hosted? ▼
Swi-prolog.discourse.group may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 216.66.8.75
- ASN:
- AS394230
- ISP:
- CDCK
- Server Location:
- Toronto
Ontario, ON
M5A
Canada, CA
Other sites hosted on 216.66.8.75
How fast does swi-prolog.discourse.group load? ▼
The average loading time of swi-prolog.discourse.group is 1488 ms. The Desktop speed index is 100 and mobile speed index is 93.- Average Load Time:
- 1488 ms
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.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)1.1s
First Contentful Paint (FCP)1.2s
First Input Delay (FID)0
Interaction To Next Paint (INP)48ms
Largest Contentful Paint (LCP)1.3s
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.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)1.1s
First Contentful Paint (FCP)1.2s
First Input Delay (FID)0
Interaction To Next Paint (INP)48ms
Largest Contentful Paint (LCP)1.3s
Lab Data
LCP request discovery
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP
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 about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Largest Contentful Paint 0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
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 about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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 about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
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.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)1.2s
First Contentful Paint (FCP)1.5s
First Input Delay (FID)0
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)1.5s
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.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)1.2s
First Contentful Paint (FCP)1.5s
First Input Delay (FID)0
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)1.5s
Lab Data
LCP request discovery
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP
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 about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
First Contentful Paint 2.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Largest Contentful Paint 2.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 2.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Does swi-prolog.discourse.group use compression? ▼
Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on swi-prolog.discourse.group are reduced by 91%.
swi-prolog.discourse.group use br compression.
Original size: 73.25 KB
Compressed size: 6.36 KB
File reduced by: 66.88 KB (91%)
Compressed size: 6.36 KB
File reduced by: 66.88 KB (91%)
Google Safe Browsing ▼
Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.SSL Checker - SSL Certificate Verify ▼
An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. swi-prolog.discourse.group supports HTTPS. swi-prolog.discourse.group supports HTTPS
Verifying SSL Support. Please wait...
Common Name: *.discourse.group
Organization:
Location:
Issuer: R13
Valid from: Oct 19 00:01:57 2025 GMT
Valid until: Jan 17 00:01:56 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization:
Location:
Issuer: R13
Valid from: Oct 19 00:01:57 2025 GMT
Valid until: Jan 17 00:01:56 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R13
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Verify HTTP/2 Support ▼
HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. swi-prolog.discourse.group supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...
Http Header ▼
HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.server: nginx
date: Sun, 14 Dec 2025 01:23:47 GMT
content-type: text/html; charset=utf-8
vary: Accept-Encoding
x-frame-options: SAMEORIGIN
x-xss-protection: 0
x-content-type-options: nosniff
x-permitted-cross-domain-policies: none
referrer-policy: strict-origin-when-cross-origin
x-discourse-route: list/latest
x-discourse-crawler-view: true
vary: Accept
cross-origin-opener-policy: same-origin-allow-popups
cache-control: no-cache, no-store
content-security-policy: upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-0G6wfMV91Gju7BxKDTUwXA0we' 'strict-dynamic'; frame-ancestors 'self' https://www.swi-prolog.org; manifest-src 'self'
x-discourse-cached: skip
x-request-id: 32f4a8aa-2a79-423e-942d-aeb7e60ae94d
x-discourse-trackview: 1
content-encoding: br
cdck-proxy-id: app-router-tieadvanced02.yyz2
strict-transport-security: max-age=31536000
cdck-proxy-id: app-balancer-tieinterceptor1b.yyz2
DNS Lookup ▼
DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.| Type | Ip | Target/Txt | TTL |
| CNAME | 899 |