tebis.com website review

The page has 49,480 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

About 198 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

About 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

A phone's processor spends 3.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

3 third-party services load with your homepage (cookiebot.eu, site.com and salesforce-scrt.com), adding 1.1 MB and 188 ms of main-thread time.

cookiebot.eu costs a phone 174 ms of main-thread work and 313 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.

site.com costs a phone 14 ms of main-thread work and 763 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.

1 image could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 3.6 MB in 46 requests on a phone: scripts 2.4 MB (20), fonts 718 KiB (2) and stylesheets 178 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

12 form fields have no label, so screen readers announce an empty box and autofill guesses.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 410 pages on tebis.com and 28 external pages.

There is no https://www.tebis.com/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.tebis.com/en/careers, https://www.tebis.com/en/academy/videos, https://www.tebis.com/en/blog, https://www.tebis.com/en/academy, https://www.tebis.com/en/software/cam-software/smartops-technology and https://www.tebis.com/en/software/cam-software/tebis-automill have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tebis.com/en/software/cam-software/smartops-technology has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tebis.com/en/academy, https://www.tebis.com/en/mytebis, https://www.tebis.com/en/software and https://www.tebis.com/en/software/cam-software took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://www.tebis.com/en.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 51 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 1,953 words of visible text.

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

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