otpco.com website review

4 images could be 431 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Facebook and weglot.com and others), adding 707 KiB and 824 ms of main-thread time.

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

Google Tag Manager costs a phone 380 ms of main-thread work and 298 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.

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

Facebook costs a phone 281 ms of main-thread work and 223 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.

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

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

63 KiB could be saved by minifying JavaScript.

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

Your largest element takes 10.9 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 10.9 s. Good is under 3.8 s.

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

Scripts block taps and scrolling for 733 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 75 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

4 images (593 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.

3 images further down the page (337 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 0.47 g of CO₂e: 56.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

No XML sitemap at https://www.otpco.com/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 54 pages on otpco.com and 6 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://www.otpco.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.otpco.com/energy-control and https://www.otpco.com/energy-control/current-and-recent-energy-control use the same meta description. A description written for each page earns more clicks.

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

5 of 18 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 “Loading the image 'https://connect.facebook.net//log/error?p=pixel&pn=SmartSetup&sl=1&v=2.9.429&e=Error%3A%20%5BSmartSe…”.

Requests the geolocation permission on page load.

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

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.

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.

The homepage has only about 204 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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 9 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.