labs.google website review

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

13 images could be 944 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

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

4 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Fonts and others), adding 489 KiB and 325 ms of main-thread time.

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

Desktop scores 83 but mobile only 57. 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.

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 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Google Flow Music”.

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

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

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

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

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

Real visitors see the first content after 2.1 s (75th percentile). 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 460 ms to 447 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 105.2 MB in 62 requests on a phone: media 102.6 MB (24), images 1.5 MB (23) and scripts 932 KiB (4). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example playground-featured-hero-mobile.webp at 1,280 px wide, shown at 390 px. Resized copies would save about 360 KiB.

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

Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 13 pages on labs.google and 31 external pages.

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://labs.google/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://labs.google/playwithputty and https://labs.google/fx/tools/flow have no <h1> headline, so visitors and search engines get no clear main topic.

https://labs.google/fx/tools/flow has 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 8 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

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

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