Website review, no card needed

johnfoos.com logo

johnfoos.com website review

Visit site (opens in a new tab)Reviewed 24 October 202650 issues · 88 checks

This review found 50 issues worth fixing on johnfoos.com, 20 of them high impact, across 88 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

Real-visitor load time (LCP)75th percentile, phones
7.2 s5.0 sMay 2Oct 175.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20266.9 s
May 9, 20266.4 s
May 16, 20265.9 s
May 23, 20265.9 s
May 30, 20265.9 s
Jun 6, 20266.0 s
Jun 13, 20266.2 s
Jun 20, 20266.0 s
Jun 27, 20265.9 s
Jul 4, 20265.8 s
Jul 11, 20265.8 s
Jul 18, 20265.8 s
Jul 25, 20265.9 s
Aug 1, 20265.9 s
Aug 8, 20265.8 s
Aug 15, 20265.6 s
Aug 22, 20265.5 s
Aug 29, 20265.4 s
Sep 5, 20265.3 s
Sep 12, 20265.3 s
Sep 19, 20265.2 s
Sep 26, 20265.2 s
Oct 3, 20265.3 s
Oct 10, 20265.3 s
Oct 17, 20265.2 s
Real-visitor tap response (INP)75th percentile, phones
437 ms314 msMay 2Oct 17405 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026331 ms
May 9, 2026328 ms
May 16, 2026329 ms
May 23, 2026334 ms
May 30, 2026350 ms
Jun 6, 2026366 ms
Jun 13, 2026388 ms
Jun 20, 2026393 ms
Jun 27, 2026401 ms
Jul 4, 2026406 ms
Jul 11, 2026416 ms
Jul 18, 2026419 ms
Jul 25, 2026423 ms
Aug 1, 2026421 ms
Aug 8, 2026413 ms
Aug 15, 2026410 ms
Aug 22, 2026400 ms
Aug 29, 2026398 ms
Sep 5, 2026393 ms
Sep 12, 2026393 ms
Sep 19, 2026404 ms
Sep 26, 2026412 ms
Oct 3, 2026416 ms
Oct 10, 2026414 ms
Oct 17, 2026405 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 johnfoos.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. johnfoos.com at 1.5 s1.5 s
  2. johnfoos.com at 2.9 s2.9 s
  3. johnfoos.com at 4.4 s4.4 s
  4. johnfoos.com at 5.8 s5.8 s
  5. johnfoos.com at 7.3 s7.3 s
  6. johnfoos.com at 8.7 s8.7 s
  7. johnfoos.com at 10.2 s10.2 s
  8. johnfoos.com at 11.6 s11.6 s

Speed

17 to fix24
  • Render-blocking requests

    5.4 s

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

  • ThreatMetrix adds 1.8 s

    1.8 s

    ThreatMetrix costs a phone 1.8 s of main-thread work and 264 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 685 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 24

    24/100

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

  • Main-thread work: 9.7 s

    A phone's processor spends 9.7 s on main-thread work while loading, 5.8 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 (ThreatMetrix, Google Tag Manager and vtexassets.com and others), adding 3.2 MB and 4.8 s of main-thread time.

  • Improve image delivery

    800 ms · 219 KiB

    6 images could be 219 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • vtexassets.com adds 826 ms

    826 ms

    vtexassets.com costs a phone 826 ms of main-thread work and 1.5 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

    150 ms · 726 KiB

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

  • Reduce unused JavaScript

    824 KiB

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

  • 20 long tasks on the main thread

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

  • Document request latency

    550 ms

    The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    537 ms

    Reduce initial server response time. Google estimates savings of 537 ms on a phone.

  • Reduce unused CSS

    450 ms · 54 KiB

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

  • TikTok adds 395 ms

    395 ms

    TikTok costs a phone 395 ms of main-thread work and 160 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.

  • Facebook adds 283 ms

    283 ms

    Facebook costs a phone 283 ms of main-thread work and 283 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.

  • Server response: 637 ms

    637 ms

    Your server takes 637 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Legacy JavaScript

    150 ms · 56 KiB

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

  • Font display

    50 ms

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

Core Web Vitals

13 to fix0
  • 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.6 s

    4.6 s

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

  • Real-user CLS: 0.26

    0.26

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

  • Real-user FCP: 4.5 s

    4.5 s

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

  • First Contentful Paint: 25.9 s

    25.9 s

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

  • Largest Contentful Paint: 28.4 s

    28.4 s

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

  • Speed Index: 25.9 s

    25.9 s

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

  • Time to Interactive: 48.6 s

    48.6 s

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

  • Total Blocking Time: 3.1 s

    3.1 s

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

  • Real-user INP: 332 ms

    332 ms

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

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

    +24%

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • 16 images without width and height

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

2 checks passed
  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • Cumulative Layout Shift: 0.075

    0.075

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

Images and page weight

2 to fix69
  • Page weight: 7.9 MB in 172 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 172 requests on a phone: HTML 4.0 MB (7), scripts 2.2 MB (68) and images 607 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    07058951-d374-47d4-87c5-073e3bfc506e___3f73b6d375d8195adaebc is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image below the first screen load straight away

    1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.23 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8892
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 6 tap targets too small

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

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

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

5 to fixGoogle 10071
  • No H1 headline

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

  • Title is short (9 characters)

    Your title is only 9 characters: “John Foos”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (9 characters)

    Your meta description is only 9 characters: “John Foos”. 70 to 160 characters is enough to sell the click.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 12 internal links, 2 external

    The homepage links to 12 pages on johnfoos.com and 2 external pages.

3 checks passed
  • Canonical URL set

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

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

  • No llms.txt

    There is no https://www.johnfoos.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.

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

Other pages

100
  • 4 pages slow to respond

    https://www.johnfoos.com/182-negro-chunky/p, https://www.johnfoos.com/apparel/indumentaria, https://www.johnfoos.com/street and https://www.johnfoos.com/kids took over 3 s to send their HTML from our server.

  • 5 internal pages checked

    We fetched 5 pages linked from your homepage and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 5 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

2 to fix87
  • 13 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 94 words

    The homepage has only about 94 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.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

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, Hotjar 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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 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.

  • 49 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on johnfoos.com, including 30 speed issues, 5 SEO issues and 4 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