Website review, no card needed

bodyglove.com logo

bodyglove.com website review

Visit site (opens in a new tab)Reviewed 18 October 202653 issues · 98 checks

This review found 53 issues worth fixing on bodyglove.com, 23 of them high impact, across 98 checks. The most urgent: reduce unused JavaScript. 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
1.7 s1.4 sApr 25Oct 101.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.6 s
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
235 ms185 msApr 25Oct 10228 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026195 ms
May 2, 2026196 ms
May 9, 2026195 ms
May 16, 2026195 ms
May 23, 2026192 ms
May 30, 2026191 ms
Jun 6, 2026195 ms
Jun 13, 2026202 ms
Jun 20, 2026204 ms
Jun 27, 2026205 ms
Jul 4, 2026209 ms
Jul 11, 2026205 ms
Jul 18, 2026204 ms
Jul 25, 2026204 ms
Aug 1, 2026203 ms
Aug 8, 2026203 ms
Aug 15, 2026204 ms
Aug 22, 2026205 ms
Aug 29, 2026213 ms
Sep 5, 2026220 ms
Sep 12, 2026224 ms
Sep 19, 2026229 ms
Sep 26, 2026229 ms
Oct 3, 2026228 ms
Oct 10, 2026228 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 bodyglove.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bodyglove.com at 1.2 s1.2 s
  2. bodyglove.com at 2.5 s2.5 s
  3. bodyglove.com at 3.7 s3.7 s
  4. bodyglove.com at 4.9 s4.9 s
  5. bodyglove.com at 6.2 s6.2 s
  6. bodyglove.com at 7.4 s7.4 s
  7. bodyglove.com at 8.6 s8.6 s
  8. bodyglove.com at 9.8 s9.8 s

Speed

17 to fix32
  • Reduce unused JavaScript

    2.9 s · 2.8 MB

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

  • Improve image delivery

    3.8 s · 758 KiB

    7 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 3.8 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Minify JavaScript

    1.1 s · 243 KiB

    243 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 32

    32/100

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

  • Main-thread work: 8.3 s

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

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    800 ms · 902 KiB

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

  • YouTube adds 780 ms

    780 ms

    YouTube costs a phone 780 ms of main-thread work and 2.0 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.

  • Legacy JavaScript

    650 ms · 183 KiB

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

  • Reduce unused CSS

    450 ms · 216 KiB

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

  • Google Tag Manager adds 445 ms

    445 ms

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

  • Shopify adds 246 ms

    246 ms

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

  • rokt.com adds 237 ms

    237 ms

    rokt.com costs a phone 237 ms of main-thread work and 496 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.

  • 2,769 HTML elements

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

  • 20 long tasks on the main thread

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

  • Klaviyo adds 139 ms

    139 ms

    Klaviyo costs a phone 139 ms of main-thread work and 370 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.

  • Minify CSS

    150 ms · 12 KiB

    12 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

  • 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: 13 ms

    13 ms

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

Core Web Vitals

9 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.

  • Largest Contentful Paint: 25.0 s

    25.0 s

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

  • Speed Index: 23.7 s

    23.7 s

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

  • Time to Interactive: 58.0 s

    58.0 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Total Blocking Time: 973 ms

    973 ms

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 259 ms

    259 ms

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

  • Cumulative Layout Shift: 0.123

    0.123

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

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

    +17%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

3 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.

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 591 ms

    591 ms

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

Images and page weight

3 to fix45
  • Page weight: 9.9 MB in 562 requests

    9.9 MB

    Your homepage downloads 9.9 MB in 562 requests on a phone: scripts 6.2 MB (181), images 1.9 MB (87) and other files 962 KiB (239). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    BG-Retro_85_Wetsuit-Homepage-Banner-MBL_21a4f65c-65d1-4ab3-b weighs 720 KiB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (799 KiB) 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.

  • About 2.8 g of CO₂ per visit

    2.80 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fixGoogle 7886
  • Invalid ARIA attributes

    26 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must be contained by particular parents (5 elements)

    Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • 8 tap targets too small

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

  • 3 links without text

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

  • 2 form fields without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (9 elements).

2 checks passed
  • Every image has alt text

    All 169 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 9280
  • No H1 headline

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

  • Meta description is long (238 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.bodyglove.com/search?q={search_term_string}")”.

  • 2 links crawlers can't follow

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

  • 339 internal links, 12 external

    The homepage links to 339 pages on bodyglove.com and 12 external pages.

5 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Wetsuits, Swimwear, & Surf Gear | Body Glove”.

  • Canonical URL set

    The canonical URL is https://www.bodyglove.com/.

  • 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://www.bodyglove.com/sitemap.xml.

AI search readiness

100
4 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 (925 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.bodyglove.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.bodyglove.com/pages/fit-guide-landing-page has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.bodyglove.com/pages/womens, https://www.bodyglove.com/pages/fit-guide-landing-page, https://www.bodyglove.com/pages/mens, https://www.bodyglove.com/pages/kids and https://www.bodyglove.com/pages/wetsuits have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5474
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56348427&Ver=2&mid=b3ac9c0a-cc8b-488b-b6cd-aa53778ff9c8&bo=1&sid=1aea69a0ca9811f1bff543a9e01dd7e8&vid=1aea5880ca9811f18b0ac1082388bff3&vids=1&msclkid=N&pi=918639831&lg.

  • 7 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “DISCOUNT_AMOUNT is not defined”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    39 of 44 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

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

  • 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 324 words of copy

    The homepage carries about 324 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN THE CREW - SIGN UP & SAVE 15%”.

  • 26 calls to action

    The homepage has 26 calls to action, for example “JOIN THE CREW - SIGN UP & SAVE 15%”, “Shop All” and “Shop by Bottoms”.

  • 8 short forms

    8 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 11 trackers load before any consent

    11

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 6 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.

  • 30 cookies set on arrival

    30

    Opening the homepage sets 30 cookies, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 68 other companies contacted

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

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 bodyglove.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity

Company

Founded
1953
Headquarters
Redondo Beach

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on bodyglove.com, including 26 speed issues, 4 SEO issues and 2 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