Website review, no card needed

williamsathleticclub.com logo

williamsathleticclub.com website review

Visit site (opens in a new tab)Reviewed 6 November 202640 issues · 80 checks

This review found 40 issues worth fixing on williamsathleticclub.com, 12 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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
2.3 s1.2 sJul 4Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.6 s
Aug 15, 20261.4 s
Aug 29, 20261.4 s
Sep 19, 20261.7 s
Sep 26, 20262.0 s
Oct 3, 20262.2 s
Oct 24, 20261.8 s
Oct 31, 20261.7 s

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 williamsathleticclub.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. williamsathleticclub.com at 0.6 s0.6 s
  2. williamsathleticclub.com at 1.2 s1.2 s
  3. williamsathleticclub.com at 1.7 s1.7 s
  4. williamsathleticclub.com at 2.3 s2.3 s
  5. williamsathleticclub.com at 2.9 s2.9 s
  6. williamsathleticclub.com at 3.5 s3.5 s
  7. williamsathleticclub.com at 4.1 s4.1 s
  8. williamsathleticclub.com at 4.7 s4.7 s

Speed

8 to fix62
  • Use efficient cache lifetimes

    2.4 s · 246 KiB

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

  • Improve image delivery

    1.1 s · 934 KiB

    11 images could be 934 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.

  • Reduce unused JavaScript

    1.4 s · 270 KiB

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

  • Mobile performance score: 62

    62/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Facebook and Klaviyo and others), adding 1.0 MB and 823 ms of main-thread time.

  • Shopify adds 276 ms

    276 ms

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

  • Main-thread work: 2.6 s

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

  • Klaviyo adds 175 ms

    175 ms

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

  • Reduce unused CSS

    280 ms · 10 KiB

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

  • Legacy JavaScript

    150 ms · 42 KiB

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

  • 5 long tasks on the main thread

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 13.9 s

    13.9 s

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

  • Time to Interactive: 14.1 s

    14.1 s

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

  • Speed Index: 7.9 s

    7.9 s

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

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

    +25%

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

  • Total Blocking Time: 233 ms

    233 ms

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

  • 1 image without width and height

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 521 ms

    521 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 3.2 MB in 274 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 274 requests on a phone: scripts 1.1 MB (91), images 1.1 MB (20) and other files 867 KiB (134). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    262 KiB

    5 images are downloaded at several times the size a phone draws them, for example RACHEL_CASHMERE-GREY-F_882939de-db1e-4741-85b7-4645c709ae04. at 900 px wide, shown at 191 px. Resized copies would save about 262 KiB.

  • 2 images in older formats

    2 images (233 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 0.9 g of CO₂ per visit

    0.91 g

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

1 checks passed
  • Images load when needed

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

Accessibility

10 to fixGoogle 9387
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 2 tap targets too small

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

  • 2 images without alt text

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

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

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

  • 17 links without text

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

  • 1 form field without a label

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

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is short (22 characters)

    Your title is only 22 characters: “Williams Athletic Club”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is long (313 characters)

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

  • 43 internal links, 4 external

    The homepage links to 43 pages on williamsathleticclub.com and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Redefined Women's Sportswear”.

  • Canonical URL set

    The canonical URL is https://williamsathleticclub.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://williamsathleticclub.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 10 pages without a meta description

    https://williamsathleticclub.com/collections/d2c-new-arrivals, https://williamsathleticclub.com/collections/shop-all, https://williamsathleticclub.com/collections/the-plaid-edit-fa26, https://williamsathleticclub.com/collections/cobalt, https://williamsathleticclub.com/collections/the-tennis-edit and https://williamsathleticclub.com/collections/d2c-heritage-knits and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://williamsathleticclub.com/collections/d2c-new-arrivals, https://williamsathleticclub.com/collections/shop-all, https://williamsathleticclub.com/collections/the-plaid-edit-fa26, https://williamsathleticclub.com/collections/the-golf-travel-edit, https://williamsathleticclub.com/collections/the-modern-club-wardrobe and https://williamsathleticclub.com/collections/the-new-golf-uniform and 5 others 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 35 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

2 to fixGoogle 9687
  • 40 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix57
  • 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 analytics detected

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

  • A 12-field form

    Your longest form asks for 12 fields (0 required). Every extra field lowers completion.

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

  • Only about 71 words

    The homepage has only about 71 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join The Club” and “Signup”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Signup”, “Shop All” and “Join The Club”.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies, 2 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.

  • 42 other companies contacted

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

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Littledata The Data Layer · Userway Website Accessibility · Loop Returns · Pdf Invoice Customizer · nice-team.net

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on williamsathleticclub.com, including 14 speed issues, 3 SEO issues and 5 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