f-secure.com website review

About 452 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 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.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.

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

1 file is served with short cache lifetimes, so returning visitors download them again (61 KiB).

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

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

3 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Analytics), adding 521 KiB and 485 ms of main-thread time.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

2 images are downloaded at several times the size a phone draws them, for example mother-child-dog-sofa.png at 998 px wide, shown at 310 px. Resized copies would save about 22 KiB.

3 images further down the page (249 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (85 KiB) is 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Some list items are not inside a list.

1 text element doesn'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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (3 elements).

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 132 pages on f-secure.com and 33 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.

/us-en/total/scam-protection, /us-en/articles/do-macs-iphones-and-ipads-need-antivirus, /us-en/articles/why-do-hackers-want-your-personal-information and /us-en/support took over 3 s to send their HTML from our server.

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

4 of 12 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 Content-Security-Policy header, the main browser-side defence against injected scripts.

Opening https://f-secure.com goes through 2 redirects before the homepage loads.

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

f-secure.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.

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

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 652 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.

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