Website review, no card needed

metsola.co logo

metsola.co website review

Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 83 checks

This review found 38 issues worth fixing on metsola.co, 13 of them high impact, across 83 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.8 s1.6 sMay 23Oct 101.9 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.9 s
Jun 20, 20262.1 s
Jun 27, 20262.4 s
Aug 22, 20262.7 s
Sep 19, 20262.2 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
198 ms144 msMay 23Oct 10186 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026150 ms
May 30, 2026160 ms
Jun 6, 2026160 ms
Jun 13, 2026170 ms
Jun 20, 2026180 ms
Jun 27, 2026192 ms
Aug 22, 2026191 ms
Sep 26, 2026150 ms
Oct 3, 2026165 ms
Oct 10, 2026186 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

Full-page screenshot of metsola.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. metsola.co at 1.2 s1.2 s
  2. metsola.co at 2.3 s2.3 s
  3. metsola.co at 3.5 s3.5 s
  4. metsola.co at 4.6 s4.6 s
  5. metsola.co at 5.8 s5.8 s
  6. metsola.co at 6.9 s6.9 s
  7. metsola.co at 8.1 s8.1 s
  8. metsola.co at 9.3 s9.3 s

Speed

10 to fix42
  • Improve image delivery

    8.1 s · 4.9 MB

    109 images could be 4.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.1 s faster on a phone.

  • 22,480 HTML elements

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

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 9.0 s

    A phone's processor spends 9.0 s on main-thread work while loading, 2.4 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 (Cookiebot, Hubspot and Clarity and others), adding 1,017 KiB and 937 ms of main-thread time.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    450 ms · 105 KiB

    About 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Cookiebot adds 529 ms

    529 ms

    Cookiebot costs a phone 529 ms of main-thread work and 172 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.

  • Render-blocking requests

    500 ms

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

  • Shopify adds 26 ms

    26 ms

    Shopify costs a phone 26 ms of main-thread work and 560 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.

  • Use efficient cache lifetimes

    150 ms · 215 KiB

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

  • Reduce unused JavaScript

    87 KiB

    About 87 KiB of JavaScript is downloaded but never used on this page.

  • Legacy JavaScript

    32 KiB

    Polyfills 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 18 ms

    18 ms

    Your server sent the HTML in 18 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix44
  • Largest Contentful Paint: 22.9 s

    22.9 s

    Your largest element takes 22.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 39.3 s

    39.3 s

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

  • Speed Index: 12.2 s

    12.2 s

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

  • Total Blocking Time: 916 ms

    916 ms

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Tap response (INP) got 13% slower for real visitors

    +13%

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix60
  • Page weight: 101.5 MB in 334 requests

    101.5 MB

    Your homepage downloads 101.5 MB in 334 requests on a phone: media 91.8 MB (15), images 8.2 MB (199) and scripts 1.1 MB (87). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    kuva-48_7d2c0f43-9d24-4a20-acfe-29f56d913db9.jpg 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).

  • 2 images far larger than shown

    50 KiB

    2 images are downloaded at several times the size a phone draws them, for example IMG_0179_2ae644ec-3730-41a2-9a7c-86e0d5e01660.png at 349 px wide, shown at 86 px. Resized copies would save about 50 KiB.

  • 3 images below the first screen load straight away

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

  • About 28.8 g of CO₂ per visit

    28.77 g

    By the Sustainable Web Design model, a visit to your homepage emits about 28.77 g of CO₂e: 3452.5 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

10 to fixGoogle 9089
  • Scrollable region must have keyboard access (67 elements)

    Scrollable region must have keyboard access: 67 elements on the page fail this check, rated serious by axe-core.

  • 12 tap targets too small

    12 tap targets are too small or too close together to hit reliably with a finger.

  • 49 images without alt text

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

  • All page content should be contained by landmarks (4 elements)

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo 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 contentinfo landmark (1 element)

    Document should not have more than one contentinfo 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8572
  • No H1 headline

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

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Metsola | Finnish and high-quality children's clothing and accessories”.

  • Meta description is long (185 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://metsola.fi)”.

  • 1 link with vague text

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

  • 470 internal links, 0 external

    The homepage links to 470 pages on metsola.co and 0 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://metsola.co/.

  • 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://metsola.co/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,593 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://metsola.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 3 pages share a meta description

    https://metsola.co/collections/vauvat-bodyt, https://metsola.co/collections/vauvat-paidat and https://metsola.co/collections/vauvat-housut use the same meta description. A description written for each page earns more clicks.

  • 12 pages without an H1

    https://metsola.co/collections/kuoma-x-metsola, https://metsola.co/collections/you-make-me-happy-xmas-collection, https://metsola.co/collections/merinomallisto-a-world-full-of-smiles, https://metsola.co/collections/outlet, https://metsola.co/collections/metsolan-uutuuksia and https://metsola.co/collections/vauvat and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://metsola.co/collections/lahjaideat-vauvalle, https://metsola.co/collections/paahineet, https://metsola.co/collections/vauvan-pipot and https://metsola.co/collections/vauvat-bodyt took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 40 small tap targets

    40 of 183 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 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”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 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 1,599 words of copy

    The homepage carries about 1,599 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “FALL IN LOVE AND BUY HERE”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Buy by size/age”, “Shop by collection” and “Contact us”.

  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 184 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 5 of them by other companies (measured from a US location before any click).

  • 26 other companies contacted

    Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 metsola.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Easy Tag Gtm Data Layer · Minmaxify Order Limits · Cookiebot Cmp · Yotpo Loyalty Rewards · Judge Me Reviews · Cms Shopify · Announcement Bar Maker By Apphero · Omnisend · Selleasy · Wishlist Guru · Discos Smart Bogo Cart Upsell · klaviyo.com · truconversion.com · nice-team.net · hextom.com · hubapi.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on metsola.co, including 15 speed issues, 5 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25