Website review, no card needed

bdswiss.com logo

bdswiss.com website review

Visit site (opens in a new tab)Reviewed 25 October 202647 issues · 68 checks

This review found 47 issues worth fixing on bdswiss.com, 19 of them high impact, across 68 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
44.6 s2.6 sMay 2Oct 1039.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20268.0 s
May 16, 20267.7 s
May 23, 20267.8 s
May 30, 20268.2 s
Jun 6, 20267.4 s
Jun 13, 20268.2 s
Jun 20, 20268.2 s
Jun 27, 20268.7 s
Jul 4, 20268.7 s
Jul 11, 20268.4 s
Jul 18, 20268.6 s
Jul 25, 20268.3 s
Aug 1, 20269.0 s
Aug 8, 20269.2 s
Aug 15, 20269.0 s
Aug 22, 20269.2 s
Aug 29, 20268.6 s
Sep 5, 20269.3 s
Sep 12, 20269.0 s
Sep 19, 20268.5 s
Sep 26, 20269.5 s
Oct 3, 202610.0 s
Oct 10, 202639.8 s
Real-visitor tap response (INP)75th percentile, phones
441 ms240 msMay 23Oct 17385 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026390 ms
May 30, 2026361 ms
Jun 6, 2026322 ms
Jun 13, 2026312 ms
Jun 20, 2026309 ms
Jun 27, 2026263 ms
Jul 4, 2026281 ms
Jul 11, 2026282 ms
Jul 18, 2026317 ms
Jul 25, 2026341 ms
Aug 1, 2026418 ms
Aug 8, 2026403 ms
Aug 15, 2026338 ms
Aug 22, 2026338 ms
Aug 29, 2026290 ms
Sep 5, 2026310 ms
Sep 12, 2026302 ms
Sep 19, 2026265 ms
Sep 26, 2026276 ms
Oct 3, 2026277 ms
Oct 10, 2026322 ms
Oct 17, 2026385 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 bdswiss.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bdswiss.com at 1.5 s1.5 s
  2. bdswiss.com at 2.9 s2.9 s
  3. bdswiss.com at 4.4 s4.4 s
  4. bdswiss.com at 5.9 s5.9 s
  5. bdswiss.com at 7.3 s7.3 s
  6. bdswiss.com at 8.8 s8.8 s
  7. bdswiss.com at 10.2 s10.2 s
  8. bdswiss.com at 11.7 s11.7 s

Speed

11 to fix26
  • Reduce unused JavaScript

    10.7 s · 2.0 MB

    About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.7 s faster on a phone.

  • Use efficient cache lifetimes

    4.8 s · 848 KiB

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

  • Render-blocking requests

    4.4 s

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

  • Mobile performance score: 26

    26/100

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

  • Main-thread work: 5.5 s

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

  • 16 long tasks on the main thread

    16 long tasks block the main thread while loading, the longest for 2.3 s. During a long task the page ignores taps.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, b-cdn.net and chargebee.com and others), adding 1.9 MB and 1.4 s of main-thread time.

  • Legacy JavaScript

    750 ms · 108 KiB

    Polyfills for old browsers add 108 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 750 ms faster on a phone.

  • Google Tag Manager adds 590 ms

    590 ms

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

  • Minify JavaScript

    450 ms · 57 KiB

    57 KiB could be saved by minifying JavaScript.

  • b-cdn.net adds 335 ms

    335 ms

    b-cdn.net costs a phone 335 ms of main-thread work and 207 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

    280 ms · 45 KiB

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

  • Improve image delivery

    150 ms · 41 KiB

    1 image could be 41 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

10 to fix50
  • 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.

  • Real-user FCP: 49.0 s

    49.0 s

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

  • First Contentful Paint: 14.3 s

    14.3 s

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

  • Largest Contentful Paint: 38.2 s

    38.2 s

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

  • Speed Index: 21.6 s

    21.6 s

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

  • Time to Interactive: 38.2 s

    38.2 s

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

  • Total Blocking Time: 3.1 s

    3.1 s

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

  • Real-user INP: 407 ms

    407 ms

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

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

    +216%

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

  • 1 image without width and height

    1 image 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-17, real Chrome visitors' tap response (inp) went from 390 ms to 385 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Real-user TTFB: 598 ms

    598 ms

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

  • Cumulative Layout Shift: 0.012

    0.012

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

Images and page weight

1 to fix33
  • Page weight: 5.5 MB in 68 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 68 requests on a phone: scripts 5.2 MB (27), other files 145 KiB (29) and stylesheets 50 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.55 g

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

Accessibility

6 to fixGoogle 8379
  • ARIA progressbar nodes must have an accessible name (1 element)

    ARIA progressbar nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 3 text elements with low contrast

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

1 checks passed
  • 11 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 16 WCAG 2.2 A/AA and best-practice rules on the phone render: 11 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 9152
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (24 characters)

    Your title is only 24 characters: “BDSwiss - Account Portal”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://dashboard.bdswiss.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at dashboard.bdswiss.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

AI search readiness

1 to fix69
  • 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://dashboard.bdswiss.com/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.

Best practices

3 to fixGoogle 7387
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 0 words

    The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 5 cookies set on arrival

    5

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

  • 28 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
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 47 issues on bdswiss.com, including 21 speed issues, 9 SEO issues and 5 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