hellotoa.com website review

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

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

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

8 third-party services load with your homepage (gotolstoy.com, Klaviyo and Shopify and others), adding 1.6 MB and 711 ms of main-thread time.

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

10 images could be 314 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Shopify costs a phone 193 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.

gotolstoy.com costs a phone 280 ms of main-thread work and 157 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.

Klaviyo costs a phone 218 ms of main-thread work and 329 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.

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

About 50 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.

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

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

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

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

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 JavaScript is shipped twice across bundles.

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

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

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

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

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

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

Your homepage downloads 4.1 MB in 349 requests on a phone: images 1.6 MB (55), other files 1.2 MB (140) and scripts 912 KiB (111). Under 2 MB keeps phones on slow connections fast.

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

22 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: 9 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

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

Your title is 87 characters, so Google will cut it off around 60: “Taste of Awesomeness — Fruit Teas, Prebiotic Juices and Loose Leaf Tea – Known Stranger”.

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

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

Your <h1> is empty.

The homepage links to 248 pages on hellotoa.com and 3 external pages.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/collections/all-products, /collections/coconut-milk, /collections/sparkling, /collections/fruit-tea-brew, /collections/tea-bags and /pages/wholesale and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all-products, /collections/black-friday, /collections/coconut-milk, /collections/sparkling, /collections/fruit-tea-brew and /collections/tea-bags and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Error: AbortError: signal is aborted without reason”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.knownstranger.com.au/customer_authentication/redirect?locale=en&region_country=AU.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to 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.

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 2,183 words of visible text.

DMARC is set to p=none, so mail pretending to be hellotoa.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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