Website review, no card needed
wodli.ch website review
Visit site (opens in a new tab)Reviewed 12 November 202637 issues · 77 checks
This review found 37 issues worth fixing on wodli.ch, 12 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. 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
73C- #81,007 of 108,842 reviewed websitesbeats 22%
- #50,682 of 61,763 online storesbeats 15%
- #47,529 of 56,363 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
1.9 s · 352 KiBAbout 352 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.4 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Shopify adds 249 ms
249 msShopify costs a phone 249 ms of main-thread work and 768 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 986 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,643 HTML elements
The page has 1,643 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (Shopify, shop.app and Google Fonts), adding 811 KiB and 255 ms of main-thread time.
Reduce unused CSS
250 ms · 29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 250 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 69 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
23 KiB3 images could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
6 KiB4 files are served with short cache lifetimes, so returning visitors download them again (6 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.
1 checks passed
Server response: 44 ms
44 msYour server sent the HTML in 44 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.6 s
9.6 sYour largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 9.7 s
9.7 sThe page becomes fully interactive after 9.7 s. Good is under 3.8 s.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image 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.
3 checks passed
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 46 ms
46 msScripts block the page for only 46 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 289 requests
2.6 MBYour homepage downloads 2.6 MB in 289 requests on a phone: scripts 958 KiB (112), other files 946 KiB (147) and images 489 KiB (16). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.7 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
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
18 text elements with low contrast
18 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.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Wodli, funktionelles Trainingsequipment, Springseile für CrossFitter – WODLI”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“Lager in der Schweiz. Keine Zollgebühren oder ext…”, “Jetzt viele TYR Schuhe im SALE” and “Rope Skipping Springseil”). One clear main headline is easier for people and search engines.
Meta description is long (317 characters)
Your meta description is 317 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
226 internal links, 3 external
The homepage links to 226 pages on wodli.ch and 3 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://wodli.ch/.
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://wodli.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.
3 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 (840 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://wodli.ch/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://wodli.ch/collections/sale and https://wodli.ch/collections/sale-1 all use the title “Sale – WODLI”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://wodli.ch/collections/equipment/Blor has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://wodli.ch/collections/wodli-tape and https://wodli.ch/collections/wodli-tape/Tape use the same meta description. A description written for each page earns more clicks.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://wodli.ch/collections/wodli-tape/Tape, whose canonical is https://wodli.ch/collections/wodli-tape/tape. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
12 small tap targets
12 of 56 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 “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 426 words of copy
The homepage carries about 426 words of visible text.
1 checks passed
6 short forms
6 short forms (1 field at most) are right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Meta Pixel (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
10 other companies contacted
Loading the homepage contacts 10 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 wodli.ch, 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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Sami Wholesale · Judge Me Reviews · Forms
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
- 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 37 issues on wodli.ch, including 10 speed issues, 6 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.