Website review, no card needed
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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 8.0 s |
| May 16, 2026 | 7.7 s |
| May 23, 2026 | 7.8 s |
| May 30, 2026 | 8.2 s |
| Jun 6, 2026 | 7.4 s |
| Jun 13, 2026 | 8.2 s |
| Jun 20, 2026 | 8.2 s |
| Jun 27, 2026 | 8.7 s |
| Jul 4, 2026 | 8.7 s |
| Jul 11, 2026 | 8.4 s |
| Jul 18, 2026 | 8.6 s |
| Jul 25, 2026 | 8.3 s |
| Aug 1, 2026 | 9.0 s |
| Aug 8, 2026 | 9.2 s |
| Aug 15, 2026 | 9.0 s |
| Aug 22, 2026 | 9.2 s |
| Aug 29, 2026 | 8.6 s |
| Sep 5, 2026 | 9.3 s |
| Sep 12, 2026 | 9.0 s |
| Sep 19, 2026 | 8.5 s |
| Sep 26, 2026 | 9.5 s |
| Oct 3, 2026 | 10.0 s |
| Oct 10, 2026 | 39.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 390 ms |
| May 30, 2026 | 361 ms |
| Jun 6, 2026 | 322 ms |
| Jun 13, 2026 | 312 ms |
| Jun 20, 2026 | 309 ms |
| Jun 27, 2026 | 263 ms |
| Jul 4, 2026 | 281 ms |
| Jul 11, 2026 | 282 ms |
| Jul 18, 2026 | 317 ms |
| Jul 25, 2026 | 341 ms |
| Aug 1, 2026 | 418 ms |
| Aug 8, 2026 | 403 ms |
| Aug 15, 2026 | 338 ms |
| Aug 22, 2026 | 338 ms |
| Aug 29, 2026 | 290 ms |
| Sep 5, 2026 | 310 ms |
| Sep 12, 2026 | 302 ms |
| Sep 19, 2026 | 265 ms |
| Sep 26, 2026 | 276 ms |
| Oct 3, 2026 | 277 ms |
| Oct 10, 2026 | 322 ms |
| Oct 17, 2026 | 385 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
How it loaded on a phone
1.5 s
2.9 s
4.4 s
5.9 s
7.3 s
8.8 s
10.2 s
11.7 s
Speed
Reduce unused JavaScript
10.7 s · 2.0 MBAbout 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 KiB17 files are served with short cache lifetimes, so returning visitors download them again (848 KiB).
Render-blocking requests
4.4 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.4 s.
Mobile performance score: 26
26/100Your 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 KiBPolyfills 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 msGoogle 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 KiB57 KiB could be saved by minifying JavaScript.
b-cdn.net adds 335 ms
335 msb-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 KiBAbout 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 KiB1 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 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 sReal 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 sThe 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 sYour 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 sVisually, the page fills in at 21.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 38.2 s
38.2 sThe page becomes fully interactive after 38.2 s. Good is under 3.8 s.
Total Blocking Time: 3.1 s
3.1 sScripts 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 msReal 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.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user TTFB: 598 ms
598 msReal visitors wait 598 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 68 requests
5.5 MBYour 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 gBy 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
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
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
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
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
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
4 trackers load before any consent
4Before 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
5Opening 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.