apsis.com website review

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

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

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

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

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

8 third-party services load with your homepage (Unpkg, Google Tag Manager and Cookiebot and others), adding 734 KiB and 584 ms of main-thread time.

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

1 image could be 18 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.

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

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

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

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

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

Desktop scores 68 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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.

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

For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.

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

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

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

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

Real visitors wait 211 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-17, real Chrome visitors' tap response (inp) went from 116 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

11 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-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 image further down the page (25 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 0.45 g of CO₂e: 54.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA tab nodes must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

The homepage links to 115 pages on apsis.com and 23 external pages.

/sv, /da, /fi and /no declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, /da, /fi and /no all use the title “AI-Driven Email Marketing & Automation for Growth | Apsis”. Search engines can't tell which page to show for a search, so each competes with the others.

/da, /fi and /no use the same meta description. A description written for each page earns more clicks.

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "lottie-player" has already…”.

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

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

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

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.

The homepage carries about 1,182 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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

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