cross.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 2.8 s

  2.8 s

  Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

• 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.

• Tap response (INP) held steady for real visitors

  0%

  Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 189 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Largest content (LCP) got 19% slower for real visitors

  +19%

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

• Page weight: 2.2 MB

  2.2 MB

  Your homepage downloads 2.2 MB on a phone, 247 KiB of it images (11%). Under 2 MB keeps phones on slow connections fast.

• About 0.6 g of CO₂ per visit

  0.61 g

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

• 7 tap targets too small

  7 tap targets are too small or too close together to hit reliably with a finger.

  Elements (3)

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (1)

• Malformed lists

  Some lists contain elements other than list items, which screen readers announce wrongly.

  Elements (1)

• All page content should be contained by landmarks (9 elements)

  All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• 1 form field without a label

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

  View source

• ARIA role should be appropriate for the element (8 elements)

  ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Title is short (22 characters)

  Your title is only 22 characters: “A.T. Cross Pen Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• Meta description is long (314 characters)

  Your meta description is 314 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• No social preview image

  No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  View source

• One H1 headline

  Your <h1> is empty.

• 159 internal links, 0 external

  The homepage links to 159 pages on cross.com and 0 external pages.

• 1 page without a meta description

  /pages/gift-sets has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 15 pages without an H1

  /pages/gift-sets, /collections/outlet, /collections/atx, /collections/bailey, /collections/bailey-light and /collections/calais and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 67 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”.

• Short HSTS lifetime

  HSTS is set, but max-age is 91 days; one year is the recommended minimum.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  cross.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  cross.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• No call to action on the first screen

  On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• Only about 53 words

  The homepage has only about 53 words of visible text; thin pages give Google and first-time buyers little to go on.

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• Email authentication score: 100/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 4 trackers load before any consent

  4

  Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

• 16 cookies set on arrival

  16

  Opening the homepage sets 16 cookies, 12 of them by other companies (measured from a US location before any click).

• No consent tool detected

  No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

• 33 other companies contacted

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