Website review, no card needed

arcxis.com logo

arcxis.com website review

Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 84 checks

This review found 38 issues worth fixing on arcxis.com, 11 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.4 s1.3 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.5 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20261.9 s
Jul 18, 20261.8 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
92 ms67 msMay 9Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202671 ms
May 16, 202670 ms
May 23, 202675 ms
May 30, 202679 ms
Jun 6, 202677 ms
Jun 20, 202686 ms
Jul 4, 202688 ms
Jul 11, 202688 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 202687 ms
Aug 22, 202688 ms
Aug 29, 202688 ms
Sep 5, 202689 ms
Sep 12, 202685 ms
Sep 19, 202687 ms
Sep 26, 202686 ms
Oct 3, 202686 ms
Oct 10, 202687 ms
Oct 17, 202686 ms
Oct 24, 202687 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of arcxis.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. arcxis.com at 0.4 s0.4 s
  2. arcxis.com at 0.8 s0.8 s
  3. arcxis.com at 1.1 s1.1 s
  4. arcxis.com at 1.5 s1.5 s
  5. arcxis.com at 1.9 s1.9 s
  6. arcxis.com at 2.3 s2.3 s
  7. arcxis.com at 2.6 s2.6 s
  8. arcxis.com at 3.0 s3.0 s

Speed

10 to fix66
  • Render-blocking requests

    2.1 s

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.

  • Reduce unused JavaScript

    1.3 s · 233 KiB

    About 233 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.

  • audioeye.com adds 1.0 s

    1.0 s

    audioeye.com costs a phone 1.0 s of main-thread work and 298 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Improve image delivery

    150 ms · 1.6 MB

    11 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    900 ms · 401 KiB

    46 files are served with short cache lifetimes, so returning visitors download them again (401 KiB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye.com, Hubspot and Google Tag Manager and others), adding 875 KiB and 1.2 s of main-thread time.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    450 ms · 44 KiB

    About 44 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Minify JavaScript

    300 ms · 42 KiB

    42 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.1 s

    A phone's processor spends 2.1 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 12.1 s

    12.1 s

    Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WE'RE WITH YOU AT EACH CRITICAL STAGE OF YOUR BUILD.”.

  • Time to Interactive: 12.3 s

    12.3 s

    The page becomes fully interactive after 12.3 s. Good is under 3.8 s.

  • Speed Index: 7.3 s

    7.3 s

    Visually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.

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

    +23%

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

  • First Contentful Paint: 2.2 s

    2.2 s

    The first text or image appears after 2.2 s on a phone. Good is under 1.8 s.

  • 12 images without width and height

    12 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    +3%

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

5 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0.023

    0.023

    The layout barely moves while loading (CLS 0.023, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix33
  • 1 image over 500 KB

    640e6d6d3d7c296f61486085_RESNET-HERS-H2O-Logo-RGB-Web-Use-2. weighs 658 KiB. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    1.0 MB

    7 images are downloaded at several times the size a phone draws them, for example 640e6d6d3d7c296f61486085_RESNET-HERS-H2O-Logo-RGB-Web-Use-2. at 9,043 px wide, shown at 165 px. Resized copies would save about 1.0 MB.

  • Page weight: 3.5 MB in 79 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 79 requests on a phone: images 2.3 MB (18), scripts 778 KiB (29) and fonts 352 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (1.8 MB) 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.

  • 5 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.99 g

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

Accessibility

6 to fixGoogle 9092
  • 37 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9291
  • No structured data

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

  • No social preview image

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

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 46 internal links, 80 external

    The homepage links to 46 pages on arcxis.com and 80 external pages.

6 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “ARCXIS is the nation's leading provider of inspection, engineering, and risk management services for residential builde…”.

  • One H1 headline

    Your main headline reads: “We're with you at each critical stage of your build.”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Engineering, Inspections & Energy Compliance Services | ARCXIS”.

  • Canonical URL set

    The canonical URL is https://arcxis.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://arcxis.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://arcxis.com/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (864 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 3 pages share a meta description

    https://arcxis.com/inspection-services, https://arcxis.com/utility-rebates-arcxis and https://arcxis.com/high-performance-certification-programs-arcxis use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://arcxis.com/private-provider-services has 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 25 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://wsv3cdn.audioeye.com/static-scripts/v2/2026-10-30/compliance.css' from origin 'htt…”.

2 checks passed
  • Tap targets are thumb-sized

    12 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • 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: 9 customer or partner logos. 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 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 548 words of copy

    The homepage carries about 548 words of visible text.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “learn more” and “LEARN MORE”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 19 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at arcxis.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
HubSpot

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on arcxis.com, including 16 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25