etq.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Vidyard and Optanon and others), adding 2.4 MB and 758 ms of main-thread time.

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

5 images could be 134 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

Vidyard costs a phone 143 ms of main-thread work and 699 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.

ffycdn.net costs a phone 0 ms of main-thread work and 342 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.

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

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

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

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 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 4.2 MB in 213 requests on a phone: scripts 2.0 MB (104), images 862 KiB (31) and other files 707 KiB (27). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Your title is only 24 characters: “Octave Reliance | Octave”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 56 pages on etq.com and 10 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/en declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/products/asset-performance-management is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/en and / all use the title “Mission-critical software for actionable intelligence | Octave”. Search engines can't tell which page to show for a search, so each competes with the others.

/support, /products/asset-performance-management, /products/asset-performance-management/reliance/supply-chain-quality-management, /products/asset-performance-management/reliance/new-product-introduction, /products/asset-performance-management/reliance/quality-events and /products/asset-performance-management/reliance/health-safety and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/en and / use the same meta description. A description written for each page earns more clicks.

/general-inquiry, /products and /products/asset-performance-management have no <h1> headline, so visitors and search engines get no clear main topic.

/products has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

Opening https://etq.com goes through 2 redirects before the homepage loads.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

octave.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

octave.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 13 fields (8 required). Every extra field lowers completion.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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