verily.com website review

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Optanon and LinkedIn Ads and others), adding 3.7 MB and 170 ms of main-thread time.

vercel-storage.com costs a phone 0 ms of main-thread work and 3.4 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.

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

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

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

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need.

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.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 154 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 1.7 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 2.0 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 5.2 MB in 129 requests on a phone: media 3.3 MB (2), scripts 1.4 MB (98) and fonts 206 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 23 pages on verily.com and 7 external pages.

There is no https://verily.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://verily.com/privacy-policy, https://verily.com/terms, https://verily.com/responsible-supply-chain and https://verily.com/consumer-health-data-privacy-policy use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://verily.com/about-us/careers, whose canonical is https://verily.com/careers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://verily.com/accessibility, https://verily.com/privacy-policy, https://verily.com/terms and https://verily.com/consumer-health-data-privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

https://verily.com/accessibility, https://verily.com/privacy-policy, https://verily.com/terms, https://verily.com/responsible-supply-chain and https://verily.com/consumer-health-data-privacy-policy 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.

https://verily.com/newsroom took over 3 s to send its HTML from our server.

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

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

Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Tag Manager and LinkedIn Insight (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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