jobs.ch website review

About 257 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.

7 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

2 third-party services load with your homepage (avo.app and jobcloud.services), adding 128 KiB and 38 ms of main-thread time.

Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need.

9 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 273 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Scripts block taps and scrolling for 234 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 219 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

52 visible links have no text or label, so screen readers cannot say where they go.

7 tap targets are too small or too close together to hit reliably with a finger.

Your title is 72 characters, so Google will cut it off around 60: “Job search on jobs.ch, the leading online job portal on the Swiss market”.

Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 152 pages on jobs.ch and 22 external pages.

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

https://www.jobs.ch/en/spotted has no <title>, so Google invents the link text in results.

https://www.jobs.ch/en and / all use the title “Job search on jobs.ch, the leading online job portal on the Swiss mar…”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.jobs.ch/en/spotted has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jobs.ch/en/companies/409d21a5-444a-4de7-ac39-682517b9864f-hotela-caisse-de-compensation-avs and https://www.jobs.ch/en/companies/409d21a5-444a-4de7-ac39-682517b9864f-hotela-caisse-de-compensation-avs/vacancies use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.jobs.ch/en/vacancies, whose canonical is https://www.jobs.ch/en/vacancies?term=. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.jobs.ch/en/vacancies has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.jobs.ch/en/companies/5e39cc7f-8f78-4065-be5d-b5005f23fca7-data-consulting-s-a/vacancies 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.

We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Content security policy”).

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 382 words of visible text.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.