Website review, no card needed

yokohamafc.shop logo

yokohamafc.shop website review

Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 71 checks

This review found 29 issues worth fixing on yokohamafc.shop, 10 of them high impact, across 71 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
1.3 s1.0 sMay 16Aug 291.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.2 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
80 ms74 msMay 16Jul 2579 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202676 ms
May 23, 202675 ms
May 30, 202677 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202678 ms
Jul 18, 202679 ms
Jul 25, 202679 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 yokohamafc.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. yokohamafc.shop at 0.6 s0.6 s
  2. yokohamafc.shop at 1.1 s1.1 s
  3. yokohamafc.shop at 1.7 s1.7 s
  4. yokohamafc.shop at 2.3 s2.3 s
  5. yokohamafc.shop at 2.9 s2.9 s
  6. yokohamafc.shop at 3.4 s3.4 s
  7. yokohamafc.shop at 4.0 s4.0 s
  8. yokohamafc.shop at 4.6 s4.6 s

Speed

5 to fix68
  • Improve image delivery

    1.1 s · 294 KiB

    3 images could be 294 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.

  • Mobile performance score: 68

    68/100

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

  • Render-blocking requests

    900 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Reduce unused CSS

    600 ms · 116 KiB

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

  • Google Fonts adds 4 ms

    4 ms

    Google Fonts costs a phone 4 ms of main-thread work and 343 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 JavaScript

    150 ms · 22 KiB

    About 22 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Shopify, jQuery CDN and Google Fonts and others), adding 453 KiB and 32 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 60 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    5 KiB

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

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

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 271 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix68
  • Largest Contentful Paint: 7.4 s

    7.4 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Time to Interactive: 7.4 s

    7.4 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Tap response (INP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 76 ms to 79 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-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 5 ms

    5 ms

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

Images and page weight

2 to fix86
  • An image on the first screen is lazy-loaded

    yfc2026-main.jpg 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 far larger than shown

    166 KiB

    1 image is downloaded at several times the size a phone draws it, for example yfc2026-main.jpg at 1,900 px wide, shown at 390 px. Resized copies would save about 166 KiB.

  • 1 image in older formats

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

  • About 0.5 g of CO₂ per visit

    0.51 g

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

1 checks passed
  • Page weight: 1.8 MB in 159 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 159 requests on a phone: other files 701 KiB (85), images 395 KiB (4) and fonts 325 KiB (11). That is a lean page.

Accessibility

5 to fixGoogle 8392
  • 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.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 1 form field without a label

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

  • 1 link without text

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Meta description is short (46 characters)

    Your meta description is only 46 characters: “横浜FCオフィシャルオンラインストアです。限定商品や応援グッズなどを多数ご用意しております。”. 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 “ld+json block 1 is not valid JSON (Expected ',' or ']' after array element in JSON at position )”.

  • One H1 headline

    Your <h1> is empty.

  • 26 internal links, 10 external

    The homepage links to 26 pages on yokohamafc.shop and 10 external pages.

5 checks passed
  • Title: 42 characters

    Your title is a healthy 42 characters: “YOKOHAMA FC ONLINE STORE | 横浜FC・公式オンラインストア”.

  • Canonical URL set

    The canonical URL is https://yokohamafc.shop/.

  • 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://yokohamafc.shop/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://yokohamafc.shop/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 13 pages without a meta description

    https://yokohamafc.shop/collections/all, https://yokohamafc.shop/collections/uniform, https://yokohamafc.shop/collections/%E8%A6%B3%E6%88%A6-%E5%BF%9C%E6%8F%B4%E3%82%B0%E3%83%83%E3%82%BA, https://yokohamafc.shop/collections/fashion, https://yokohamafc.shop/collections/accessories and https://yokohamafc.shop/collections/%E9%9B%91%E8%B2%A8 and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://yokohamafc.shop/collections/%E8%A6%B3%E6%88%A6-%E5%BF%9C%E6%8F%B4%E3%82%B0%E3%83%83%E3%82%BA, whose canonical is https://yokohamafc.shop/collections/%e8%a6%b3%e6%88%a6-%e5%bf%9c%e6%8f%b4%e3%82%b0%e3%83%83%e3%82%ba. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages with very little text

    https://yokohamafc.shop/collections/all, https://yokohamafc.shop/collections/uniform, https://yokohamafc.shop/collections/%E8%A6%B3%E6%88%A6-%E5%BF%9C%E6%8F%B4%E3%82%B0%E3%83%83%E3%82%BA, https://yokohamafc.shop/collections/fashion, https://yokohamafc.shop/collections/accessories and https://yokohamafc.shop/collections/%E9%9B%91%E8%B2%A8 and 7 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 13 internal pages checked

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

5 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • 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 13 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    20 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 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.

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

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

1 checks passed
  • 2 short forms

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (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.

  • 9 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on yokohamafc.shop, including 9 speed issues, 3 SEO issues and 6 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