lenels2.com website review

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

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

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

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

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

About 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

18 long tasks block the main thread while loading, the longest for 2.0 s. During a long task the page ignores taps.

8 third-party services load with your homepage (Adobe Scene7, signalfx.com and Optanon and others), adding 1.1 MB and 1.0 s of main-thread time.

383 KiB could be saved by minifying JavaScript.

Adobe Scene7 costs a phone 315 ms of main-thread work and 59 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.

Optanon costs a phone 249 ms of main-thread work and 594 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.

signalfx.com costs a phone 270 ms of main-thread work and 228 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.

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

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

4 images could be 139 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TRUSTED SECURITY. INNOVATION ADVANTAGE. Security is complex…”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 368 ms to 355 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 3.1 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.9 MB in 180 requests on a phone: scripts 4.7 MB (74), other files 764 KiB (55) and images 665 KiB (27). Under 2 MB keeps phones on slow connections fast.

2 images (383 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.

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

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

2 buttons have no accessible name, so screen readers announce just “button”.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

10 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

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

15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

Open Graph is missing og:description, so shared links fall back to guesses.

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

The homepage links to 140 pages on lenels2.com and 10 external pages.

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.

There is no https://buildings.honeywell.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://buildings.honeywell.com/au/en/home, https://buildings.honeywell.com/in/en/home, https://buildings.honeywell.com/pl/en/home, https://buildings.honeywell.com/dk/en/home, https://buildings.honeywell.com/gb/en/home and https://buildings.honeywell.com/ae/en/home all use the title “Building Automation”. Search engines can't tell which page to show for a search, so each competes with the others.

https://buildings.honeywell.com/us/en/redirects/external/honeywell-building-technologies-japan has no meta description, so Google writes the search snippet from whatever text it finds.

https://buildings.honeywell.com/au/en/home, https://buildings.honeywell.com/in/en/home, https://buildings.honeywell.com/pl/en/home, https://buildings.honeywell.com/dk/en/home, https://buildings.honeywell.com/gb/en/home and https://buildings.honeywell.com/ae/en/home 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://buildings.honeywell.com/us/en/redirects/external/honeywell-building-technologies-japan, whose canonical is https://buildings.honeywell.com/us/en/brands/our-brands/building-ja. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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