stxnext.com website review

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

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

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

Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (website-files.com, Google Tag Manager and Hubspot and others), adding 2.4 MB and 1.6 s of main-thread time.

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

website-files.com costs a phone 538 ms of main-thread work and 1.1 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 380 ms of main-thread work and 505 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Hubspot costs a phone 247 ms of main-thread work and 317 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 2,603 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

19 long tasks block the main thread while loading, the longest for 194 ms. During a long task the page ignores taps.

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

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

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

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

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

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

Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Scripts block taps and scrolling for 860 ms in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 29.4 MB in 108 requests on a phone: media 26.3 MB (7), scripts 2.0 MB (30) and images 688 KiB (42). Under 2 MB keeps phones on slow connections fast.

6a6487e133086439cff4ca3d_green-circle-glow.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 69 characters, so Google will cut it off around 60: “AI/ML, Data, and AI-Augmented Software Development Company | STX Next”.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 150 pages on stxnext.com and 11 external pages.

There is no https://www.stxnext.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.

robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

6 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

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

The homepage carries about 913 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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