Website review, no card needed
suomalainen.com website review
Visit site (opens in a new tab)Reviewed 4 November 202644 issues · 96 checks
This review found 44 issues worth fixing on suomalainen.com, 20 of them high impact, across 96 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81B- #39,174 of 115,641 reviewed websitesbeats 60%
- #26,443 of 66,528 online storesbeats 54%
- #25,527 of 60,792 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 122 ms |
| May 23, 2026 | 122 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 119 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 119 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 118 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 119 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 120 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.1 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Reduce unused JavaScript
1.4 s · 1,023 KiBAbout 1,023 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
giosg.com adds 2.2 s
2.2 sgiosg.com costs a phone 2.2 s of main-thread work and 1.4 MB 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.
Render-blocking requests
2.0 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
11,162 HTML elements
The page has 11,162 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 8.1 s
A phone's processor spends 8.1 s on main-thread work while loading, 5.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (giosg.com, Yotpo and cookieinformation.com and others), adding 1.8 MB and 2.4 s of main-thread time.
Use efficient cache lifetimes
150 ms · 1.3 MB23 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
400 ms · 62 KiBAbout 62 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 400 ms faster on a phone.
Improve image delivery
150 ms · 259 KiB26 images could be 259 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 303 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 14 KiB14 KiB could be saved by minifying JavaScript.
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 87 ms
87 msYour server sent the HTML in 87 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.5 s
8.5 sYour largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Käytämme sivustollamme evästeitä tarjotaksemme sinulle enti…”.
Time to Interactive: 20.4 s
20.4 sThe page becomes fully interactive after 20.4 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 536 ms
536 msScripts block taps and scrolling for 536 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 122 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 175 ms
175 msReal visitors wait 175 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 499 ms
499 msReal visitors wait 499 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 369 requests
5.5 MBYour homepage downloads 5.5 MB in 369 requests on a phone: scripts 2.0 MB (67), media 1.2 MB (1) and images 1.2 MB (87). Under 2 MB keeps phones on slow connections fast.
30 images far larger than shown
2.4 MB30 images are downloaded at several times the size a phone draws them, for example 9789510526194_1-tunteiden-metsa_1024x1024.jpg at 882 px wide, shown at 146 px. Resized copies would save about 2.4 MB.
23 images below the first screen load straight away
23 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.55 g of CO₂e: 186.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
Interactive controls must not be nested (10 elements)
Interactive controls must not be nested: 10 elements on the page fail this check, rated serious by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
ARIA toggle fields must have an accessible name (1 element)
ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Document should not have more than one banner landmark (1 element)
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)
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 63 images in the HTML carry an alt attribute.
56 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 71 WCAG 2.2 A/AA and best-practice rules on the phone render: 56 passed and 15 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
106 links crawlers can't follow
106 links have no real href, so search engines can't follow them.
Meta description is long (320 characters)
Your meta description is 320 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Book, Organization and Product) but with 1 problem, for example “ld+json block 27 is not valid JSON (Expected ',' or '}' after property value in JSON at position)”.
911 internal links, 1 external
The homepage links to 911 pages on suomalainen.com and 1 external page.
6 checks passed
One H1 headline
Your main headline reads: “Suomalainen.com .cls-vpollo-1{fill:#000}.cls-vpollo-1,.cls-vpollo-2,.cls-vpollo-3,.cls-vpollo-4{stroke-width:0}.cls-vpo…”.
Title: 41 characters
Your title is a healthy 41 characters: “Suomalainen Kirjakauppa | Suomalainen.com”.
Canonical URL set
The canonical URL is https://www.suomalainen.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.suomalainen.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (8,082 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.suomalainen.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without an H1
https://www.suomalainen.com/collections/syksy, https://www.suomalainen.com/collections/cozy-coloring-varityskirjat and https://www.suomalainen.com/collections/halloween have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
6 checks passed
Linked pages load
6 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 6 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
132 of 153 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 2,054 words of copy
The homepage carries about 2,054 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “New book releases” and “Book Nook”.
36 short forms
36 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Hotjar.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Tag Manager, LinkedIn Insight, Microsoft Ads and Microsoft Clarity (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
No consent tool detected
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.
28 other companies contacted
Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at suomalainen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
Company
- Employees
- 270
- Founded
- 1912
- Headquarters
- Kustannusosakeyhtiö Otava (1000)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on suomalainen.com, including 15 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.