bodyprecision.com website review

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

Squarespace costs a phone 1.3 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 4.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

6 third-party services load with your homepage (Squarespace, flodesk.com and sqspcdn.com and others), adding 2.2 MB and 1.5 s of main-thread time.

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

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

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

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

flodesk.com costs a phone 174 ms of main-thread work and 434 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.

squarespace-cdn.com costs a phone 0 ms of main-thread work and 334 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.

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

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

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

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

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.

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

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

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

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

Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Discover Pilates, Change Your Life Pilates Excellence Start…”. Most of its time is element render delay (2.4 s).

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

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.3 MB in 92 requests on a phone: scripts 1.3 MB (50), fonts 403 KiB (14) and images 317 KiB (5). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (177 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 0.66 g of CO₂e: 78.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h1 → h4), 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 14 characters: “Body Precision”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 7 <h1> headlines (““Pilates is complete coordination of body, mind a…”, “•” and “"Change happens through movement and movement hea…”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/653926fa120f7f089b2…”.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 51 pages on bodyprecision.com and 6 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), 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.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/our-studio and /about all use the title “Our Studio — Body Precision”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/new-to-body-precision, /our-studio, /our-owner, /our-teachers, /private-sessions and /classes and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /about, whose canonical is /our-studio. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/653926fa120f7f089b290fa3/53/5c5a…”.

http://bodyprecision.com does not redirect to https, so some visitors land on the insecure version.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

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.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

bodyprecision.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

bodyprecision.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no form on the homepage, so every lead has to click through to another page first.

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

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

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

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

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