x.com website review

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

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

1 third-party service load with your homepage (Twitter), adding 142 KiB and 0 ms of main-thread time.

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

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 wait 7.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Your title is only 28 characters: “X. It’s what’s happening / X”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“Happening now.” and “See what’s happening”). One clear main headline is easier for people and search engines.

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

The homepage links to 9 pages on x.com and 12 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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.

There is no https://x.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 GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://x.com/i/jf/onboarding/web is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://x.com/i/jf/onboarding/web has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://x.com/tos, whose canonical is https://x.com/en/tos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://x.com/i/jf/onboarding/web has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.