personalhour.com website review

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

14 images could be 758 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Shopify and others), adding 3.6 MB and 1.3 s of main-thread time.

YouTube costs a phone 462 ms of main-thread work and 1,018 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.

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

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

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

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

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

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

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

Google CDN costs a phone 157 ms of main-thread work and 298 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.

33 KiB could be saved by minifying JavaScript.

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

11 KiB could be saved by minifying CSS.

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 15.5 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.7 s. Good is under 3.8 s.

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

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

Real visitors wait 279 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 31.1 MB in 210 requests on a phone: media 26.2 MB (4), scripts 2.6 MB (87) and images 1.7 MB (29). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example 624e6f85-f1dd-4576-8a4b-64e82d5200e0.jpg at 3,168 px wide, shown at 90 px. Resized copies would save about 448 KiB.

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

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

9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

Headings skip levels (h2 → h5), 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 title is 85 characters, so Google will cut it off around 60: “PersonalHour®: Premium Pilates Reformers at Unmatched Value in the US – Personal Hour”.

There are 3 <h1> headlines (“”, “” and “PersonalHour®”). One clear main headline is easier for people and search engines.

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

The homepage links to 102 pages on personalhour.com and 7 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

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

https://personalhour.com/collections/all, https://personalhour.com/policies/shipping-policy, https://personalhour.com/collections/perfect-foldable-pilates-reformer-by-personalhour, https://personalhour.com/collections/personalhour-pilates-us-accessories, https://personalhour.com/pages/about-personalhour and https://personalhour.com/pages/faq and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://personalhour.com/collections/all, https://personalhour.com/collections/november-pilates-feast-sale, https://personalhour.com/collections/in-stock-pilates-reformers-ships-fast-from-the-us, https://personalhour.com/collections/perfect-foldable-pilates-reformer-by-personalhour, https://personalhour.com/collections/studio-pilates-reformer-bundle-deals and https://personalhour.com/collections/personalhour-pilates-us-accessories and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Criteo, FullStory, Google Ads, Google Analytics and Google Tag Manager and 4 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 17 cookies, 1 of them by other companies (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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.