Website review, no card needed
begroup.fi website review
Visit site (opens in a new tab)Reviewed 22 October 202639 issues · 90 checks
This review found 39 issues worth fixing on begroup.fi, 11 of them high impact, across 90 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 697 ms |
| May 9, 2026 | 707 ms |
| May 16, 2026 | 760 ms |
| May 23, 2026 | 733 ms |
| May 30, 2026 | 705 ms |
| Jun 6, 2026 | 654 ms |
| Jun 13, 2026 | 570 ms |
| Jun 20, 2026 | 556 ms |
| Jun 27, 2026 | 561 ms |
| Jul 4, 2026 | 533 ms |
| Jul 11, 2026 | 529 ms |
| Jul 18, 2026 | 508 ms |
| Jul 25, 2026 | 506 ms |
| Aug 1, 2026 | 510 ms |
| Aug 8, 2026 | 543 ms |
| Aug 15, 2026 | 550 ms |
| Aug 22, 2026 | 530 ms |
| Aug 29, 2026 | 530 ms |
| Sep 5, 2026 | 499 ms |
| Sep 12, 2026 | 511 ms |
| Sep 19, 2026 | 537 ms |
| Sep 26, 2026 | 531 ms |
| Oct 3, 2026 | 548 ms |
| Oct 10, 2026 | 553 ms |
| Oct 17, 2026 | 512 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 115 ms |
| May 9, 2026 | 126 ms |
| May 16, 2026 | 128 ms |
| May 23, 2026 | 132 ms |
| May 30, 2026 | 125 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 116 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 114 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 108 ms |
| Aug 29, 2026 | 109 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 116 ms |
| Oct 3, 2026 | 118 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 115 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
Speed
Reduce unused JavaScript
1.1 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.0 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.0 s.
Mobile performance score: 65
65/100Your mobile performance score is 65 (desktop: 78). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (serviceform.com, Google Tag Manager and Ontame and others), adding 1.9 MB and 805 ms of main-thread time.
Use efficient cache lifetimes
845 KiB20 files are served with short cache lifetimes, so returning visitors download them again (845 KiB).
serviceform.com adds 471 ms
471 msserviceform.com costs a phone 471 ms of main-thread work and 1.4 MB 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.
Legacy JavaScript
350 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
2,779 HTML elements
The page has 2,779 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 170 ms
170 msGoogle Tag Manager costs a phone 170 ms of main-thread work and 364 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.
Improve image delivery
243 KiB17 images could be 243 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
150 ms · 81 KiBAbout 81 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 204 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 13 KiB13 KiB could be saved by minifying JavaScript.
Minify CSS
20 KiB20 KiB could be saved by minifying CSS.
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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 895 ms of it running JavaScript. That is comfortably low.
Server response: 123 ms
123 msYour server sent the HTML in 123 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 20.7 s
20.7 sThe page becomes fully interactive after 20.7 s. Good is under 3.8 s.
Largest Contentful Paint: 7.2 s
7.2 sYour largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HANKIMME, JALOSTAMME JA TOIMITAMME TERÄKSET SUORAAN SINUN T…”.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 261 ms
261 msScripts block taps and scrolling for 261 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 115 ms to 115 ms 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: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 129 ms
129 msReal visitors wait 129 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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 360 ms
360 msReal visitors wait 360 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 133 requests
3.9 MBYour homepage downloads 3.9 MB in 133 requests on a phone: scripts 2.2 MB (47), images 1.3 MB (42) and other files 321 KiB (29). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (679 KiB) 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.
About 1.1 g of CO₂ per visit
1.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Elements must only use permitted ARIA attributes (4 elements)
Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (85 characters)
Your title is 85 characters, so Google will cut it off around 60: “Teräs, ruostumaton teräs & alumiini - Tervetuloa BE Group Suomen sivuille! | BE-Group”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (528 characters)
Your meta description is 528 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
238 internal links, 7 external
The homepage links to 238 pages on begroup.fi and 7 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Hankimme, jalostamme ja toimitamme teräkset suoraan sinun tarpeisiisi”.
Canonical URL set
The canonical URL is https://www.begroup.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.begroup.fi/sitemap.axd.
AI search readiness
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.
Some text only appears after JavaScript runs
35%The HTML your server sends has 703 of the 2,017 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.begroup.fi/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.
1 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.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 173 found) and read each the way a search engine does.
7 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.
Every page has an H1
Each page we checked has a main headline.
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
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://dash.serviceform.com/embed/chat.css?10' from origin 'https://www.begroup.fi' has b…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
42 of 52 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.
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.
Local business without LocalBusiness data
Your homepage shows a map 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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,017 words of copy
The homepage carries about 2,017 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
12 other companies contacted
Loading the homepage contacts 12 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 begroup.fi, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Litium
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on begroup.fi, including 15 speed issues, 3 SEO issues and 6 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.