sensit-tech.com website review

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

24 images could be 23.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 22.3 s faster on a phone.

About 518 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.6 s faster on a phone.

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

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

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

4 third-party services load with your homepage (Hotjar, Google Tag Manager and bunny.net and others), adding 246 KiB and 393 ms of main-thread time.

2 KiB could be saved by minifying JavaScript.

7 KiB could be saved by minifying CSS.

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.

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

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

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

The first text or image appears after 6.8 s on a phone. Good is under 1.8 s.

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

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

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

Your homepage downloads 30.4 MB in 84 requests on a phone: images 28.3 MB (37), scripts 822 KiB (27) and HTML 716 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example NWE.webp at 1,500 px wide, shown at 85 px. Resized copies would save about 66 KiB.

4 images (154 KiB) 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.

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

7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 tap target is too small or too close together to hit reliably with a finger.

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

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 on the page fails this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

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

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

The homepage links to 102 pages on sensit-tech.com and 2 external pages.

https://sensit-tech.com/gas-leak-detection-products and https://sensit-tech.com/products all use the title “Gas Leak Detection Products - Methane & Multi-Gas Detectors - SENSIT …”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sensit-tech.com/gas-leak-detection-products and https://sensit-tech.com/products use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://sensit-tech.com/products, whose canonical is https://sensit-tech.com/gas-leak-detection-products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://sensit-tech.com/gas-leak-detection-products, https://sensit-tech.com/products and https://sensit-tech.com/gas-leak-detection-software have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

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 389 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Hotjar (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.

Opening the homepage sets 11 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.