Bizkaibizi.eus
Bizikleta elektrikoen alokairua Bizkaian | bizkaibizi-n - bizkaibizi
Domain Summary
What is the traffic rank for Bizkaibizi.eus?
• Bizkaibizi.eus ranks #1,473,926 globally on HypeStat.
What percent of global Internet users visit Bizkaibizi.eus?
• 1.41E-5% of global Internet users visit Bizkaibizi.eus
How many people visit Bizkaibizi.eus each day?
• Bizkaibizi.eus receives approximately 696 visitors and 1,031 page impressions per day.
Which countries does Bizkaibizi.eus receive most of its visitors from?
• Bizkaibizi.eus is mostly visited by people located in Spain.
How much Bizkaibizi.eus can earn?
• Bizkaibizi.eus should earn about $0.49/day from advertising revenue.
What is Bizkaibizi.eus estimated value?
• Estimated value of Bizkaibizi.eus is $414.67.
What IP addresses does Bizkaibizi.eus resolve to?
• Bizkaibizi.eus resolves to the IP addresses 157.97.108.157.
Where are Bizkaibizi.eus servers located in?
• Bizkaibizi.eus has servers located in Germany.
bizkaibizi.eus Profile

What technologies does bizkaibizi.eus use?
These are the technologies used at bizkaibizi.eus. bizkaibizi.eus has a total of 14 technologies installed in 14 different categories.bizkaibizi.eus Traffic Analysis
Bizkaibizi.eus is ranked #1,473,926 in the world. This website is viewed by an estimated 696 visitors daily, generating a total of 1K pageviews. This equates to about 21.1K monthly visitors. Bizkaibizi.eus traffic has increased by 28.26% compared to last month.Daily Visitors696
24.81%
Monthly Visits21.1K
28.26%
Pages per Visit1.48
1.54%
Visit duration01:37
68.52%
Bounce Rate72.12%
0.13%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 696
- Monthly Visits:
- 21,089
- Pages per Visit:
- 1.48
- Daily Pageviews:
- 1,031
- Avg. visit duration:
- 01:37
- Bounce rate:
- 72.12%
- Global Reach:
- 1.41E-5%
- Monthly Visits (SEMrush):
- 8,237
- Monthly Unique Visitors (SEMrush):
- 8,015
- Monthly Visits (SimilarWeb):
- 20,471
- HypeRank:
- 1,473,926
- SEMrush Rank:
- 8,217,867
- SimilarWeb Rank:
- 1,473,926
Traffic sources
- Direct:
- 55.15%
- Referral:
- 0%
- Search:
- 44.85%
- Social:
- 0%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 8.84%
- Mobile:
- 91.16%
Total Visits Last 3 Months
5.9K
JUN
16.4K
JUL
21.1K
AUG
Visitors by country
- Country
- Users%
- Spain 100.00%
Backlinks Report ▼
Bizkaibizi.eus has a total of 22 backlinks from 21 referring domains and most of them comes from Moldova.- Total Backlinks:
- 22
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 21
- Referring IPs:
- 19
- Authority Domain Score:
- 27
Backlinks by country
- Country
- Domains
- Moldova 3
- Germany 1
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 14
- .top
- 2
- .net
- 2
- .edu
- 0
- .gov
- 0
Last update was 15 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with bizkaibizi.eus 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:
- bizkaibizi.eus
- Rank:
(Rank based on keywords, cost and organic traffic) - 8,217,867
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 35
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 9
- 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 $0.5 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $14.7 and annual gross revenue of approximately $178.9. Based on these figures, the site's net worth is estimated at around $414.7.How much would bizkaibizi.eus make?
- Daily Revenue:
- $0.49
- Monthly Revenue:
- $14.70
- Yearly Revenue:
- $178.85
Daily earning by country
- CountryPageviewsEarning
- Spain 1,031$0.49
Loss of money due to Adblock?
- Daily Revenue Loss:
- $0.09
- Monthly Revenue Loss:
- $2.82
- Yearly Revenue Loss:
- $34.32
- Daily Pageviews Blocked:
- 196
- Monthly Pageviews Blocked:
- 5,877
- Yearly Pageviews Blocked:
- 71,500
Daily revenue loss by country
- CountryBlockedLost Money
- Spain 196$0.09
How much is bizkaibizi.eus worth?
- Website Value:
- $414.7
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- bizkaibizi.eus
- 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:
- bizkaibizi.eus
- 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:
- bizkaibizi.eus
- 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 bizkaibizi.eus hosted? ▼
Bizkaibizi.eus may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 157.97.108.157
- ASN:
- AS8560
- ISP:
- 1&1 Internet SE
- Server Location:
Germany, DE
Other sites hosted on 157.97.108.157
How fast does bizkaibizi.eus load? ▼
The average loading time of bizkaibizi.eus is 265 ms. The Desktop speed index is 81 and mobile speed index is 0.- Average Load Time:
- 265 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)23ms
Time To First Byte (TTFB)346ms
First Contentful Paint (FCP)791ms
First Input Delay (FID)0
Interaction To Next Paint (INP)65ms
Largest Contentful Paint (LCP)1.2s
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)23ms
Time To First Byte (TTFB)346ms
First Contentful Paint (FCP)791ms
First Input Delay (FID)0
Interaction To Next Paint (INP)65ms
Largest Contentful Paint (LCP)1.2s
Lab Data
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Largest Contentful Paint 1.2 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
Max Potential First Input Delay 330 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
Time to Interactive 2.3 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
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 about optimal lazy loading
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Total Blocking Time 290 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
Speed Index 1.6 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
First Contentful Paint 0.9 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
INP breakdown
Start investigating with the longest subpart. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest subpart. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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 how to defer third-parties with a facade
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Does bizkaibizi.eus 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 bizkaibizi.eus are reduced by 79%.
bizkaibizi.eus use gzip compression.
Original size: 55.71 KB
Compressed size: 11.29 KB
File reduced by: 44.42 KB (79%)
Compressed size: 11.29 KB
File reduced by: 44.42 KB (79%)
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. bizkaibizi.eus supports HTTPS. bizkaibizi.eus supports HTTPS
Verifying SSL Support. Please wait...
Common Name: www.bizkaibizi.eus
Organization:
Location:
Issuer: E5
Valid from: Aug 8 08:04:21 2025 GMT
Valid until: Nov 6 08:04:20 2025 GMT
Authority: CA:FALSE
Keysize:
Organization:
Location:
Issuer: E5
Valid from: Aug 8 08:04:21 2025 GMT
Valid until: Nov 6 08:04:20 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: E5
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:
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:
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. bizkaibizi.eus 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.content-length: 0
location: https://www.bizkaibizi.eus/
cache-control: no-cache
HTTP/2 301
date: Sat, 20 Sep 2025 18:33:46 GMT
server: Apache
x-redirect-by: WordPress
location: https://www.bizkaibizi.eus/eu/
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
content-security-policy: default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com; script-src-elem 'self' 'unsafe-inline' https://cdn.maptiler.com https://www.googletagmanager.com https://consent.cookiebot.com https://templates.nextbike.net; img-src 'self' https://secure.gravatar.com https://ps.w.org https://s.w.org https://i0.wp.com https://i1.wp.com https://www.googletagmanager.com https://imgsct.cookiebot.com https://static.nextbike.net https://a.tile.openstreetmap.org https://b.tile.openstreetmap.org https://c.tile.openstreetmap.org https://cdn.maptiler.com https://api.maptiler.com https://nuernbergmobil.de https://nextbike-live.pluspol-networks.de data:; style-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://templates.nextbike.net https://api.nextbike.net https://maps.nextbike.net https://cdn.maptiler.com; font-src 'self' data: https://templates.nextbike.net https://api.nextbike.net https://maps.nextbike.net; connect-src 'self' https://*.wordpress.com https://www.google-analytics.com https://region1.google-analytics.com https://*.google-analytics.com https://templates.nextbike.net https://api.nextbike.net https://maps.nextbike.net https://static.nextbike.net https://api.maptiler.com; media-src 'self'; frame-src 'self' https://consentcdn.cookiebot.com; manifest-src 'self'; worker-src blob: https://cdn.maptiler.com
x-xss-protection: 1; mode=block
referrer-policy: origin-when-cross-origin
content-length: 0
content-type: text/html; charset=UTF-8
age: 55
x-cache: HIT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Wed, 11 Jan 1984 05:00:00 GMT
pragma: no-cache
x-seen: be_cache
strict-transport-security: max-age=16000000
HTTP/2 200
date: Sat, 20 Sep 2025 18:33:46 GMT
server: Apache
link: <https://www.bizkaibizi.eus/eu/wp-json/>; rel="https://api.w.org/", <https://www.bizkaibizi.eus/eu/wp-json/wp/v2/pages/659>; rel="alternate"; title="JSON"; type="application/json", <https://www.bizkaibizi.eus/eu/>; rel=shortlink
content-encoding: gzip
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
content-security-policy: default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com; script-src-elem 'self' 'unsafe-inline' https://cdn.maptiler.com https://www.googletagmanager.com https://consent.cookiebot.com https://templates.nextbike.net; img-src 'self' https://secure.gravatar.com https://ps.w.org https://s.w.org https://i0.wp.com https://i1.wp.com https://www.googletagmanager.com https://imgsct.cookiebot.com https://static.nextbike.net https://a.tile.openstreetmap.org https://b.tile.openstreetmap.org https://c.tile.openstreetmap.org https://cdn.maptiler.com https://api.maptiler.com https://nuernbergmobil.de https://nextbike-live.pluspol-networks.de data:; style-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://templates.nextbike.net https://api.nextbike.net https://maps.nextbike.net https://cdn.maptiler.com; font-src 'self' data: https://templates.nextbike.net https://api.nextbike.net https://maps.nextbike.net; connect-src 'self' https://*.wordpress.com https://www.google-analytics.com https://region1.google-analytics.com https://*.google-analytics.com https://templates.nextbike.net https://api.nextbike.net https://maps.nextbike.net https://static.nextbike.net https://api.maptiler.com; media-src 'self'; frame-src 'self' https://consentcdn.cookiebot.com; manifest-src 'self'; worker-src blob: https://cdn.maptiler.com
x-xss-protection: 1; mode=block
referrer-policy: origin-when-cross-origin
content-length: 11563
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
age: 54
accept-ranges: bytes
x-cache: HIT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Wed, 11 Jan 1984 05:00:00 GMT
pragma: no-cache
x-seen: be_cache
strict-transport-security: max-age=16000000
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 |
SOA | 300 | ||
Mname | ns.bizkaia.net | ||
Rname | adi.lantik.bizkaia.net | ||
Serial Number | 24 | ||
Refresh | 7200 | ||
Retry | 600 | ||
Expire | 1209600 | ||
Minimum TTL | 300 | ||
TXT | 300 | ||
TXT | 300 | ||
TXT | 300 | ||
MX | 300 | ||
MX | 300 | ||
NS | 300 | ||
NS | 300 | ||
NS | 300 | ||
A | 157.97.108.157 | 300 |