anika.com website review

Google Tag Manager costs a phone 2.3 s of main-thread work and 516 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 11.6 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Other Google APIs/SDKs and others), adding 941 KiB and 3.3 s of main-thread time.

Your mobile performance score is 53 (desktop: 98). Pages that score under 90 lose visitors before the first paint.

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

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

About 382 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Other Google APIs/SDKs costs a phone 376 ms of main-thread work and 115 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.

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

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

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

Desktop scores 98 but mobile only 53. 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.

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

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.

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

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

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Restore Active Living®”. Most of its time is element render delay (1.7 s).

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

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

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

By the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 52.8 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: 1 element on the page fails this check, rated moderate by axe-core.

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

Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 92 pages on anika.com and 12 external pages.

https://anika.com/about/contact took over 3 s to send its HTML from our server.

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

Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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