Website review, no card needed

sinebrychoff.fi logo

sinebrychoff.fi website review

Visit site (opens in a new tab)Reviewed 31 October 202635 issues · 79 checks

This review found 35 issues worth fixing on sinebrychoff.fi, 14 of them high impact, across 79 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
1.5 s1.2 sMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
100 ms94 msMay 9Oct 2496 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202698 ms
May 16, 202699 ms
May 23, 202697 ms
May 30, 202698 ms
Jun 6, 202697 ms
Jun 13, 202696 ms
Jun 20, 202696 ms
Jun 27, 202696 ms
Jul 4, 202697 ms
Jul 11, 202697 ms
Jul 18, 202697 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202697 ms
Aug 29, 202696 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 202696 ms
Sep 26, 202698 ms
Oct 3, 202698 ms
Oct 10, 202699 ms
Oct 17, 202698 ms
Oct 24, 202696 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 sinebrychoff.fi (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sinebrychoff.fi at 0.5 s0.5 s
  2. sinebrychoff.fi at 0.9 s0.9 s
  3. sinebrychoff.fi at 1.4 s1.4 s
  4. sinebrychoff.fi at 1.8 s1.8 s
  5. sinebrychoff.fi at 2.3 s2.3 s
  6. sinebrychoff.fi at 2.8 s2.8 s
  7. sinebrychoff.fi at 3.2 s3.2 s
  8. sinebrychoff.fi at 3.7 s3.7 s

Speed

6 to fix57
  • Improve image delivery

    12.3 s · 2.7 MB

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

  • Use efficient cache lifetimes

    4.1 s · 903 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 57

    57/100

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

  • Reduce unused JavaScript

    300 ms · 70 KiB

    About 70 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 1,656 HTML elements

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

  • 2 long tasks on the main thread

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (carlsberggroup.com, carlsbergwebservices.com and Cloudinary), adding 238 KiB and 56 ms of main-thread time.

  • Legacy JavaScript

    11 KiB

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

  • Duplicated JavaScript

    10 KiB

    10 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 284 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 23.8 s

    23.8 s

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

  • Time to Interactive: 24.0 s

    24.0 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • Real-user CLS: 0.18

    0.18

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

  • Cumulative Layout Shift: 0.191

    0.191

    The layout shifts by 0.191 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

6 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 117 ms

    117 ms

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 495 ms

    495 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 57 ms

    57 ms

    Scripts block the page for only 57 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix43
  • Page weight: 5.0 MB in 93 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 93 requests on a phone: images 3.5 MB (15), other files 830 KiB (15) and scripts 386 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (1.2 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.

  • 9 images below the first screen load straight away

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

  • 4 images far larger than shown

    167 KiB

    4 images are downloaded at several times the size a phone draws them, for example crisp-radler-ananas-1920p-square-web.jpg at 1,390 px wide, shown at 390 px. Resized copies would save about 167 KiB.

  • About 1.4 g of CO₂ per visit

    1.41 g

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

Accessibility

5 to fixGoogle 9290
  • <svg> elements with an img or image role must have alternative text (6 elements)

    <svg> elements with an img or image role must have alternative text: 6 elements on the page fail this check, rated serious by axe-core.

  • 5 text elements with low contrast

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

  • 4 tap targets too small

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

5 to fixGoogle 10077
  • Title is short (12 characters)

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Sinebrychoff”, “Brewing Tomorrow” and “Crisp Radler Ananas 0,0%”). One clear main headline is easier for people and search engines.

  • Meta description is long (1676 characters)

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

  • No favicon declared

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

  • 162 internal links, 104 external

    The homepage links to 162 pages on sinebrychoff.fi and 104 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://sinebrychoff.fi/.

  • 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.carlsberggroup.com/sitemap/.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://sinebrychoff.fi/llms.txt (13 KiB, 124 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 15 pages share a meta description

    https://sinebrychoff.fi/yhtioe/lyhyesti, https://sinebrychoff.fi/yhtioe/strategiamme, https://sinebrychoff.fi/yhtioe/tarkoitus, https://sinebrychoff.fi/yhtioe/carlsbergin-historia, https://sinebrychoff.fi/yhtioe/carlsbergin-historia/carlsberg-saatio and https://sinebrychoff.fi/yhtioe/sinebrychoffin-historia and 9 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://sinebrychoff.fi/yhtioe/palaute has 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 81 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

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    9 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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.

  • No calls to action

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

  • No social proof

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

  • Only about 183 words

    The homepage has only about 183 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

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

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

2 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 3 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Employees
920
Founded
1819
Headquarters
Kerava

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on sinebrychoff.fi, including 13 speed issues, 5 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

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