Cashmachine.La - Info receives about 272 unique visitors and 544 (2.00 per visitor) page views per day which should earn about $2.22/day from advertising revenue. Estimated site value is $1,621.29. According to Alexa Traffic Rank is ranked number 3,898,321 in the world and 6.0E-6% of global Internet users visit it. Site is hosted in New York, New York, 10013, United States and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

Squarespace Profile

Last update was 51 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

272 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
3,898,321 visit alexa
Alexa Reach:
6.0E-6%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

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

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Squarespace, Inc. 
Server Location:
New York
New York, NY
United States, US

Other sites hosted on

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Serve images in next-gen formats - Potential savings of 1,100 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

SizePotential Savings
872 KB778 KB
199 KB59 KB
180 KB58 KB
161 KB57 KB
122 KB42 KB
226 KB39 KB
233 KB34 KB
59 KB33 KB
Avoids an excessive DOM size - 60 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 26 requests • 3,291 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
263291 KB
92057 KB
4836 KB
6260 KB
4101 KB
130 KB
28 KB
00 KB
213161 KB
Eliminate render-blocking resources - Potential savings of 1,110 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
2 KB190
8 KB190
415 KB910
398 KB870
6 KB190
Efficiently encode images - Potential savings of 701 KB
Optimized images load faster and consume less cellular data. Learn more.

SizePotential Savings
872 KB695 KB
199 KB5 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms83 ms0 KB0 KB301
83 ms144 ms30 KB328 KB200text/htmlDocument
153 ms170 ms2 KB2 KB200text/cssStylesheet
154 ms454 ms8 KB19 KB200text/javascriptScript
154 ms199 ms415 KB1620 KB200text/javascriptScript
154 ms201 ms398 KB1773 KB200text/javascriptScript
154 ms173 ms6 KB32 KB200text/cssStylesheet
154 ms171 ms15 KB46 KB200text/javascriptScript
846 ms1003 ms99 KB99 KB200image/svg+xmlOther
948 ms1134 ms59 KB59 KB200image/jpegImage
948 ms1103 ms234 KB233 KB200image/jpegImage
949 ms983 ms873 KB872 KB200image/jpegImage
949 ms969 ms227 KB226 KB200image/jpegImage
949 ms984 ms180 KB180 KB200image/jpegImage
949 ms984 ms162 KB161 KB200image/jpegImage
949 ms968 ms199 KB199 KB200image/jpegImage
949 ms970 ms123 KB122 KB200image/jpegImage
951 ms1015 ms1 KB0 KB200application/jsonXHR
973 ms1017 ms1 KB3 KB200application/jsonXHR
975 ms1175 ms15 KB15 KB200application/font-woff2Font
976 ms1061 ms67 KB67 KB200application/font-woff2Font
976 ms1152 ms46 KB46 KB200application/font-woff2Font
976 ms1056 ms42 KB41 KB200application/font-woff2Font
976 ms994 ms40 KB39 KB200application/font-woff2Font
977 ms1105 ms51 KB51 KB200application/font-woff2Font
1184 ms1319 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 10 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
604800000 ms873 KB
604800000 ms234 KB
604800000 ms227 KB
604800000 ms199 KB
604800000 ms180 KB
604800000 ms162 KB
604800000 ms123 KB
604800000 ms59 KB
604800000 ms8 KB
604800000 ms0 KB
Minimize third-party usage - Third-party code blocked the main thread for 140 ms
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.

SizeMain-Thread Blocking Time
836 KB143 ms
269 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
471 ms
392 ms
863 ms
9 ms
872 ms
123 ms
1085 ms
6 ms
1192 ms
8 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
199 ms
85 ms
176 ms
79 ms
17 ms
128 ms
JavaScript execution time - 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
181 ms15 ms1 ms
170 ms132 ms26 ms
159 ms147 ms2 ms
159 ms135 ms22 ms
Properly size images - Potential savings of 448 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
872 KB97 KB
233 KB85 KB
226 KB83 KB
180 KB66 KB
161 KB59 KB
199 KB31 KB
122 KB19 KB
59 KB10 KB
Remove unused CSS - Potential savings of 26 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

