Website review, no card needed

poundfit.com logo

poundfit.com website review

Visit site (opens in a new tab)Reviewed 31 October 202641 issues · 79 checks

This review found 41 issues worth fixing on poundfit.com, 19 of them high impact, across 79 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.5 s5.3 sMay 9Oct 246.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.6 s
May 16, 20265.6 s
May 23, 20265.7 s
May 30, 20265.7 s
Jun 6, 20265.7 s
Jun 13, 20265.6 s
Jun 20, 20265.5 s
Jun 27, 20265.5 s
Jul 4, 20265.4 s
Jul 11, 20265.4 s
Jul 18, 20265.4 s
Jul 25, 20265.5 s
Aug 1, 20265.5 s
Aug 8, 20265.5 s
Aug 15, 20265.5 s
Aug 22, 20265.5 s
Aug 29, 20265.5 s
Sep 5, 20265.7 s
Sep 12, 20265.8 s
Sep 19, 20266.0 s
Sep 26, 20266.1 s
Oct 3, 20266.2 s
Oct 10, 20266.1 s
Oct 17, 20266.2 s
Oct 24, 20266.3 s
Real-visitor tap response (INP)75th percentile, phones
227 ms165 msMay 9Oct 24220 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026172 ms
May 16, 2026172 ms
May 23, 2026172 ms
May 30, 2026173 ms
Jun 6, 2026172 ms
Jun 13, 2026174 ms
Jun 20, 2026175 ms
Jun 27, 2026178 ms
Jul 4, 2026179 ms
Jul 11, 2026176 ms
Jul 18, 2026175 ms
Jul 25, 2026179 ms
Aug 1, 2026187 ms
Aug 8, 2026195 ms
Aug 15, 2026203 ms
Aug 22, 2026200 ms
Aug 29, 2026202 ms
Sep 5, 2026198 ms
Sep 12, 2026197 ms
Sep 19, 2026201 ms
Sep 26, 2026203 ms
Oct 3, 2026207 ms
Oct 10, 2026211 ms
Oct 17, 2026219 ms
Oct 24, 2026220 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of poundfit.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. poundfit.com at 0.8 s0.8 s
  2. poundfit.com at 1.6 s1.6 s
  3. poundfit.com at 2.4 s2.4 s
  4. poundfit.com at 3.2 s3.2 s
  5. poundfit.com at 4.1 s4.1 s
  6. poundfit.com at 4.9 s4.9 s
  7. poundfit.com at 5.7 s5.7 s
  8. poundfit.com at 6.5 s6.5 s

Speed

8 to fix56
  • Improve image delivery

    25.7 s · 20.4 MB

    13 images could be 20.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 25.7 s faster on a phone.

  • Render-blocking requests

    4.3 s

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

  • Main-thread work: 4.4 s

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

  • Mobile performance score: 56

    56/100

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

  • Reduce unused CSS

    750 ms · 163 KiB

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

  • Use efficient cache lifetimes

    425 KiB

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

  • Reduce unused JavaScript

    266 KiB

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

  • 2,264 HTML elements

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

  • Font display

    150 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (cdn-cookieyes.com, jQuery CDN and WordPress and others), adding 59 KiB and 107 ms of main-thread time.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    19 KiB

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

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 23 ms

    23 ms

    Your server sent the HTML in 23 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 35.1 s

    35.1 s

    Your largest element takes 35.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NO REPS, JUST RHYTHM. Grab the beat and leave the rest on t…”.

  • Time to Interactive: 36.5 s

    36.5 s

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

  • Speed Index: 7.7 s

    7.7 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user INP: 243 ms

    243 ms

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

  • Tap response (INP) got 28% slower for real visitors

    +28%

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

  • Cumulative Layout Shift: 0.114

    0.114

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

  • 6 images without width and height

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

2 checks passed
  • Real-user CLS: 0.06

    0.06

    For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 142 ms

    142 ms

    Scripts block the page for only 142 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix28
  • Page weight: 22.9 MB in 207 requests

    22.9 MB

    Your homepage downloads 22.9 MB in 207 requests on a phone: images 21.3 MB (19), scripts 678 KiB (89) and fonts 584 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    POUND-Header_Become_an_instructor_1080x1320-601x735.png weighs 676 KiB. On a phone connection a single image that size takes seconds.

  • 8 images below the first screen load straight away

    8 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

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

  • 3 images far larger than shown

    287 KiB

    3 images are downloaded at several times the size a phone draws them, for example 863282022_18634385668056585_1273334469699737473_nfull.webp at 640 px wide, shown at 61 px. Resized copies would save about 287 KiB.

  • About 6.5 g of CO₂ per visit

    6.49 g

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

Accessibility

6 to fixGoogle 9792
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (4 elements)

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

  • Page should contain a level-one heading (1 element)

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

  • 8 links without text

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

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8575
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (26 characters)

    Your title is only 26 characters: “POUND - Rockout. Workout.®”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (327 characters)

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

  • 3 links with vague text

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 72 internal links, 43 external

    The homepage links to 72 pages on poundfit.com and 43 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://poundfit.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://poundfit.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://poundfit.com/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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (680 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://poundfit.com/.

  • 5 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

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

  • Thin social proof

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

  • No direct contact details

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 501 words of copy

    The homepage carries about 501 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop”, “Shop All” and “Learn More”.

  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • 8 other companies contacted

    Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at poundfit.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on poundfit.com, including 20 speed issues, 5 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25