tonaactive.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Shopify and others), adding 661 KiB and 833 ms of main-thread time.

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

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

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

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

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

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

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

6 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FROM THE FOUNDING DESIGNER FOR LULULEMON”.

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

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

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

Scripts block taps and scrolling for 500 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' tap response (inp) went from 112 ms to 101 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.4 MB in 201 requests on a phone: other files 854 KiB (116), scripts 838 KiB (49) and images 539 KiB (19). Under 2 MB keeps phones on slow connections fast.

1 image (42 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (42 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.68 g of CO₂e: 82.2 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.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

There are 3 <h1> headlines (“FROM THE FOUNDING DESIGNER FOR LULULEMON”, “So THIS Is how workout leggings are supposed to f…” and “"NEW LEGGINGS RARELY LIVE UP TO THE HYPE - THESE …”). One clear main headline is easier for people and search engines.

The homepage links to 105 pages on tonaactive.com and 8 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.

https://tonaactive.com/products/the-tonalift-leggings is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://tonaactive.com/pages/how-is-tona-different and https://tonaactive.com/pages/how-tona-is-different all use the title “How Are TONA Leggings Different? – TONA Activewear”. Search engines can't tell which page to show for a search, so each competes with the others.

https://tonaactive.com/pages/how-is-tona-different, https://tonaactive.com/pages/manifesto, https://tonaactive.com/pages/our-mission, https://tonaactive.com/pages/pfas-free-fabric, https://tonaactive.com/pages/faq and https://tonaactive.com/pages/how-tona-is-different and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

https://tonaactive.com/pages/how-tona-is-different took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://tonaactive.com/.

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

5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://tonaactive.com/cdn/shop/t/144/assets/testimonial-cards.css?v=23833' because its MI…”.

1 image is served at too low a resolution for sharp phone screens.

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

The homepage carries about 522 words of visible text.

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