SizePotential Savings
/*! Squarespace LESS Compiler (less.js language v1.3.3) */ .sqs-slide-wrapper[data-slide-type="cov...
27 KB26 KB
Avoid enormous network payloads - Total size was 3,291 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

873 KB
415 KB
398 KB
234 KB
227 KB
199 KB
180 KB
162 KB
123 KB
99 KB
Minimizes main-thread work - 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Script Evaluation
441 ms
83 ms
Script Parsing & Compilation
54 ms
Style & Layout
47 ms
Parse HTML & CSS
30 ms
Garbage Collection
27 ms
21 ms
Avoid chaining critical requests - 10 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 60 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. 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.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1.7MiB (86% reduction).

Compressing could save 743.5KiB (85% reduction).
Compressing and resizing***935-JXAQYYDBSAZTNATVL5IL/ke17ZwdGBToddI8pDm48kK60W-ob1oA2Fm-j4E_9NQB7gQa3H78H3Y0txjaiv_0fDoOvxcdMmMKkDsyUqMSsMWxHk725yiiHCCLfrh8O1z4YTzHvnKhyp6Da-NYroOW3ZGjoBKy3azqku80C789l0kD6Ec8Uq9YczfrzwR7e2Mh5VMMOxnTbph8FXiclivDQnof***TlCeE0rAhj6HUpXkw/IMG-0394.JPG?format=1500w could save 583.8KiB (94% reduction).
Compressing and resizing***TlCeE0rAhj6HUpXkw/IMG-6576.JPG?format=1500w could save 415.6KiB (93% reduction).
Compressing could save 17.1KiB (19% reduction).

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:***e6-min.css

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 73.7KiB (74% reduction).

Compressing could save 73.7KiB (74% reduction).

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (expiration not specified)
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 328.2 KB
Compressed size: 29.52 KB
File reduced by: 298.67 KB (91%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name:
Issuer: Let's Encrypt Authority X3
Valid from: Jan 6 05:07:05 2020 GMT
Valid until: Apr 5 05:07:05 2020 GMT

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

date: Tue, 07 Jan 2020 13:37:35 GMT
Age: 53007
Set-Cookie: crumb=BR+HL713bC7LMDc2N2U3ZWExY2QzYjBkNGIzOWU3NDA5MmMxM2Vh;Path=/
Content-Length: 0
x-contextid: iyZh1fCW/zTiYOGla
server: Squarespace

HTTP/1.1 200 OK
date: Tue, 07 Jan 2020 04:25:47 GMT
expires: Thu, 01 Jan 1970 00:00:00 GMT
content-type: text/html;charset=utf-8
etag: W/"3f03e029ecfbebfe157e45123293d507--gzip"
content-encoding: gzip
Vary: Accept-Encoding
Age: 86115
Set-Cookie: crumb=BXcoacMzQf6VM2Q1MWQyYjJmMTYwYWUyZjkzMTA4ZmZkYzFiMDZk;Path=/
Accept-Ranges: bytes
Content-Length: 30233
x-contextid: 4TeFqNdI/X76RUOs0
server: Squarespace

+ DNS Lookup

Type Ip Target TTL
MX 3600
MX 3600
MX 3600
MX 3600
MX 3600
SOA 3600
Serial Number 2016060807
Refresh 28800
Retry 7200
Expire 604800
Minimum TTL 0
A 571
A 571
A 571
A 571
NS 3570
NS 3570

+ Whois Lookup

Domain Created:
Domain Age:
4 years 9 months 20 days  

whois lookup at
Registry Domain ID: D7200607-LANIC
Registrar WHOIS Server:
Registrar URL:
Updated Date: 2019-03-26T06:23:50.0Z
Creation Date: 2015-03-18T02:13:33.0Z
Registry Expiry Date: 2020-03-18T23:59:59.0Z
Registrar:, Inc.
Registrar IANA ID:
Domain Status: clientRenewProhibited
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Domain Status: clientDeleteProhibited
Registrant Email:
Admin Email:
Tech Email:
DNSSEC: unsigned
Billing Email:
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.4805058800
URL of the ICANN Whois Inaccuracy Complaint Form:
>>> Last update of WHOIS database: 2020-01-08T04:21:33.0Z <<<

For more information on Whois status codes, please visit

This whois service is provided by LANIC and only contains
information pertaining to Internet domain names registered by our
our customers. By using this service you are agreeing (1) not to use any
information presented here for any purpose other than determining
ownership of domain names, (2) not to store or reproduce this data in
any way, (3) not to use any high-volume, automated, electronic processes
to obtain data from this service. Abuse of this service is monitored and
actions in contravention of these terms will result in being permanently
blacklisted. All data is (c) LANIC

Access to the whois service is rate limited. For more information, please
Last update was 51 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites
23 secs
25 secs
40 secs
1 min
1 min
1 min
1 min
1 min
2 mins
2 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget