Website review, no card needed

vintage-muscle.org logo

vintage-muscle.org website review

Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 76 checks

This review found 35 issues worth fixing on vintage-muscle.org, 10 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of vintage-muscle.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vintage-muscle.org at 0.8 s0.8 s
  2. vintage-muscle.org at 1.5 s1.5 s
  3. vintage-muscle.org at 2.3 s2.3 s
  4. vintage-muscle.org at 3.0 s3.0 s
  5. vintage-muscle.org at 3.8 s3.8 s
  6. vintage-muscle.org at 4.5 s4.5 s
  7. vintage-muscle.org at 5.3 s5.3 s
  8. vintage-muscle.org at 6.1 s6.1 s

Speed

11 to fix67
  • Render-blocking requests

    1.1 s

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

  • Main-thread work: 4.1 s

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

  • 3,266 HTML elements

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

  • Improve image delivery

    1.4 MB

    20 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (loox.io, Klaviyo and Google Tag Manager and others), adding 3.0 MB and 843 ms of main-thread time.

  • Mobile performance score: 67

    67/100

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

  • Reduce unused JavaScript

    528 KiB

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

  • loox.io adds 307 ms

    307 ms

    loox.io costs a phone 307 ms of main-thread work and 850 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.

  • 8 long tasks on the main thread

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

  • Klaviyo adds 185 ms

    185 ms

    Klaviyo costs a phone 185 ms of main-thread work and 517 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 81 ms

    81 ms

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

  • Use efficient cache lifetimes

    136 KiB

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

  • Reduce unused CSS

    36 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

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

6 to fix66
  • Time to Interactive: 20.4 s

    20.4 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Built for the Man Who Wants His Old Self Back.”.

  • Speed Index: 5.1 s

    5.1 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Total Blocking Time: 301 ms

    301 ms

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

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.9 MB in 331 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 331 requests on a phone: images 2.3 MB (48), scripts 1.4 MB (111) and other files 937 KiB (125). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.38 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

4 to fixGoogle 9794
  • 7 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 79 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 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 10082
  • Canonical points to another host

    Your canonical URL points to vintage-muscle.com, not vintage-muscle.org, so Google may credit that host instead.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Built for the Man Who Wants His Old Self Back.”). One clear main headline is easier for people and search engines.

  • Meta description is long (248 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 117 internal links, 17 external

    The homepage links to 117 pages on vintage-muscle.org and 17 external pages.

4 checks passed
  • Title: 58 characters

    Your title is a healthy 58 characters: “Vintage Muscle: Where Old-School Grit Meets Modern Science”.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://vintage-muscle.org/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 (4,456 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix58
  • 2 linked pages are broken

    Your homepage links to https://vintage-muscle.org/pages/quiz-4-0 and https://vintage-muscle.org/products/uronabol, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    / and https://vintage-muscle.org/discount/B2G2 all use the title “Vintage Muscle: Where Old-School Grit Meets Modern Science”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://vintage-muscle.org/collections/all, https://vintage-muscle.org/collections/shop-now and https://vintage-muscle.org/pages/help have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://vintage-muscle.org/collections/all, https://vintage-muscle.org/collections/shop-now, https://vintage-muscle.org/pages/helphq, https://vintage-muscle.org/pages/help, https://vintage-muscle.org/products/code-name-hades-fat-burner and https://vintage-muscle.org/products/myo-11-myostatin-inhibitor and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://vintage-muscle.org/products/myo-11-myostatin-inhibitor took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 1,326 words of copy

    The homepage carries about 1,326 words of visible text.

  • Urgency cues

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

5 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Buy Now”, “Shop Best Sellers” and “Shop All Products →”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 441 testimonial or review blocks, 40 customer or partner logos, a star rating, 2 trust badges and “14,500+ reviews”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 46 other companies contacted

    Loading the homepage contacts 46 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 vintage-muscle.org, 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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Wyllo Formerly Nofraud · Klaviyo Email Marketing Sms · Freegifts · loox.io · rechargecdn.com · gorgias.chat · bogos.io · goaffpro.com · 9gtb.com

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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on vintage-muscle.org, including 17 speed issues, 5 SEO issues and 1 conversion gap. 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