Website review, no card needed

bbq-plancha.nl logo

bbq-plancha.nl website review

Visit site (opens in a new tab)Reviewed 8 November 202628 issues · 81 checks

This review found 28 issues worth fixing on bbq-plancha.nl, 9 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
987 ms716 msMay 16Oct 31814 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026748 ms
May 23, 2026758 ms
May 30, 2026756 ms
Jun 6, 2026747 ms
Jun 13, 2026753 ms
Jun 20, 2026752 ms
Jun 27, 2026758 ms
Jul 4, 2026752 ms
Jul 11, 2026777 ms
Jul 18, 2026803 ms
Jul 25, 2026818 ms
Aug 1, 2026840 ms
Aug 8, 2026823 ms
Aug 15, 2026825 ms
Aug 22, 2026844 ms
Aug 29, 2026869 ms
Sep 5, 2026926 ms
Sep 12, 2026947 ms
Sep 19, 2026956 ms
Sep 26, 2026941 ms
Oct 3, 2026862 ms
Oct 10, 2026820 ms
Oct 17, 2026812 ms
Oct 24, 2026809 ms
Oct 31, 2026814 ms
Real-visitor tap response (INP)75th percentile, phones
88 ms80 msMay 16Oct 3181 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202686 ms
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202687 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202686 ms
Jul 18, 202686 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 202687 ms
Aug 22, 202686 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202686 ms
Oct 3, 202684 ms
Oct 10, 202682 ms
Oct 17, 202682 ms
Oct 24, 202681 ms
Oct 31, 202681 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 bbq-plancha.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bbq-plancha.nl at 0.4 s0.4 s
  2. bbq-plancha.nl at 0.8 s0.8 s
  3. bbq-plancha.nl at 1.3 s1.3 s
  4. bbq-plancha.nl at 1.7 s1.7 s
  5. bbq-plancha.nl at 2.1 s2.1 s
  6. bbq-plancha.nl at 2.5 s2.5 s
  7. bbq-plancha.nl at 2.9 s2.9 s
  8. bbq-plancha.nl at 3.4 s3.4 s

Speed

10 to fix58
  • Reduce unused JavaScript

    1.4 s · 261 KiB

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

  • Main-thread work: 4.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, vanchat.app and JSDelivr CDN and others), adding 1.8 MB and 1.1 s of main-thread time.

  • Mobile performance score: 58

    58/100

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

  • Shopify adds 834 ms

    834 ms

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

    400 ms · 209 KiB

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

  • Improve image delivery

    300 ms · 159 KiB

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

  • Reduce unused CSS

    300 ms · 35 KiB

    About 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 2,514 HTML elements

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

  • vanchat.app adds 119 ms

    119 ms

    vanchat.app costs a phone 119 ms of main-thread work and 331 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.

  • 3 long tasks on the main thread

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

  • Duplicated JavaScript

    50 ms · 16 KiB

    16 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    50 ms

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

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

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

    13 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 13.8 s

    13.8 s

    Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Compañero plancha in een winters landschap — Black Friday”.

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Time to Interactive: 13.9 s

    13.9 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • 11 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.8 s 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.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 INP: 94 ms

    94 ms

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

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

    380 ms

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

  • Total Blocking Time: 107 ms

    107 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 398 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 398 requests on a phone: scripts 1.2 MB (158), other files 1.2 MB (174) and images 663 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    1.01 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9296
  • Form elements must have labels (2 elements)

    Form elements must have labels: 2 elements on the page fail this check, rated critical by axe-core.

  • 53 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

3 to fixGoogle 10086
  • Meta description is long (169 characters)

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

  • No robots.txt

    There is no robots.txt at bbq-plancha.nl/robots.txt, the first file search crawlers ask for.

  • One H1 headline

    Your <h1> is empty.

  • 166 internal links, 10 external

    The homepage links to 166 pages on bbq-plancha.nl and 10 external pages.

5 checks passed
  • Title: 50 characters

    Your title is a healthy 50 characters: “BBQ Plancha.nl - RJR Royal Living – BBQ-Plancha.nl”.

  • Canonical URL set

    The canonical URL is https://bbq-plancha.nl/.

  • Structured data in place

    Structured data found: Organization, Product and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://bbq-plancha.nl/sitemap.xml.

AI search readiness

100
2 checks passed
  • 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 (1,733 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://bbq-plancha.nl/collections/bbq-plancha-cadeaubonnen has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://bbq-plancha.nl/collections/smokeless-bbq-plancha-grills took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

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

  • 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 10 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 1,029 words of copy

    The homepage carries about 1,029 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 9 short forms

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

  • Social proof on the page

    Social proof on the homepage: 126 testimonial or review blocks and a star rating.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 bbq-plancha.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Sami Wholesale · Vanchat

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 28 issues on bbq-plancha.nl, including 15 speed issues, 3 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