waze009.com Waze009.com

   
WAZE

Domain Summary

What percent of global Internet users visit Waze009.com?

• 8.3E-6% of global Internet users visit Waze009.com

How many people visit Waze009.com each day?

• Waze009.com receives approximately 408 visitors and 3,879 page impressions per day.

How much Waze009.com can earn?

• Waze009.com should earn about $15.83/day from advertising revenue.

What is Waze009.com estimated value?

• Estimated value of Waze009.com is $17,763.38.

What IP addresses does Waze009.com resolve to?

• Waze009.com resolves to the IP addresses 34.160.150.204.

Where are Waze009.com servers located in?

• Waze009.com has servers located in Kansas City, Missouri, 64184, United States.

waze009.com Profile

Title:WAZE
Edit Site Info

What technologies does waze009.com use?

These are the technologies used at waze009.com. waze009.com has a total of 11 technologies installed in 5 different categories.
Web Servers
Apache HTTP Server Apache HTTP Server
CDN
cdnjs cdnjs
Google Cloud CDN Google Cloud CDN
Unpkg Unpkg
CloudFlare CloudFlare
Google Cloud Google Cloud
JavaScript Libraries
crypto-js crypto-js
jQuery jQuery
Miscellaneous
HTTP/3 HTTP/3
PWA PWA
Operating Systems
Ubuntu Ubuntu

waze009.com Traffic Analysis

This website is viewed by an estimated 408 visitors daily, generating a total of 3.9K pageviews. This equates to about 12.4K monthly visitors. Waze009.com traffic has increased by 76.49% compared to last month.
Daily Visitors408
26.83%
Monthly Visits12.4K
76.49%
Pages per Visit9.50
176.56%
Visit duration28:06
874.57%
Bounce Rate6.19%
88.33%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
408
Monthly Visits:
12,362
Pages per Visit:
9.50
Daily Pageviews:
3,879
Avg. visit duration:
28:06
Bounce rate:
6.19%
Global Reach:
8.3E-6%
Monthly Visits (SEMrush):
12,499
Monthly Unique Visitors (SEMrush):
889
HypeRank:
n/a
SEMrush Rank:
16,290,729
SimilarWeb Rank:
6,402,669
*All traffic values are estimates only.

Traffic sources

Direct:
100.00%
Referral:
0%
Search:
0%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

1.1K
DEC
7K
JAN
12.4K
FEB
Last update was 139 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with waze009.com in any way. Only publicly available statistics data are displayed.

Search Engine Indexes ▼

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
1

  ▼

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.
SemRushSemRush
Domain:
  waze009.com
Rank:
(Rank based on keywords, cost and organic traffic)
  16,290,729
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  9
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $15.8 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $474.9 and annual gross revenue of approximately $5.8K. Based on these figures, the site's net worth is estimated at around $17.8K.

How much would waze009.com make?

Daily Revenue:
$15.83
Monthly Revenue:
$474.90
Yearly Revenue:
$5,777.95
*All earnings values are estimates only.

How much is waze009.com worth?

Website Value:
$17.8K

Ad Experience Report ▼

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
waze009.com
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:
waze009.com
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:
waze009.com
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 waze009.com hosted? ▼

Waze009.com may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
34.160.150.204
ASN:
AS396982 
ISP:
Google LLC 
Server Location:
Kansas City
Missouri, MO
64184
United States, US
 

Other sites hosted on 34.160.150.204

How fast does waze009.com load? ▼

The average loading time of waze009.com is 1173 ms. The Desktop speed index is 97 and mobile speed index is 80.
Average Load Time:
1173 ms

Page Speed (Google PageSpeed Insights) - Desktop

97
0-49 50-89 90-100 i

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)6ms 97% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)984ms 54% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 54% 36% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 36% 8% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 8%
First Contentful Paint (FCP)1.8s 76% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 76% 14% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 14% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)49ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 1% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 1% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.7s 88% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 88% 7% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 7% 3% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 3%

Origin Data

