squareup.com score is

Top Technologies
CloudFlare
CDN
Google Font API
Font Scripts
WordPress
CMS
Nginx
Web Servers
Font Awesome
Font Scripts
Apache
Web Servers
Twitter Bootstrap
Web Frameworks
Google Tag Manager
Tag Managers

86 squareup.com Last Updated: 3 years

Success 63% of passed verification steps
Warning 30% of total warning
Errors 7% of total errors, require fast action

Desktop Speed Score

Mobile Speed Score

Performance Desktop Score 59%
Best Practices Desktop Score 93%
SEO Desktop Score 83%
Progressive Web App Desktop Score 36%
Performance Mobile Score 10%
Best Practices Mobile Score 93%
SEO Mobile Score 85%
Progressive Web App Mobile Score 42%
Page Authority Authority 71%
Domain Authority Domain Authority 88%
Moz Rank 7.1/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 51 Characters
SQUARE: SOLUTIONS & TOOLS TO GROW YOUR BUSINESS
Meta Description 158 Characters
Square helps millions of sellers run their business-from secure credit card processing to point of sale solutions. Get paid faster with Square. Sign up today!
Effective URL 20 Characters
https://squareup.com
Excerpt Page content
Square: Solutions & Tools to Grow Your Business The future of business is yours to shape.Get startedFind what works. For whatever’s next.See our solutionsSquareGet startedContact SalesStart reaching more customers online.Set up a free online store that syncs with your inventory and your social media—to help you meet customers wherever they shop.Start selling onlineConnect your restaurant, from kitchen to community.Reach your diners anywhere, with an integrated POS, Kitchen Display System, and online ordering solution.Get the toolsGet paid fast from anywhere.Send professional invoices, track them in real time, and accept payments online—all from one place. Save time with auto-billing, stored information, and powerfu...
Keywords Cloud Density
square27 business24 more17 learn14 online11 payments9 sales7 services7 service7 hardware7
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
square 27
business 24
more 17
learn 14
online 11
payments 9
sales 7
services 7
service 7
hardware 7
Google Preview Your look like this in google search result
SQUARE: SOLUTIONS & TOOLS TO GROW YOUR BUSINESS
https://squareup.com
Square helps millions of sellers run their business-from secure credit card processing to point of sale solutions. Get paid faster with Square. Sign u
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~258.5 KB
Code Size: ~201.96 KB
Text Size: ~56.54 KB Ratio: 21.87%

squareup.com Estimation Traffic and Earnings

126,905
Unique Visits
Daily
234,774
Pages Views
Daily
$227
Income
Daily
3,553,340
Unique Visits
Monthly
6,691,059
Pages Views
Monthly
$5,675
Income
Monthly
41,117,220
Unique Visits
Yearly
78,884,064
Pages Views
Yearly
$59,928
Income
Yearly

Desktop Speed Score

Desktop Screenshot
Keep request counts low and transfer sizes small 213 requests • 1,395 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Time to Interactive 3.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Cumulative Layout Shift 1.407
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid chaining critical requests 5 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
First CPU Idle 2.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Remove unused CSS Potential savings of 98 KiB
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
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS
Minimize third-party usage Third-party code blocked the main thread for 110 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
First Meaningful Paint 1.5 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid serving legacy JavaScript to modern browsers Potential savings of 47 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Minimize main-thread work 2.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid an excessive DOM size 1,553 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Links do not have descriptive text 13 links found
Descriptive link text helps search engines understand your content
Total Blocking Time 260 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Remove unused JavaScript Potential savings of 265 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce initial server response time Root document took 750 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
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
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minify JavaScript Potential savings of 10 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
JavaScript execution time 0.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid multiple page redirects Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Properly size images Potential savings of 71 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Serve static assets with an efficient cache policy 26 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources Potential savings of 120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Estimated Input Latency 20 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
Avoids enormous network payloads Total size was 1,395 KiB
Large network payloads cost users real money and are highly correlated with long load times
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

Mobile Speed Score

Mobile Screenshot
Tap targets are not sized appropriately 96% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Estimated Input Latency 300 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
Largest Contentful Paint 8.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid serving legacy JavaScript to modern browsers Potential savings of 47 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Avoid an excessive DOM size 1,568 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First Contentful Paint (3G) 9791 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Reduce JavaScript execution time 4.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce the impact of third-party code Third-party code blocked the main thread for 1,080 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
Max Potential First Input Delay 700 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
Speed Index 7.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Cumulative Layout Shift 1.878
Cumulative Layout Shift measures the movement of visible elements within the viewport
Remove unused CSS Potential savings of 98 KiB
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
First Contentful Paint 5.0 s
First Contentful Paint marks the time at which the first text or image is painted
Links do not have descriptive text 13 links found
Descriptive link text helps search engines understand your content
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
First Meaningful Paint 6.7 s
First Meaningful Paint measures when the primary content of a page is visible
Minify JavaScript Potential savings of 10 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve static assets with an efficient cache policy 26 resources found
A long cache lifetime can speed up repeat visits to your page
Keep request counts low and transfer sizes small 211 requests • 1,294 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid chaining critical requests 5 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
Avoids enormous network payloads Total size was 1,294 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Initial server response time was short Root document took 460 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize main-thread work 10.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
First CPU Idle 13.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Remove unused JavaScript Potential savings of 271 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
Document uses legible font sizes 99.95% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Time to Interactive 15.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Eliminate render-blocking resources Potential savings of 450 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Total Blocking Time 2,720 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

squareup.com Alexa Rank

674

Global Rank

194

United States

Domain Available

Domain (TDL) and Typo Status
squareup.co Available Buy Now!
squareup.us Available Buy Now!
squareup.com Available Buy Now!
squareup.org Available Buy Now!
squareup.net Available Buy Now!
suareup.com Available Buy Now!
wquareup.com Available Buy Now!
xquareup.com Available Buy Now!

Information Server squareup.com

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 301 
date: Tue, 13 Apr 2021 21:01:04 GMT
content-type: text/html; charset=utf-8
location: https://squareup.com/us/en
cache-control: no-cache
x-request-id: a23de4c1-c036-427b-90ea-70c2a936d627
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
x-download-options: noopen
x-permitted-cross-domain-policies: none
x-square: S=awa788.sjc2b.square
strict-transport-security: max-age=631152000; includeSubDomains; preload
DNS Records DNS Resource Records associated with a hostname
squareup.com View DNS Records

Social Data