squareup.com website review

Not measured in this review.

• Real-user FCP: 2.2 s

  2.2 s

  Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 1.5 s

  1.5 s

  Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

• Largest content (LCP) held steady for real visitors

  -1%

  Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• 5 images below the first screen load straight away

  5 images further down the page (123 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• About 0.4 g of CO₂ per visit

  0.44 g

  By the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 53.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

• Certain ARIA roles must be contained by particular parents (4 elements)

  Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

  Elements (3)

• ARIA attributes must conform to valid values (1 element)

  ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 6 text elements with low contrast

  6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (3)

• Interactive controls must not be nested (4 elements)

  Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• Form elements should have a visible label (1 element)

  Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  Elements (2)

• 4 links without text

  4 visible links have no text or label, so screen readers cannot say where they go.

• 1 form field without a label

  1 form field has no label, so screen readers announce an empty box and autofill guesses.

• Headings skip levels

  Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

  Elements (1)

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• 354 internal links, 20 external

  The homepage links to 354 pages on squareup.com and 20 external pages.

• No Organization structured data

  There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

• 12 pages without a title

  /us/en/restaurants, /us/en/restaurants/coffee-shop, /us/en/restaurants/quick-service, /us/en/restaurants/full-service, /us/en/restaurants/bars and /us/en/restaurants/food-truck and 6 others have no <title>, so Google invents the link text in results.

  Elements (8)

• 12 pages without a meta description

  /us/en/restaurants, /us/en/restaurants/coffee-shop, /us/en/restaurants/quick-service, /us/en/restaurants/full-service, /us/en/restaurants/bars and /us/en/restaurants/food-truck and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 15 pages without an H1

  /us/en/restaurants, /us/en/restaurants/switch-to-square, /us/en/restaurants/coffee-shop, /us/en/restaurants/quick-service, /us/en/restaurants/drive-thru and /us/en/restaurants/full-service and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 2 pages with very little text

  /us/en/restaurants/switch-to-square and /us/en/restaurants/capabilities have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 123 found) and read each the way a search engine does.

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• Local business without LocalBusiness data

  Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

• Thin social proof

  Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• Phone number is not tap-to-call

  Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• About 711 words of copy

  The homepage carries about 711 words of visible text.

• 1 tracker load before any consent

  1

  Before a visitor clicks anything, the page loads Google Analytics (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

• 31 cookies set on arrival

  31

  Opening the homepage sets 31 cookies (measured from a US location before any click).

• 15 other companies contacted

  Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.