lilith.fi website review

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

7 images could be 540 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

About 93 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.

5 third-party services load with your homepage (Facebook, Google Tag Manager and cookieconfirm.com and others), adding 778 KiB and 533 ms of main-thread time.

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

Facebook costs a phone 269 ms of main-thread work and 289 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 251 ms of main-thread work and 302 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.2 s on main-thread work while loading, 768 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

4 KiB could be saved by minifying JavaScript.

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

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.

Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalize content and ads, provide soci…”.

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

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

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

26 images have no width and height attributes, so the layout jumps as each one loads.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.1 MB in 122 requests on a phone: images 1.4 MB (38), scripts 918 KiB (38) and fonts 576 KiB (14). Under 2 MB keeps phones on slow connections fast.

lilith_ryhmakuva_transparent_web-768x491.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

5 images (545 KiB) are 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.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

2 images have no alt text, which hurts accessibility and image search.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 23 characters: “Lilith Osk - Lilith Osk”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link has no real href, so search engines can't follow it.

The homepage links to 53 pages on lilith.fi and 27 external pages.

There is no https://lilith.fi/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.

https://lilith.fi/palvelut-ja-tekijat, https://lilith.fi/nyt, https://lilith.fi/lilith25-historiikki, https://lilith.fi/lilithin-tahdet, https://lilith.fi/ajankohtaista/saannot and https://lilith.fi/category/ajankohtaista have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://lilith.fi/lilithin-tahdet, whose canonical is https://lilith.fi/category/lilithin-tahdet. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lilith.fi/nyt, https://lilith.fi/kauppapaikka, https://lilith.fi/yhteystiedot, https://lilith.fi/lilith25-historiikki, https://lilith.fi/lilithin-tahdet and https://lilith.fi/category/ajankohtaista have no <h1> headline, so visitors and search engines get no clear main topic.

https://lilith.fi/palvelut-ja-tekijat and https://lilith.fi/kauppapaikka have 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.

https://lilith.fi/nyt, https://lilith.fi/en, https://lilith.fi/lilith25-historiikki, https://lilith.fi/ajankohtaista/kaupunkikuvien-sarjasta-kuvataiteen-brandiksi-jussi-lahtinen, https://lilith.fi/lilithin-tahdet and https://lilith.fi/ajankohtaista/saannot and 1 other took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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