Website review, no card needed

wiannoclub.com logo

wiannoclub.com website review

Visit site (opens in a new tab)Reviewed 18 October 202641 issues · 83 checks

This review found 41 issues worth fixing on wiannoclub.com, 15 of them high impact, across 83 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
2.0 s1.5 sJun 20Sep 51.5 s
Show as table
DateReal-visitor load time (LCP)
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20262.0 s
Aug 15, 20261.8 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.5 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 wiannoclub.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wiannoclub.com at 0.4 s0.4 s
  2. wiannoclub.com at 0.8 s0.8 s
  3. wiannoclub.com at 1.1 s1.1 s
  4. wiannoclub.com at 1.5 s1.5 s
  5. wiannoclub.com at 1.9 s1.9 s
  6. wiannoclub.com at 2.3 s2.3 s
  7. wiannoclub.com at 2.6 s2.6 s
  8. wiannoclub.com at 3.0 s3.0 s

Speed

9 to fix55
  • Render-blocking requests

    8.8 s

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

  • Reduce unused JavaScript

    4.2 s · 820 KiB

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

  • Reduce unused CSS

    4.2 s · 798 KiB

    About 798 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.2 s faster on a phone.

  • Use efficient cache lifetimes

    3.5 s · 608 KiB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 58). 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 (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.5 MB and 505 ms of main-thread time.

  • Minify JavaScript

    450 ms · 36 KiB

    36 KiB could be saved by minifying JavaScript.

  • YouTube adds 340 ms

    340 ms

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

  • Google Tag Manager adds 151 ms

    151 ms

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

  • Legacy JavaScript

    200 ms · 10 KiB

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

  • Minify CSS

    150 ms · 13 KiB

    13 KiB could be saved by minifying CSS.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 135 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).

  • Improve image delivery

    14 KiB

    2 images could be 14 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix66
  • First Contentful Paint: 15.1 s

    15.1 s

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

  • Largest Contentful Paint: 19.5 s

    19.5 s

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

  • Speed Index: 15.1 s

    15.1 s

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

  • Time to Interactive: 19.5 s

    19.5 s

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

  • 17 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 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
  • Total Blocking Time: 91 ms

    91 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 94 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 94 requests on a phone: scripts 1.6 MB (49), stylesheets 817 KiB (22) and fonts 302 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

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

  • 1 image below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.83 g

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

1 checks passed
  • 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 8792
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 3 images without alt text

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 checks passed
  • 35 automated accessibility rules passed

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

SEO

8 to fixGoogle 6260
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (25 characters)

    Your title is only 25 characters: “Public Home - Wianno 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.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.wiannoclub.com/sitemap.xml, so Google discovers your pages only by following links.

  • 15 links with vague text

    15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 17 internal links, 3 external

    The homepage links to 17 pages on wiannoclub.com and 3 external pages.

2 checks passed
  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    32%

    The HTML your server sends has 101 of the 313 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.wiannoclub.com/web/pages/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.wiannoclub.com/web/pages/home all use the title “Public Home - Wianno Club”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.wiannoclub.com/web/pages/home, https://www.wiannoclub.com/web/pages/the-club, https://www.wiannoclub.com/web/pages/for-guests, https://www.wiannoclub.com/web/pages/contact and https://www.wiannoclub.com/web/pages/careers have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.wiannoclub.com/web/pages/home has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.wiannoclub.com/web/pages/home and https://www.wiannoclub.com/web/pages/contact 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.

  • 5 internal pages checked

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

3 checks passed
  • Linked pages load

    All 5 pages we checked loaded without an error.

  • 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

4 to fixGoogle 5483
  • 17 small tap targets

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

  • 5 third-party cookies

    5 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.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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 social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 313 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 2 short forms

    2 short forms (0 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 8 cookies set on arrival

    8

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 wiannoclub.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
Analytics
Google 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 41 issues on wiannoclub.com, including 14 speed issues, 8 SEO issues and 3 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