ptpfit.ca website review

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and nfcube.com and others), adding 514 KiB and 246 ms of main-thread time.

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

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.

About 114 KiB of JavaScript is downloaded but never used on this page.

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

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 could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

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

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

The layout shifts by 0.158 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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 7.5 MB in 282 requests on a phone: images 5.9 MB (117), other files 635 KiB (66) and scripts 613 KiB (73). Under 2 MB keeps phones on slow connections fast.

4 images (1.4 MB) are 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.14 g of CO₂e: 256.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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: 2 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 431 pages on ptpfit.ca and 3 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://ptpfit.ca/pages/about-us, https://ptpfit.ca/blogs/articles, https://ptpfit.ca/collections/all-products, https://ptpfit.ca/collections/posture, https://ptpfit.ca/collections/main-sale and https://ptpfit.ca/collections/bodyweight and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://ptpfit.ca/pages/about-us, https://ptpfit.ca/blogs/articles, https://ptpfit.ca/collections/all-products, https://ptpfit.ca/collections/posture, https://ptpfit.ca/collections/main-sale and https://ptpfit.ca/collections/bodyweight and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://ptpfit.ca/collections/pilates, https://ptpfit.ca/collections/all-products, https://ptpfit.ca/collections/posture, https://ptpfit.ca/collections/brianna-throssell-x-bahe, https://ptpfit.ca/collections/bodyweight and https://ptpfit.ca/collections/cardio and 2 others 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.

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

27 of 69 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 “Invalid or unexpected token”.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.