Website review, no card needed
rialclean.ch website review
Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 64 checks
This review found 26 issues worth fixing on rialclean.ch, 8 of them high impact, across 64 checks. The most urgent: use efficient cache lifetimes. 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
76CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
1.2 s · 1.6 MB26 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Render-blocking requests
1.5 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 81
81/100Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
638 KiB13 images could be 638 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
450 ms · 66 KiBAbout 66 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.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
3 third-party services on the page
3 third-party services load with your homepage (Cloudflare CDN, Google Fonts and brainstormforce.com), adding 119 KiB and 1 ms of main-thread time.
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: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 124 ms of it running JavaScript. That is comfortably low.
Server response: 119 ms
119 msYour server sent the HTML in 119 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “rialclean (Header)”. Most of its time is resource load delay (1.5 s).
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.111
0.111The layout shifts by 0.111 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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
Time to Interactive: 3.4 s
3.4 sThe page is fully interactive after 3.4 s.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
11 images in older formats
11 images (1.2 MB) are 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.
6 images far larger than shown
90 KiB6 images are downloaded at several times the size a phone draws them, for example residence-panorama-1024x668-landscape.jpg at 955 px wide, shown at 316 px. Resized copies would save about 90 KiB.
1 image below the first screen load straight away
1 image further down the page (133 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.49 g of CO₂e: 58.3 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.7 MB in 32 requests
1.7 MBYour homepage downloads 1.7 MB in 32 requests on a phone: images 1.3 MB (16), fonts 239 KiB (6) and scripts 95 KiB (4). That is a lean page.
Accessibility
10 buttons without a name
10 buttons have no accessible name, so screen readers announce just “button”.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (21 characters)
Your title is only 21 characters: “Rialclean Reinigungen”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (23 characters)
Your meta description is only 23 characters: “Reinigungen aller Arten”. 70 to 160 characters is enough to sell the click.
6 internal links, 2 external
The homepage links to 6 pages on rialclean.ch and 2 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://rialclean.ch/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.
XML sitemap found
Your XML sitemap is reachable at https://rialclean.ch/sitemap.xml.
AI search readiness
No llms.txt
There is no https://rialclean.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (446 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share a title
/, https://rialclean.ch/dienstleistungen, https://rialclean.ch/referenzen, https://rialclean.ch/kontakt and https://rialclean.ch/offertenanfrage all use the title “Rialclean Reinigungen”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://rialclean.ch/dienstleistungen, https://rialclean.ch/referenzen and https://rialclean.ch/kontakt have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://rialclean.ch/dienstleistungen, https://rialclean.ch/referenzen, https://rialclean.ch/kontakt and https://rialclean.ch/offertenanfrage have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://rialclean.ch/kontakt has 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.
2 pages slow to respond
https://rialclean.ch/dienstleistungen and https://rialclean.ch/offertenanfrage took over 3 s to send their HTML from our server.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 4 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Thin social proof
Social proof on the homepage: 25 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 671 words of copy
The homepage carries about 671 words of visible text.
Privacy and tracking
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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 rialclean.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2018.
Stack
- CMS
- WordPress
- Hosting
- Hostpoint AG
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on rialclean.ch, including 10 speed issues, 3 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.