1x.tech website review

1 image could be 551 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Stripe and Facebook and others), adding 1.2 MB and 1.0 s of main-thread time.

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

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

Google Tag Manager costs a phone 437 ms of main-thread work and 304 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.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

Stripe costs a phone 234 ms of main-thread work and 297 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.

Google Maps costs a phone 153 ms of main-thread work and 393 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.

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

Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

About 20 KiB of CSS is downloaded but never applied on this page.

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.

Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEO”.

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

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

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

Real visitors wait 405 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

Your homepage downloads 6.1 MB in 100 requests on a phone: scripts 2.5 MB (46), other files 1.6 MB (38) and images 1.5 MB (8). Under 2 MB keeps phones on slow connections fast.

image weighs 716 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example image at 3,813 px wide, shown at 390 px. Resized copies would save about 838 KiB.

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

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

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

Your title is only 16 characters: “1X | Home Robots”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“NEOHome Robot” and “ExperienceNEO”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.1x.tech/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at 1x.tech/robots.txt, the first file search crawlers ask for.

The homepage links to 27 pages on 1x.tech and 5 external pages.

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.

Your homepage links to /terms-and-conditions, which answers with an error. Visitors hit a dead end and search engines drop it.

/ai, /manufacturing, /discover, /logs, /privacy-policy and /get-updates and 1 other use the same meta description. A description written for each page earns more clicks.

/discover, /robot-fleet, /logs, /support and /investor-relations have no <h1> headline, so visitors and search engines get no clear main topic.

/robot-fleet, /logs, /support, /get-updates and /investor-relations 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.

/get-updates took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

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

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

1 link from your homepage to your own site is broken, for example https://www.1x.tech/terms-and-conditions (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

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

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.

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

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

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.

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