Lindsay.ca.us
Lindsay Home Page | Lindsay California
Domain Summary
What is the traffic rank for Lindsay.ca.us?
• Lindsay.ca.us ranks #4,077,117 globally on HypeStat.
What percent of global Internet users visit Lindsay.ca.us?
• 2.3E-6% of global Internet users visit Lindsay.ca.us
How many people visit Lindsay.ca.us each day?
• Lindsay.ca.us receives approximately 113 visitors and 232 page impressions per day.
Which countries does Lindsay.ca.us receive most of its visitors from?
• Lindsay.ca.us is mostly visited by people located in United States,India.
How much Lindsay.ca.us can earn?
• Lindsay.ca.us should earn about $0.96/day from advertising revenue.
What is Lindsay.ca.us estimated value?
• Estimated value of Lindsay.ca.us is $1,046.69.
What IP addresses does Lindsay.ca.us resolve to?
• Lindsay.ca.us resolves to the IP addresses 162.221.183.17.
Where are Lindsay.ca.us servers located in?
• Lindsay.ca.us has servers located in Buffalo, New York, 14221, United States.
lindsay.ca.us Profile
Title:Lindsay Home Page | Lindsay California
What technologies does lindsay.ca.us use?
These are the technologies used at lindsay.ca.us. lindsay.ca.us has a total of 4 technologies installed in 4 different categories.lindsay.ca.us Traffic Analysis
Lindsay.ca.us is ranked #4,077,117 in the world. This website is viewed by an estimated 113 visitors daily, generating a total of 232 pageviews. This equates to about 3.4K monthly visitors. Lindsay.ca.us traffic has decreased by 81.6% compared to last month.Daily Visitors113
26.61%
Monthly Visits3.4K
81.6%
Pages per Visit2.06
47.69%
Visit duration00:44
737.5%
Bounce Rate35.34%
37.23%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 113
- Monthly Visits:
- 3,424
- Pages per Visit:
- 2.06
- Daily Pageviews:
- 232
- Avg. visit duration:
- 00:44
- Bounce rate:
- 35.34%
- Global Reach:
- 2.3E-6%
- Monthly Visits (SEMrush):
- 1,420
- Monthly Unique Visitors (SEMrush):
- 1,420
- Monthly Visits (SimilarWeb):
- 3,327
- HypeRank:
- 4,077,117
- SEMrush Rank:
- 170,653
- SimilarWeb Rank:
- 4,077,117
Traffic sources
- Direct:
- 38.03%
- Referral:
- 9.15%
- Search:
- 52.82%
- Social:
- 0%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 100.00%
- Mobile:
- 0%
Total Visits Last 3 Months
4.5K
FEB
18.6K
MAR
3.4K
APR
Visitors by country
- Country
- Users%
- United States 84.03%
- India 15.97%
Backlinks Report ▼
Lindsay.ca.us has a total of 376 backlinks from 77 referring domains and most of them comes from United States.- Total Backlinks:
- 376
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 77
- Referring IPs:
- 88
- Authority Domain Score:
- 32
Backlinks by country
- Country
- Domains
- United States 26
- India 3
- Russian Federation 2
- Romania 2
- Singapore 1
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 53
- .org
- 5
- .net
- 3
- .gov
- 1
- .edu
- 0
Last update was 39 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 lindsay.ca.us 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:
- lindsay.ca.us
- Rank:
(Rank based on keywords, cost and organic traffic) - 170,653
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 914
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 10,647
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $1,007.00
Revenue report ▼
Google.com would generate approximately $1 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $28.8 and annual gross revenue of approximately $350.4. Based on these figures, the site's net worth is estimated at around $1K.How much would lindsay.ca.us make?
- Daily Revenue:
- $0.96
- Monthly Revenue:
- $28.80
- Yearly Revenue:
- $350.40
Daily earning by country
- CountryPageviewsEarning
- United States 195$0.94
- India 37$0.01
Loss of money due to Adblock?
- Daily Revenue Loss:
- $0.17
- Monthly Revenue Loss:
- $5.20
- Yearly Revenue Loss:
- $63.30
- Daily Pageviews Blocked:
- 45
- Monthly Pageviews Blocked:
- 1,364
- Yearly Pageviews Blocked:
- 16,595
Daily revenue loss by country
- CountryBlockedLost Money
- United States 35$0.17
- India 10$0.00
How much is lindsay.ca.us worth?
- Website Value:
- $1K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- lindsay.ca.us
- 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:
- lindsay.ca.us
- 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:
- lindsay.ca.us
- 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 lindsay.ca.us hosted? ▼
Lindsay.ca.us may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 162.221.183.17
- ASN:
- AS16509
- ISP:
- Amazon.com, Inc.
- Server Location:
- Buffalo
New York, NY
14221
United States, US
Other sites hosted on 162.221.183.17
How fast does lindsay.ca.us load? ▼
The average loading time of lindsay.ca.us is 297 ms. The Desktop speed index is 88 and mobile speed index is 64.- Average Load Time:
- 297 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)4ms
Time To First Byte (TTFB)811ms
First Contentful Paint (FCP)2.7s
First Input Delay (FID)0
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)2.8s
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)4ms
Time To First Byte (TTFB)919ms
First Contentful Paint (FCP)2.3s
First Input Delay (FID)0
Interaction To Next Paint (INP)33ms
Largest Contentful Paint (LCP)2.4s
Lab Data
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 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
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
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Legacy JavaScript
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
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
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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
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
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
First Contentful Paint 1.5 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
Largest Contentful Paint 1.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
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
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
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a SLOW 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)725ms
First Contentful Paint (FCP)3.1s
First Input Delay (FID)0
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)3.1s
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)2.9s
First Input Delay (FID)0
Interactive To Next Paint (INP)96ms
Largest Contentful Paint (LCP)2.9s
Lab Data
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
Max Potential First Input Delay 100 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
First Contentful Paint 5.7 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
Speed Index 5.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
Total Blocking Time 20 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
Largest Contentful Paint 5.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
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 6.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
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Legacy JavaScript
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
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 lindsay.ca.us 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 lindsay.ca.us are reduced by 76%.
lindsay.ca.us use gzip compression.
Original size: 33.66 KB
Compressed size: 7.78 KB
File reduced by: 25.88 KB (76%)
Compressed size: 7.78 KB
File reduced by: 25.88 KB (76%)
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. lindsay.ca.us has 79 Safety Reputations.- Status:
- UNKNOWN
- Safety Reputations:
- 79
- Safety Confidence:
- 10
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. lindsay.ca.us supports HTTPS. lindsay.ca.us supports HTTPS
Verifying SSL Support. Please wait...
Common Name: lindsay.ca.us
Organization:
Location:
Issuer: R10
Valid from: Apr 19 21:52:11 2025 GMT
Valid until: Jul 18 21:52:10 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization:
Location:
Issuer: R10
Valid from: Apr 19 21:52:11 2025 GMT
Valid until: Jul 18 21:52:10 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R10
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. lindsay.ca.us does not support 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: Thu, 15 May 2025 21:38:47 GMT
location: http://www.lindsay.ca.us/
cache-control: max-age=1209600
content-length: 233
content-type: text/html; charset=iso-8859-1
x-cache-original-ttl: 1209600s
x-backend-age: 18274
age: 0
expires: Fri, 16 May 2025 03:03:21 GMT
x-cache: cached
x-full-url: lindsay.ca.us/
x-rpid: RP3E1A600
cacheid: 1
set-cookie: HAPersist=d-ssle1a1-pa1-rpe1a1; path=/
cache-control: private
connection: close
HTTP/1.1 302 Found
date: Fri, 16 May 2025 02:43:21 GMT
location: https://www.lindsay.ca.us/
content-length: 210
content-type: text/html; charset=iso-8859-1
x-cache-original-ttl: 1209600s
age: 0
expires: Fri, 16 May 2025 02:43:21 GMT
x-cache: uncached
cache-control: private, no-cache
x-full-url: www.lindsay.ca.us/
x-rpid: RP3E1A600
cacheid: 2
set-cookie: HAPersist=d-ssle1a1-pa2-rpe1a1; path=/
connection: close
HTTP/1.1 200 OK
date: Thu, 15 May 2025 20:13:57 GMT
content-language: en
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
link: </home>; rel="canonical",</node/161>; rel="shortlink"
cache-control: public, max-age=86400
vary: Cookie,Accept-Encoding
content-encoding: gzip
etag: "1747340037-1"
last-modified: Thu, 15 May 2025 20:13:57 GMT
x-sid: AS3E1A703
content-type: text/html; charset=utf-8
x-cache-original-ttl: 86400s
x-backend-age: 23363
age: 0
expires: Fri, 16 May 2025 03:03:21 GMT
x-cache: cached
x-full-url: www.lindsay.ca.us/
x-rpid: RP3E1D600
accept-ranges: bytes
content-length: 7971
cacheid: 4
set-cookie: HAPersist=d-ssle1a1-pa2-rpe1d1; path=/
cache-control: private
connection: close
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 |
MX | 900 | ||
SOA | 86400 | ||
Mname | ns1.ocsnet.net | ||
Rname | Administrator.ocsnet.net | ||
Serial Number | 2024030401 | ||
Refresh | 7200 | ||
Retry | 1800 | ||
Expire | 604800 | ||
Minimum TTL | 3600 | ||
TXT | 10800 | ||
A | 162.221.183.17 | 240 | |
NS | 7140 | ||
NS | 7140 | ||
NS | 7140 |
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 February 5, 2003 and will expire on February 4, 2026 if not renewed. This website is now assigned through the registrar US Locality. The WHOIS data for this website's domain was last updated on March 27, 2025.- Domain Created:
- 2003-02-05
- Domain Expires:
- 2026-02-04
- Domain Updated:
- 2025-03-27
- Domain Age:
- 22 years 4 months 19 days
- Domain Registrar:
- US Locality
- Domain Owner:
- City of Lindsay, CA
- WhoIs:
Domain Name: lindsay.ca.us Registry Domain ID: D3590755-US Registrar WHOIS Server: Registrar URL: www.whois.us Updated Date: 2025-03-27T21:18:22Z Creation Date: 2003-02-05T09:00:38Z Registry Expiry Date: 2026-02-04T23:59:59Z Registrar: US Locality Registrar IANA ID: Registrar Abuse Contact Email: Registrar Abuse Contact Phone: Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited Registry Registrant ID: C38839740-US Registrant Name: William Zigler Registrant Organization: City of Lindsay, CA Registrant Street: PO Box 369 Registrant Street: 251 E Honolulu St Registrant Street: Registrant City: Lindsay Registrant State/Province: CA Registrant Postal Code: 93247 Registrant Country: US Registrant Phone: +1.5595627103 Registrant Phone Ext: Registrant Fax: +1.5595627100 Registrant Fax Ext: Registrant Email:Registrant Application Purpose: P5 Registrant Nexus Category: C21 Registry Admin ID: C38839740-US Admin Name: William Zigler Admin Organization: City of Lindsay, CA Admin Street: PO Box 369 Admin Street: 251 E Honolulu St Admin Street: Admin City: Lindsay Admin State/Province: CA Admin Postal Code: 93247 Admin Country: US Admin Phone: +1.5595627103 Admin Phone Ext: Admin Fax: +1.5595627100 Admin Fax Ext: Admin Email:
Admin Application Purpose: P5 Admin Nexus Category: C21 Registry Tech ID: C8441126-US Tech Name: Ryan Walker Tech Organization: OACYS Technology Tech Street: 767 North Porter Road Tech Street: Tech Street: Tech City: Porterville Tech State/Province: CA Tech Postal Code: 93257 Tech Country: US Tech Phone: +1.5597814123 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email:
Tech Application Purpose: P5 Tech Nexus Category: C21 Registry Domain Manager ID: C3659196-US Domain Manager Name: usTLD Locality Administrator Domain Manager Organization: Registry Services, LLC Domain Manager Street: 100 S. Mill Avenue Domain Manager Street: Suite 1600 Domain Manager Street: Domain Manager City: Tempe Domain Manager State/Province: AZ Domain Manager Postal Code: 85281 Domain Manager Country: US Domain Manager Phone: +1.4806519999 Domain Manager Phone Ext: Domain Manager Fax: Domain Manager Fax Ext: Domain Manager Email:
Domain Manager Application Purpose: P5 Domain Manager Nexus Category: C21 Name Server: ns2.ocsnet.net Name Server: ns1.ocsnet.net Name Server: ns3.ocsnet.net DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2025-05-16T02:44:21Z