physiotru.com website review

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

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

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

8 third-party services load with your homepage (cloudfront.net, Attentive and Shopify and others), adding 2.2 MB and 622 ms of main-thread time.

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

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

About 70 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

cloudfront.net costs a phone 161 ms of main-thread work and 606 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.

Attentive costs a phone 131 ms of main-thread work and 628 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.

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

Shopify costs a phone 105 ms of main-thread work and 459 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.

20 KiB could be saved by minifying JavaScript.

9 long tasks block the main thread while loading, the longest for 92 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).

Polyfills for old browsers add 26 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.

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

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

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

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

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

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 117 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 2.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.2 MB in 381 requests on a phone: media 3.5 MB (2), images 2.0 MB (41) and scripts 1.9 MB (107). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example PDPCollagen.png at 1,365 px wide, shown at 64 px. Resized copies would save about 168 KiB.

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

1 image (82 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.

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

3 images have no alt text, which hurts accessibility and image search.

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

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

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

Your <h1> is empty.

The homepage links to 57 pages on physiotru.com and 2 external pages.

The HTML your server sends has 1,022 of the 1,773 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your homepage links to https://physiotru.com/products/physiopulse and https://physiotru.com/products/physiovision, which answer with an error. Visitors hit a dead end and search engines drop them.

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

/ and https://physiotru.com/tools/recurring/get-subscription-access all use the title “PhysioTru”, 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://physiotru.com/products/physio-complete, https://physiotru.com/pages/about-us, https://physiotru.com/blogs/healthy-living, https://physiotru.com/pages/reviews, https://physiotru.com/tools/recurring/get-subscription-access and https://physiotru.com/collections/best-sellers and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://physiotru.com/products/physio-fit and https://physiotru.com/products/physiofit use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://physiotru.com/products/physiofit, whose canonical is https://physiotru.com/products/physio-fit. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://physiotru.com/pages/reviews, https://physiotru.com/collections/best-sellers and https://physiotru.com/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

https://physiotru.com/products/physio-fit, https://physiotru.com/products/physiocollagen, https://physiotru.com/products/physio-flora and https://physiotru.com/blogs/healthy-living took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97093822&Ver=2&mid=18f8f3e4-06eb-460f-bcfc-397b6b89ba7c&bo=1&sid=a7413b80daef11f1bfb46fb4f8f8980f&vid=a7414b60daef11f1acea49265cac4e5f&vids=1&msclkid=N&pi=918639831&lg.

5 of 15 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 “Failed to load resource: net::ERR_FAILED”.

The homepage carries about 1,773 words of visible text.

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