twitch.tv website review

92 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

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

69 images could be 561 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

About 151 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

The page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.

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

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

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

3 third-party services load with your homepage (twitchcdn.net, Branch Metrics and jtvnw.net), adding 1.2 MB and 42 ms of main-thread time.

jtvnw.net costs a phone 0 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.

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

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 2.1 MB in 158 requests on a phone: images 1.1 MB (89), scripts 844 KiB (46) and fonts 123 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

8 elements hidden from screen readers can still receive keyboard focus.

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

48 visible links have no text or label, so screen readers cannot say where they go.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 6 characters: “Twitch”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

A phone browser shows 831 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

Large scripts ship without source maps.

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.

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

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 831 words of visible text.

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