Website review, no card needed

bidering.dk logo

bidering.dk website review

Visit site (opens in a new tab)Reviewed 11 November 202623 issues · 69 checks

This review found 23 issues worth fixing on bidering.dk, 5 of them high impact, across 69 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

Full-page screenshot of bidering.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix84
  • Render-blocking requests

    1.8 s

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

  • 3,006 HTML elements

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

  • Use efficient cache lifetimes

    750 ms · 280 KiB

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

  • Mobile performance score: 84

    84/100

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

  • Font display

    300 ms

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

  • Klarna adds 0 ms

    0 ms

    Klarna costs a phone 0 ms of main-thread work and 313 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

    228 KiB

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

  • Reduce unused CSS

    150 ms · 10 KiB

    About 10 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 71 ms. During a long task the page ignores taps.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Fonts, Klarna and klarnacdn.net), adding 648 KiB and 1 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 190 ms

    190 ms

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

Core Web Vitals

4 to fix82
  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “En bidering beroliger din baby. Den dulmer, når tænderne er…”.

  • Time to Interactive: 4.2 s

    4.2 s

    The page becomes fully interactive after 4.2 s. Good is under 3.8 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.

  • 10 images without width and height

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

3 checks passed
  • Speed Index: 3.4 s

    3.4 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 5 ms

    5 ms

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

Images and page weight

2 to fix83
  • 9 images below the first screen load straight away

    9 images further down the page (325 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    7 KiB

    1 image is downloaded at several times the size a phone draws it, for example Matchstick-Monkey-Abe-Bidering.jpg at 640 px wide, shown at 207 px. Resized copies would save about 7 KiB.

  • 2 images in older formats

    2 images (154 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 0.2 g of CO₂ per visit

    0.24 g

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

1 checks passed
  • Page weight: 859 KiB in 69 requests

    859 KiB

    Your homepage downloads 859 KiB in 69 requests on a phone: images 537 KiB (30), fonts 159 KiB (4) and scripts 61 KiB (18). That is a lean page.

Accessibility

1 to fixGoogle 9899
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 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. (186 elements).

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 238 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9283
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Bidering til baby i træ, naturgummi eller silikone | Find bideringe her!”.

  • 200 internal links, 236 external

    The homepage links to 200 pages on bidering.dk and 236 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Bidering”.

  • Canonical URL set

    The canonical URL is https://bidering.dk/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://bidering.dk/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://bidering.dk/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.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,643 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 13 linked pages hidden from search

    https://bidering.dk/betingelser, https://bidering.dk/vare/opry-bidering-blomst-blaa-oe65mm-1-stk, https://bidering.dk/vare/opry-bidering-hjerte-lilla-oe65mm-1-stk, https://bidering.dk/vare/opry-bidering-blomst-lys-rosa-oe65mm-1-stk, https://bidering.dk/vare/opry-bidering-blomst-groen-oe65mm-1-stk and https://bidering.dk/vare/opry-bidering-hjerte-gul-oe65mm-1-stk and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://bidering.dk/blog, https://bidering.dk/om, https://bidering.dk/betingelser, https://bidering.dk/vare/opry-bidering-blomst-blaa-oe65mm-1-stk, https://bidering.dk/vare/opry-bidering-hjerte-lilla-oe65mm-1-stk and https://bidering.dk/vare/opry-bidering-blomst-lys-rosa-oe65mm-1-stk and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://bidering.dk/om has 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 189 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 4 small tap targets

    4 of 15 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

4 to fix58
  • 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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 3,629 words of copy

    The homepage carries about 3,629 words of visible text.

2 checks passed
  • 186 calls to action

    The homepage has 186 calls to action, for example “Gå til shop”.

  • 2 short forms

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

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 bidering.dk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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

CMS
WordPress
Framework
jQuery
E-commerce
Shopify
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on bidering.dk, including 10 speed issues, 2 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