apem.com website review

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

8 third-party services load with your homepage (Google CDN, Hubspot and Google Tag Manager and others), adding 2.9 MB and 1.9 s of main-thread time.

About 1.3 MB of JavaScript is downloaded but never used on this page.

Google CDN costs a phone 886 ms of main-thread work and 1.5 MB 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.

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

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

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

Hubspot costs a phone 389 ms of main-thread work and 732 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.

Google Tag Manager costs a phone 270 ms of main-thread work and 269 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 2,497 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

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.

The page becomes fully interactive after 28.4 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.

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

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your homepage downloads 5.4 MB in 189 requests on a phone: scripts 3.8 MB (117), other files 724 KiB (19) and images 390 KiB (34). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (31 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

6 tap targets are too small or too close together to hit reliably with a finger.

Some list items are not inside a list.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

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

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

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

The homepage links to 152 pages on apem.com and 4 external pages.

There is no /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.

/en-us, /, /fr and /de all use the title “APEM | Human-machine interface (HMI) solutions | Global Leader”. Search engines can't tell which page to show for a search, so each competes with the others.

/products has no meta description, so Google writes the search snippet from whatever text it finds.

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

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /, whose canonical is /en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/products has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'about:blank' from origin 'https://www.apem.com' has been blocked by CORS policy: Cross ori…”.

Large scripts ship without source maps.

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

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

apem.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

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.

Before a visitor clicks anything, the page loads Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 15 cookies, 1 of them by other companies (measured from a US location before any click).

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