Website review, no card needed

bohemia.net logo

bohemia.net website review

Visit site (opens in a new tab)Reviewed 30 October 202638 issues · 77 checks

This review found 38 issues worth fixing on bohemia.net, 15 of them high impact, across 77 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
4.0 s2.0 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.8 s
Aug 15, 20263.1 s
Aug 22, 20263.3 s
Aug 29, 20263.4 s
Sep 5, 20263.5 s
Sep 12, 20263.5 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.6 s
Oct 10, 20263.7 s
Oct 17, 20263.7 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
271 ms97 msMay 9Oct 24229 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026117 ms
May 16, 2026118 ms
May 23, 2026121 ms
May 30, 2026122 ms
Jun 6, 2026120 ms
Jun 13, 2026120 ms
Jun 20, 2026119 ms
Jun 27, 2026118 ms
Jul 4, 2026119 ms
Jul 11, 2026121 ms
Jul 18, 2026119 ms
Jul 25, 2026120 ms
Aug 1, 2026132 ms
Aug 8, 2026162 ms
Aug 15, 2026211 ms
Aug 22, 2026246 ms
Aug 29, 2026251 ms
Sep 5, 2026248 ms
Sep 12, 2026237 ms
Sep 19, 2026230 ms
Sep 26, 2026233 ms
Oct 3, 2026230 ms
Oct 10, 2026230 ms
Oct 17, 2026231 ms
Oct 24, 2026229 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 bohemia.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bohemia.net at 0.8 s0.8 s
  2. bohemia.net at 1.6 s1.6 s
  3. bohemia.net at 2.5 s2.5 s
  4. bohemia.net at 3.3 s3.3 s
  5. bohemia.net at 4.1 s4.1 s
  6. bohemia.net at 4.9 s4.9 s
  7. bohemia.net at 5.8 s5.8 s
  8. bohemia.net at 6.6 s6.6 s

Speed

8 to fix39
  • Improve image delivery

    7.4 s · 7.6 MB

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

  • Reduce unused JavaScript

    1.5 s · 321 KiB

    About 321 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Main-thread work: 16.1 s

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

  • Mobile performance score: 39

    39/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, cookiehub.eu and cookiehub.net and others), adding 72.7 MB and 438 ms of main-thread time.

  • bistudio.com adds 0 ms

    0 ms

    bistudio.com costs a phone 0 ms of main-thread work and 72.2 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.

  • Use efficient cache lifetimes

    450 ms · 391 KiB

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

  • Google Tag Manager adds 378 ms

    378 ms

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

  • Font display

    250 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    10 KiB

    About 10 KiB of CSS is downloaded but never applied on this page.

  • 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: 11 ms

    11 ms

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

Core Web Vitals

12 to fix33
  • 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: 26.3 s

    26.3 s

    Your largest element takes 26.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cookies help us improve the site and keep our advertising r…”.

  • Time to Interactive: 26.9 s

    26.9 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Total Blocking Time: 930 ms

    930 ms

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user INP: 369 ms

    369 ms

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

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

    +96%

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

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

    +64%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

2 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Cumulative Layout Shift: 0.02

    0.02

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

Images and page weight

5 to fix14
  • Page weight: 74.6 MB in 89 requests

    74.6 MB

    Your homepage downloads 74.6 MB in 89 requests on a phone: media 63.9 MB (14), images 9.7 MB (29) and scripts 806 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • 14 images far larger than shown

    5.1 MB

    14 images are downloaded at several times the size a phone draws them, for example 2b572e56-59b0-4644-bf53-6fa311230ebb-1 at 2,560 px wide, shown at 358 px. Resized copies would save about 5.1 MB.

  • 3 images over 500 KB

    3 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.

  • 8 images in older formats

    8 images (4.7 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.

  • An image on the first screen is lazy-loaded

    10ea0ee2-5c53-4100-9385-511568523d39-1 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).

  • About 21.2 g of CO₂ per visit

    21.15 g

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

Accessibility

4 to fixGoogle 8994
  • 32 tap targets too small

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

  • 6 text elements with low contrast

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

  • 1 link without text

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

  • Headings should not be empty (9 elements)

    Headings should not be empty: 9 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • 10 H1 headlines

    There are 10 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

  • 31 internal links, 35 external

    The homepage links to 31 pages on bohemia.net and 35 external pages.

7 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Bohemia Interactive — creators of Arma, DayZ, and Vigor. Unleash your imagination with tools made for creators and comm…”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Bohemia Interactive – Official Website”.

  • Canonical URL set

    The canonical URL is https://bohemia.net/en/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • 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://bohemia.net/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.bohemia.net/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.

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.

  • 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 (415 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://www.bohemia.net/en and / all use the title “Bohemia Interactive – Official Website”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.bohemia.net/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.bohemia.net/en/games/armareforger, https://www.bohemia.net/en/games/dayz, https://www.bohemia.net/en/games/silica and https://www.bohemia.net/en/games/arma3 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 19 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 31 small tap targets

    31 of 76 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”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 3 trust badges. 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 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 506 words of copy

    The homepage carries about 506 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN US” and “BUY”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “SHOP”, “Join us” and “Buy”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 bohemia.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Employees
350
Founded
1999
Headquarters
Mníšek pod Brdy

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 bohemia.net, including 20 speed issues, 1 SEO issue and 2 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