Website review, no card needed
gshc.ch website review
Visit site (opens in a new tab)Reviewed 20 October 202632 issues · 81 checks
This review found 32 issues worth fixing on gshc.ch, 12 of them high impact, across 81 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 851 ms |
| May 9, 2026 | 891 ms |
| May 16, 2026 | 964 ms |
| May 23, 2026 | 967 ms |
| May 30, 2026 | 969 ms |
| Jun 6, 2026 | 912 ms |
| Jun 13, 2026 | 879 ms |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 965 ms |
| Aug 15, 2026 | 986 ms |
| Aug 22, 2026 | 946 ms |
| Aug 29, 2026 | 944 ms |
| Sep 5, 2026 | 938 ms |
| Sep 12, 2026 | 904 ms |
| Sep 19, 2026 | 930 ms |
| Sep 26, 2026 | 964 ms |
| Oct 3, 2026 | 996 ms |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 117 ms |
| May 9, 2026 | 111 ms |
| May 16, 2026 | 108 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 94 ms |
| Jul 4, 2026 | 92 ms |
| Jul 11, 2026 | 90 ms |
| Jul 18, 2026 | 124 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 136 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 127 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 126 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 132 ms |
| Oct 17, 2026 | 131 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
Speed
Render-blocking requests
2.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
YouTube adds 1.6 s
1.6 sYouTube costs a phone 1.6 s of main-thread work and 3.1 MB 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: 47
47/100Your mobile performance score is 47 (desktop: 84). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.9 s
A phone's processor spends 5.9 s on main-thread work while loading, 2.7 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 (YouTube, Google Tag Manager and Facebook and others), adding 3.9 MB and 2.4 s of main-thread time.
Reduce unused JavaScript
1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
600 ms · 96 KiBAbout 96 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.
Improve image delivery
557 KiB6 images could be 557 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
550 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).
Google Tag Manager adds 365 ms
365 msGoogle Tag Manager costs a phone 365 ms of main-thread work and 370 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.
Use efficient cache lifetimes
358 KiB6 files are served with short cache lifetimes, so returning visitors download them again (358 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 268 ms. During a long task the page ignores taps.
Legacy JavaScript
67 KiBPolyfills for old browsers add 67 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 84 but mobile only 47. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 122 ms
122 msYour server sent the HTML in 122 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 33.9 s
33.9 sThe page becomes fully interactive after 33.9 s. Good is under 3.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GENÈVE-SERVETTE HOCKEY CLUB”.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 117 ms to 131 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 400 ms
400 msReal visitors wait 400 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.073
0.073The layout barely moves while loading (CLS 0.073, good is under 0.1).
Images and page weight
Page weight: 6.4 MB in 112 requests
6.4 MBYour homepage downloads 6.4 MB in 112 requests on a phone: scripts 3.6 MB (39), images 2.1 MB (25) and stylesheets 244 KiB (9). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
286 KiB2 images are downloaded at several times the size a phone draws them, for example banner.jpg at 1,600 px wide, shown at 366 px. Resized copies would save about 286 KiB.
1 image in older formats
1 image (483 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 1.8 g of CO₂ per visit
1.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.81 g of CO₂e: 217.2 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
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“GENÈVE-SERVETTEHOCKEY CLUB”, “COORDONNÉES” and “GENÈVE-SERVETTE HOCKEY CLUB”). One clear main headline is easier for people and search engines.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
55 internal links, 34 external
The homepage links to 55 pages on gshc.ch and 34 external pages.
6 checks passed
Meta description: 95 characters
Your meta description is 95 characters: “Page officielle du Genève-Servette Hockey Club (#GSHC) - Club de hockey professionnel de Genève”.
Title: 57 characters
Your title is a healthy 57 characters: “Genève-Servette Hockey Club - Genève-Servette Hockey Club”.
Canonical URL set
The canonical URL is https://www.gshc.ch/.
Structured data in place
Structured data found: WebPage.
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.gshc.ch/sitemap.xml.
AI search readiness
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.gshc.ch/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (457 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.gshc.ch/anniversaires is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 pages without a meta description
https://www.gshc.ch/game-center, https://www.gshc.ch/offres-abonnements, https://www.gshc.ch/effectif, https://www.gshc.ch/contact, https://www.gshc.ch/fans/infos-pratiques-jour-de-match and https://www.gshc.ch/fans/application-officielle and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://fonts.googleapis.com/css2?family=DM+Sans:ital,opsz,wght@0,9..40,100..1000;1,9..40,100..1000&fami…”.
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
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 457 words of copy
The homepage carries about 457 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
22 other companies contacted
Loading the homepage contacts 22 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 gshc.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- TYPO3 CMS
- Analytics
- Google Tag Manager
Company
- Founded
- 1905
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on gshc.ch, including 17 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.