Website review, no card needed

boll.ch logo

boll.ch website review

Visit site (opens in a new tab)Reviewed 22 October 202638 issues · 77 checks

This review found 38 issues worth fixing on boll.ch, 12 of them high impact, across 77 checks. The most urgent: font display. 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
919 ms635 msMay 2Oct 3738 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026820 ms
May 9, 2026668 ms
May 16, 2026701 ms
May 23, 2026784 ms
May 30, 2026731 ms
Jun 6, 2026813 ms
Jun 13, 2026805 ms
Jun 20, 2026805 ms
Jul 4, 2026852 ms
Jul 11, 2026809 ms
Jul 18, 2026811 ms
Jul 25, 2026886 ms
Aug 1, 2026734 ms
Aug 8, 2026772 ms
Aug 15, 2026697 ms
Aug 22, 2026708 ms
Aug 29, 2026781 ms
Sep 5, 2026805 ms
Sep 12, 2026839 ms
Sep 19, 2026819 ms
Sep 26, 2026738 ms
Oct 3, 2026738 ms
Real-visitor tap response (INP)75th percentile, phones
71 ms70 msSep 5Sep 2671 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 202670 ms
Sep 12, 202671 ms
Sep 19, 202670 ms
Sep 26, 202671 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

Full-page screenshot of boll.ch (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. boll.ch at 0.8 s0.8 s
  2. boll.ch at 1.6 s1.6 s
  3. boll.ch at 2.3 s2.3 s
  4. boll.ch at 3.1 s3.1 s
  5. boll.ch at 3.9 s3.9 s
  6. boll.ch at 4.7 s4.7 s
  7. boll.ch at 5.5 s5.5 s
  8. boll.ch at 6.3 s6.3 s

Speed

5 to fix75
  • Font display

    3.0 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).

  • Use efficient cache lifetimes

    350 ms · 4.5 MB

    67 files are served with short cache lifetimes, so returning visitors download them again (4.5 MB).

  • Improve image delivery

    3.6 MB

    29 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 75

    75/100

    Your mobile performance score is 75 (desktop: 71). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    650 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Reduce unused CSS

    15 KiB

    About 15 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.2 s

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

  • Server response: 241 ms

    241 ms

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

Core Web Vitals

3 to fix75
  • Cumulative Layout Shift: 0.328

    0.328

    The layout shifts by 0.328 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 6.3 s

    6.3 s

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

  • 34 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.7 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.

4 checks passed
  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Das 1988 gegründete IT-Unternehmen BOLL Engineering AG zähl…”.

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Time to Interactive: 2.5 s

    2.5 s

    The page is fully interactive after 2.5 s.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix43
  • Page weight: 4.6 MB in 68 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 68 requests on a phone: images 4.5 MB (61), HTML 45 KiB (1) and fonts 32 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (1.8 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.

  • 3 images far larger than shown

    393 KiB

    3 images are downloaded at several times the size a phone draws them, for example 35_years_boll.jpg at 1,260 px wide, shown at 316 px. Resized copies would save about 393 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (554 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.29 g

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

Accessibility

11 to fixGoogle 5675
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 21 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 21 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

7 to fixGoogle 9170
  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 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.boll.ch/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at boll.ch/robots.txt, the first file search crawlers ask for.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 258 internal links, 15 external

    The homepage links to 258 pages on boll.ch and 15 external pages.

2 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “BOLL Engineering AG vertreibt L�sungen in den Bereichen Netzwerk- und Mail-Security, Identity- und Access-Management so…”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “BOLL Engineering AG - IT Security Distribution”.

AI search readiness

1 to fix88
  • 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.boll.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (700 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 4 pages share a title

    /, https://www.boll.ch/ch_de/index.html, https://www.boll.ch/ch_fr/index.html and https://www.boll.ch/portfolio.html all use the title “BOLL Engineering AG - IT Security Distribution”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.boll.ch/solutions/index.html, https://www.boll.ch/asimily/index.html, https://www.boll.ch/claroty/index.html, https://www.boll.ch/cyolo/index.html, https://www.boll.ch/eset/index.html and https://www.boll.ch/fudo/index.html and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.boll.ch/ch_de/index.html, https://www.boll.ch/ch_fr/index.html and https://www.boll.ch/portfolio.html use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.boll.ch/ch_de/index.html and https://www.boll.ch/ch_fr/index.html have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 7 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

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

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

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

    The homepage carries about 401 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Learn more...”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

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 boll.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on boll.ch, including 8 speed issues, 7 SEO issues and 2 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