Programmable

Website review, no card needed

bulbious.nl logo

bulbious.nl website review

Visit site (opens in a new tab)Reviewed 10 November 202625 issues · 71 checks

This review found 25 issues worth fixing on bulbious.nl, 6 of them high impact, across 71 checks. The most urgent: render-blocking 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

Site score

86B

Closest competitors among Shopify stores

Compare side by side

One score from every part of this review. How it works

bulbious.nl (opens in a new tab)
Full-page screenshot of bulbious.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bulbious.nl at 0.8 s0.8 s
  2. bulbious.nl at 1.5 s1.5 s
  3. bulbious.nl at 2.3 s2.3 s
  4. bulbious.nl at 3.0 s3.0 s
  5. bulbious.nl at 3.8 s3.8 s
  6. bulbious.nl at 4.5 s4.5 s
  7. bulbious.nl at 5.3 s5.3 s
  8. bulbious.nl at 6.1 s6.1 s

Speed

6 to fix87

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 87

    87/100

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

  • Improve image delivery

    450 ms · 129 KiB

    4 images could be 129 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, Cloudflare CDN and sqa-api.com), adding 355 KiB and 541 ms of main-thread time.

  • Shopify adds 521 ms

    521 ms

    Shopify costs a phone 521 ms of main-thread work and 326 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

    450 ms · 66 KiB

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

  • Reduce unused JavaScript

    150 ms · 95 KiB

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

  • Legacy JavaScript

    7 KiB

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

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

2 checks passed

  • Main-thread work: 1.8 s

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

  • Server response: 39 ms

    39 ms

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

Core Web Vitals

2 to fix100

  • Largest Contentful Paint: 4.1 s

    4.1 s

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

  • Time to Interactive: 4.1 s

    4.1 s

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

9 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.1 s

    1.1 s

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

  • Real-user CLS: 0.00

    0.00

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

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

    336 ms

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

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100

  • About 0.6 g of CO₂ per visit

    0.55 g

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

4 checks passed

  • Page weight: 1.9 MB in 214 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 214 requests on a phone: other files 844 KiB (117), images 501 KiB (12) and scripts 383 KiB (48). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

2 to fixGoogle 9597

  • 11 text elements with low contrast

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Bloembollen kopen voor Tuin en Balkon | Bulbious | Plant the magic!”.

  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Bloembollen kopen bij Bulbious” and “Bloembollen voor elke tuin, balkon en terras”). One clear main headline is easier for people and search engines.

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

  • 57 internal links, 9 external

    The homepage links to 57 pages on bulbious.nl and 9 external pages.

5 checks passed

  • Canonical URL set

    The canonical URL is https://bulbious.nl/.

  • Structured data in place

    Structured data found: Organization 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://bulbious.nl/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 (897 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

7 to fix36

  • 1 linked page is broken

    Your homepage links to https://bulbious.nl/blogs/tips, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

    https://bulbious.nl/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://bulbious.nl/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://bulbious.nl/products/bijen-vlinderhuis-geel and https://bulbious.nl/products/bijen-vlinderhuis-paars all use the title “Bijen- & Vlinderhuis | Insectenhotel voor wilde bijen en vlinders | B…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://bulbious.nl/collections/all, https://bulbious.nl/pages/veelgestelde-vragen, https://bulbious.nl/customer_authentication/redirect and https://bulbious.nl/pages/bloemenhart-het-bloembollen-cadeau-hartstichting-bulbious have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://bulbious.nl/products/bijen-vlinderhuis-geel and https://bulbious.nl/products/bijen-vlinderhuis-paars use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://bulbious.nl/collections/all, https://bulbious.nl/pages/veelgestelde-vragen, https://bulbious.nl/pages/over-ons, https://bulbious.nl/pages/tuintips, https://bulbious.nl/customer_authentication/redirect and https://bulbious.nl/pages/bloemenhart-het-bloembollen-cadeau-hartstichting-bulbious and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://bulbious.nl/customer_authentication/redirect, https://bulbious.nl/pages/bloemenhart-het-bloembollen-cadeau-hartstichting-bulbious and https://bulbious.nl/products/bloemenhart-bloembollen-cadeau took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

1 checks passed

  • Canonical URLs point to themselves

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

Best practices

1 to fixGoogle 9693

  • 4 small tap targets

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

2 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67

  • No social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 844 words of copy

    The homepage carries about 844 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: “Shop hier!”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop” and “Shop hier!”.

  • 5 short forms

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

Privacy and tracking

1 to fix

  • 4 trackers load before any consent

    4

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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 bulbious.nl, 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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Ot Theme Sections · Vo Product Options · Smind Sections · Ot Section Builder · Smind App · Easy Content Builder · Eazy Swatches · Simple Marquee · Wizz Sticky Cart Add To Cart

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on bulbious.nl, including 8 speed issues, 3 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