hartman.fi website review

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

About 177 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, videoly.co and Cloudflare CDN and others), adding 720 KiB and 652 ms of main-thread time.

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

20 KiB could be saved by minifying CSS.

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

5 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Polyfills for old browsers add 9 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.

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.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Syystarjouksia Hartmanilta KUUKAUDEN TARJOUSLEHTI”.

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

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

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

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

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

Real visitors wait 462 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

21 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' tap response (inp) went from 179 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.6 MB in 390 requests on a phone: scripts 1.3 MB (269), images 788 KiB (61) and stylesheets 220 KiB (17). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (170 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.74 g of CO₂e: 88.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

No meta description, so Google writes its own snippet from whatever text it finds.

94 links have no real href, so search engines can't follow them.

Your title is only 19 characters: “Rautakauppa Hartman”. Between 30 and 65 characters leaves room to say what you do and for whom.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 855 pages on hartman.fi and 8 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

/fi/stores/store/redirect/___store/sv/___from_store/fi/uenc/aHR0cHM6Ly93d3cuaGFydG1hbi5maS9zdi8~, /fi/english, /sv/danish, /fi/yhteystiedot, /fi/tuotemerkki and /fi/rautakauppa and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

Chrome logged issues while loading the page (“Cookie”).

1 link go through two or more redirects, for example https://www.hartman.fi/fi/stores/store/redirect/___store/sv/___from_store/fi/uenc/aHR0cHM6Ly93d3cuaGFydG1hbi5maS9zdi8~/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

hartman.fi has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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 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 1,434 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 17 cookies, 1 of them by other companies (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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.