fitgirl.com website review

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

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

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

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

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

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

8 third-party services load with your homepage (Twitter, wheelio-app.com and Shopify and others), adding 486 KiB and 137 ms of main-thread time.

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

About 25 KiB of CSS is downloaded but never applied on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A woman on a beach stretching and doing the scorpion yoga p…”.

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

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

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 188 requests on a phone: images 1.0 MB (29), other files 792 KiB (106) and scripts 381 KiB (39). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example meal-plan-three-3-fit-girls-guide-fitgirls-fitgirlsguide-fgg at 600 px wide, shown at 174 px. Resized copies would save about 15 KiB.

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

10 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: 34 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 27 characters: “Fit Girls® 28 Day Jumpstart”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 33 pages on fitgirl.com and 6 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://www.fitgirls.com/collections/guides/products/fitgirlsguide-28dayjumpstart-bundle and https://www.fitgirls.com/products/fitgirlsguide-28dayjumpstart-bundle all use the title “Fit Girl's Guide - 28 Day Jumpstart - Bundle - Fit Girls®”, 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://www.fitgirls.com/collections/guides/products/fitgirlsguide-28dayjumpstart-bundle and https://www.fitgirls.com/products/fitgirlsguide-28dayjumpstart-bundle use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.fitgirls.com/collections/guides/products/fitgirlsguide-28dayjumpstart-bundle, whose canonical is https://www.fitgirls.com/products/fitgirlsguide-28dayjumpstart-bundle. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.fitgirls.com/pages/submit, https://www.fitgirls.com/pages/hiit, https://www.fitgirls.com/collections/guides/products/fitgirlsguide-28dayjumpstart-bundle, https://www.fitgirls.com/collections/guides/products/everything-bundle, https://www.fitgirls.com/collections/bundles and https://www.fitgirls.com/products/fitgirlsguide-28dayjumpstart-bundle 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 16 found) and read each the way a search engine does.

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

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.

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

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