vrchat.com website review

4 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

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

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

About 211 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

7 third-party services load with your homepage (Squarespace, Google Tag Manager and sqspcdn.com and others), adding 3.1 MB and 769 ms of main-thread time.

Your mobile performance score is 55 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

Squarespace costs a phone 658 ms of main-thread work and 1.3 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.

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.6 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 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

Desktop scores 81 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

3 KiB could be saved by minifying CSS.

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 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Explore thousands of worlds, meet people from everywhere, a…”.

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

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

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

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

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

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

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

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

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

3 images are downloaded at several times the size a phone draws them, for example BeWhoever.webp at 1,920 px wide, shown at 293 px. Resized copies would save about 554 KiB.

Your homepage downloads 3.3 MB in 69 requests on a phone: images 1.4 MB (6), scripts 1.3 MB (32) and stylesheets 257 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5f0770791aaf5731151…”.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 49 pages on vrchat.com and 63 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), 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://hello.vrchat.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.

https://hello.vrchat.com/careers and https://hello.vrchat.com/about all use the title “Careers — VRChat”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://hello.vrchat.com/careers, https://hello.vrchat.com/press, https://hello.vrchat.com/avatar-systems, https://hello.vrchat.com/avatar-marketplace, https://hello.vrchat.com/developer-faq and https://hello.vrchat.com/community-guidelines and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

https://hello.vrchat.com/careers, https://hello.vrchat.com/avatar-marketplace, https://hello.vrchat.com/community-guidelines, https://hello.vrchat.com/video-content-guidelines, https://hello.vrchat.com/community-faq and https://hello.vrchat.com/vrchatplus and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://hello.vrchat.com/community-guidelines, https://hello.vrchat.com/video-content-guidelines, https://hello.vrchat.com/community-faq and https://hello.vrchat.com/community 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.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/5f0770791aaf57311515b23d/296/5c5…”.

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

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

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

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

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (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 2 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.