All pages served from this origin have an SLOW 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)5ms 87% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 87% 5% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 5% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
Time To First Byte (TTFB)452ms 90% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 90% 8% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 8% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)5.5s 33% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 33% 14% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 14% 52% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 52%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)411ms 61% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 61% 17% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 17% 20% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 20%
Largest Contentful Paint (LCP)6.0s 37% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 37% 15% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 15% 46% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 46%

Lab Data

Time to Interactive 0.9 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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Optimize DOM size  
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
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
Max Potential First Input Delay 110 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
Total Blocking Time 10 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
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs

Page Speed (Google PageSpeed Insights) - Mobile

80
0-49 50-89 90-100 i

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 97% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 98% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.2s 54% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 40% 50% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 50% 8% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 8%
First Contentful Paint (FCP)1.7s 76% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 78% 14% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 14% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)140ms 98% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 84% 10% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 10% 5% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 5%
Largest Contentful Paint (LCP)1.7s 88% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 90% 6% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 6% 3% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 3%

Origin Data

All pages served from this origin have an SLOW 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)3ms 89% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 89% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 8% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 8%
Time To First Byte (TTFB)356ms 86% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 86% 11% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 11% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)5.7s 42% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 42% 10% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 10% 47% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 47%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)430ms 58% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 58% 18% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 18% 23% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 23%
Largest Contentful Paint (LCP)6.2s 47% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 47% 10% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 10% 42% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 42%

Lab Data

INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Time to Interactive 3.8 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
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
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
Max Potential First Input Delay 70 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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Largest Contentful Paint 3.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
Total Blocking Time 10 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
Speed Index 5.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
First Contentful Paint 3.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Optimize DOM size  
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides

Does waze009.com 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 waze009.com are reduced by 89%.
waze009.com use gzip compression.
Original size: 598.27 KB
Compressed size: 62.89 KB
File reduced by: 535.38 KB (89%)

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.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.
Status:
  SUSPICIOUS

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. waze009.com supports HTTPS.
 waze009.com supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: waze009.com
Organization:
Location:
Issuer: Sectigo RSA Domain Validation Secure Server CA
Valid from: Dec 27 00:00:00 2024 GMT
Valid until: Dec 25 23:59:59 2025 GMT
Authority: CA:FALSE
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.
 waze009.com 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. 
date: Sun, 16 Mar 2025 23:07:02 GMT
server: Apache/2.4.41 (Ubuntu)
vary: Accept-Encoding
content-encoding: gzip
content-type: text/html; charset=UTF-8
via: 1.1 google
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

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
A 34.160.150.204 52
NS coraline.ns.cloudflare.com 172728
NS toby.ns.cloudflare.com 172728
HINFO 3600

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on December 25, 2023 and will expire on December 25, 2025 if not renewed. This website is now assigned through the registrar 1API GmbH. The WHOIS data for this website's domain was last updated on December 26, 2023.
Domain Created:
2023-12-25
Domain Expires:
2025-12-25
Domain Updated:
2023-12-26
Domain Age:
1 years 7 months 9 days
Domain Registrar:
1API GmbH
Domain Owner:
REDACTED FOR PRIVACY
WhoIs:
 

Domain Name: WAZE009.COM
Registry Domain ID: 2840502490_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.1api.net
Registrar URL: http://www.1api.net
Updated Date: 2023-12-26T09:24:43Z
Creation Date: 2023-12-25T14:42:01Z
Registrar Registration Expiration Date: 2025-12-25T14:42:01Z
Registrar: 1API GmbH
Registrar IANA ID: 1387
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +49.68949396850
Reseller: iDotz.Net - Domain Name Registrar & Service https://idotz.net
Domain Status: clientTransferProhibited - http://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID: 
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: CA
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: contact via https://www.1api.net/send-message/waze009.com/registrant
Registry Admin ID: 
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: contact via https://www.1api.net/send-message/waze009.com/admin
Registry Tech ID: 
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: contact via https://www.1api.net/send-message/waze009.com/tech
Name Server: toby.ns.cloudflare.com
Name Server: coraline.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System:
http://wdprs.internic.net/
>>> Last update of WHOIS database: 2025-03-16T23:08:13Z