arcsolinc.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 FCP: 3.1 s

  3.1 s

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

• Real-user TTFB: 2.0 s

  2.0 s

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

• Real-user LCP: 3.6 s

  3.6 s

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

• Tap response (INP) got 16% slower for real visitors

  +16%

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

• Largest content (LCP) held steady for real visitors

  +5%

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

• Page weight: 6.9 MB

  6.9 MB

  Your homepage downloads 6.9 MB on a phone, 5.2 MB of it images (74%). Under 2 MB keeps phones on slow connections fast.

• 4 images in older formats

  4 images (739 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  Elements (4)

• 3 images far larger than shown

  315 KiB

  3 images are downloaded at several times the size a phone draws them, for example image_2021-11-02_090641.png at 1,158 px wide, shown at 360 px. Resized copies would save about 315 KiB.

  Elements (3)

• 3 images below the first screen load straight away

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

  Elements (3)

• About 2.0 g of CO₂ per visit

  1.97 g

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

• 1 button without a name

  1 button has no accessible name, so screen readers announce just “button”.

  Elements (1)

• 13 text elements with low contrast

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

  Elements (3)

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

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

  Elements (3)

• Document should not have more than one banner landmark (1 element)

  Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• No main landmark

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

  Elements (1)

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

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

  Elements (1)

• Headings skip levels

  Headings skip levels (h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

  View sourceElements (2)

• No social preview image

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

  View source

• 38 internal links, 15 external

  The homepage links to 38 pages on arcsolinc.com and 15 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.

  View source

• No llms.txt

  There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

• 3 pages slow to respond

  /cutting-automation/hypertherm-plasma-cutting, /about and /about/about-us took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

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

  View source

• Thin social proof

  Social proof on the homepage: 43 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

• No opening hours

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

• No form on the homepage

  There is no form on the homepage, so every lead has to click through to another page first.

• No map or directions link

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

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

• About 474 words of copy

  The homepage carries about 474 words of visible text.

• 4 trackers load before any consent

  4

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

• 5 cookies set on arrival

  5

  Opening the homepage sets 5 cookies (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.

• 10 other companies contacted

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