Website review, no card needed

humblebee.se logo

humblebee.se website review

Visit site (opens in a new tab)Reviewed 20 October 202633 issues · 74 checks

This review found 33 issues worth fixing on humblebee.se, 5 of them high impact, across 74 checks. The most urgent: page weight: 13.6 MB in 37 requests. 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

Full-page screenshot of humblebee.se (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. humblebee.se at 0.4 s0.4 s
  2. humblebee.se at 0.8 s0.8 s
  3. humblebee.se at 1.1 s1.1 s
  4. humblebee.se at 1.5 s1.5 s
  5. humblebee.se at 1.9 s1.9 s
  6. humblebee.se at 2.3 s2.3 s
  7. humblebee.se at 2.6 s2.6 s
  8. humblebee.se at 3.0 s3.0 s

Speed

9 to fix85
  • Use efficient cache lifetimes

    11.7 MB

    6 files are served with short cache lifetimes, so returning visitors download them again (11.7 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and website-files.com and others), adding 13.5 MB and 585 ms of main-thread time.

  • website-files.com adds 76 ms

    76 ms

    website-files.com costs a phone 76 ms of main-thread work and 12.7 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.

  • Mobile performance score: 85

    85/100

    Your mobile performance score is 85 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    850 ms

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

  • Improve image delivery

    481 KiB

    4 images could be 481 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    435 KiB

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

  • Google Tag Manager adds 253 ms

    253 ms

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

  • Google CDN adds 124 ms

    124 ms

    Google CDN costs a phone 124 ms of main-thread work and 347 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.

  • Reduce unused CSS

    150 ms · 26 KiB

    About 26 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.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    17 KiB

    Polyfills for old browsers add 17 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.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 462 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

5 to fix83
  • Time to Interactive: 8.9 s

    8.9 s

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

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

  • Speed Index: 3.7 s

    3.7 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 11 images without width and height

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

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

2 checks passed
  • Total Blocking Time: 147 ms

    147 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 13.6 MB in 37 requests

    13.6 MB

    Your homepage downloads 13.6 MB in 37 requests on a phone: media 11.6 MB (2), scripts 943 KiB (13) and images 793 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (90 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.

  • 1 image below the first screen load straight away

    1 image further down the page (52 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.8 g of CO₂ per visit

    3.84 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8993
  • 23 text elements with low contrast

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

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 25 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 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 42 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: 42 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9285
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (199 characters)

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

  • Structured data has 1 problem

    Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 1)”.

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

  • 31 internal links, 4 external

    The homepage links to 31 pages on humblebee.se and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “What's your next move?”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Welcome to Humblebee - a digital studio in Sweden”.

  • 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.humblebee.se/sitemap.xml.

AI search readiness

2 to fix75
  • 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

    42%

    The HTML your server sends has 356 of the 853 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

1 to fix95
  • 3 pages without an H1

    https://www.humblebee.se/programs/coventures-program, https://www.humblebee.se/programs/customer-experience-program and https://www.humblebee.se/programs/strategic-products-program have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.humblebee.se/programs and https://www.humblebee.se/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 20 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 10087
  • 20 small tap targets

    20 of 36 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

3 to fix60
  • 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.

  • Thin social proof

    Social proof on the homepage: 8 customer or partner logos. 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 853 words of copy

    The homepage carries about 853 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Book a meeting” and “Apply”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Webflow
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 33 issues on humblebee.se, including 14 speed issues, 4 SEO issues and 3 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