pehmea.fi website review

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

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

3 images could be 457 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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 600 ms).

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying CSS.

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tee juhlistasi unohtumattomat! Vuokraamme pehmytjäätelökone…”. Most of its time is element render delay (2.0 s).

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

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

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 5.4 MB in 51 requests on a phone: images 4.9 MB (21), fonts 319 KiB (1) and scripts 142 KiB (20). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example 5.jpg at 1,414 px wide, shown at 342 px. Resized copies would save about 2.2 MB.

5.jpg weighs 706 KiB. On a phone connection a single image that size takes seconds.

18 images (4.9 MB) 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.

17 images further down the page (4.8 MB) 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 1.53 g of CO₂e: 183.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.

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

Your title is 73 characters, so Google will cut it off around 60: “Koti - Vuokraa pehmytjäätelökone juhliin | Helppo ja hauska ohjelmanumero”.

There are 3 <h1> headlines (“Vuokraa pehmytjäätelökone juhliin | Helppo ja hau…”, “Tervetuloa Pehmea.fi- juhlat alkavat tästä!” and “Vuokraa pehmytjäätelökone juhliin | Helppo ja hau…”). One clear main headline is easier for people and search engines.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 9 pages on pehmea.fi and 3 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/ and https://www.pehmea.fi/en all use the title “Koti - Vuokraa pehmytjäätelökone juhliin | Helppo ja hauska ohjelmanu…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.pehmea.fi/yhteystiedot has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pehmea.fi/varaaminen and https://www.pehmea.fi/vuokrauslomake use the same meta description. A description written for each page earns more clicks.

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

We fetched 5 pages linked from your homepage 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.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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.