Website review, no card needed

badaj.to logo

badaj.to website review

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

This review found 47 issues worth fixing on badaj.to, 19 of them high impact, across 88 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
3.6 s2.7 sMay 2Oct 173.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.8 s
May 16, 20262.9 s
May 23, 20263.0 s
May 30, 20263.1 s
Jun 6, 20263.2 s
Jun 13, 20263.3 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
130 ms122 msMay 2Oct 17127 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026124 ms
May 9, 2026123 ms
May 16, 2026124 ms
May 23, 2026125 ms
May 30, 2026126 ms
Jun 6, 2026127 ms
Jun 13, 2026128 ms
Jun 20, 2026128 ms
Jun 27, 2026128 ms
Jul 4, 2026129 ms
Jul 11, 2026128 ms
Jul 18, 2026128 ms
Jul 25, 2026127 ms
Aug 1, 2026125 ms
Aug 8, 2026126 ms
Aug 15, 2026126 ms
Aug 22, 2026127 ms
Aug 29, 2026127 ms
Sep 5, 2026127 ms
Sep 12, 2026127 ms
Sep 19, 2026127 ms
Sep 26, 2026127 ms
Oct 3, 2026127 ms
Oct 10, 2026127 ms
Oct 17, 2026127 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 badaj.to (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. badaj.to at 0.9 s0.9 s
  2. badaj.to at 1.8 s1.8 s
  3. badaj.to at 2.7 s2.7 s
  4. badaj.to at 3.6 s3.6 s
  5. badaj.to at 4.5 s4.5 s
  6. badaj.to at 5.4 s5.4 s
  7. badaj.to at 6.3 s6.3 s
  8. badaj.to at 7.2 s7.2 s

Speed

13 to fix25
  • Reduce unused JavaScript

    9.8 s · 1.7 MB

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

  • Use efficient cache lifetimes

    2.9 s · 1.8 MB

    148 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 25

    25/100

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

  • Main-thread work: 4.7 s

    A phone's processor spends 4.7 s on main-thread work while loading, 2.7 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 (YouTube, Google CDN and Facebook and others), adding 3.3 MB and 910 ms of main-thread time.

  • Improve image delivery

    1,015 KiB

    6 images could be 1,015 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    630 ms · 180 KiB

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

  • YouTube adds 312 ms

    312 ms

    YouTube costs a phone 312 ms of main-thread work and 973 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.

  • Legacy JavaScript

    350 ms · 58 KiB

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

  • Google CDN adds 256 ms

    256 ms

    Google CDN costs a phone 256 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.

  • 2,914 HTML elements

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

  • askspot.io adds 34 ms

    34 ms

    askspot.io costs a phone 34 ms of main-thread work and 724 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.

  • 17 long tasks on the main thread

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

  • Minify JavaScript

    30 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 52 but mobile only 25. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

12 to fix33
  • 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 CLS: 0.76

    0.76

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

  • Largest Contentful Paint: 31.2 s

    31.2 s

    Your largest element takes 31.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Używamy technologii takich jak pliki cookie do przechowywan…”.

  • Speed Index: 20.4 s

    20.4 s

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

  • Time to Interactive: 37.1 s

    37.1 s

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

  • Cumulative Layout Shift: 0.771

    0.771

    The layout shifts by 0.771 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

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

    +23%

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Total Blocking Time: 388 ms

    388 ms

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

  • 25 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

2 checks passed
  • Real-user INP: 121 ms

    121 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

Images and page weight

3 to fix53
  • Page weight: 6.8 MB in 241 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 241 requests on a phone: scripts 4.0 MB (98), images 1.8 MB (53) and other files 474 KiB (47). Under 2 MB keeps phones on slow connections fast.

  • 19 images below the first screen load straight away

    19 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images far larger than shown

    366 KiB

    3 images are downloaded at several times the size a phone draws them, for example choroby-cywilizacyjne-obrazek.jpg at 1,600 px wide, shown at 370 px. Resized copies would save about 366 KiB.

  • About 1.9 g of CO₂ per visit

    1.93 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8493
  • 4 text elements with low contrast

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

  • 80 images without alt text

    80 images have no alt text, which hurts accessibility and image search.

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

  • Zoom is disabled

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

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

  • 37 links without text

    37 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

4 to fixGoogle 9275
  • No H1 headline

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

  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “badaj.to Laboratoria Medyczne | Badania krwi i diagnostyka laboratoryjna”.

  • Meta description is short (56 characters)

    Your meta description is only 56 characters: “Kup swoje badania online. Taniej, szybciej, bez kolejek.”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 335 internal links, 24 external

    The homepage links to 335 pages on badaj.to and 24 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://badaj.to/.

  • Structured data in place

    Structured data found: BreadcrumbList, MedicalOrganization, Organization and WebPage.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://badaj.to/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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://badaj.to/llms.txt (195 KiB, 1 link), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 10 pages without a meta description

    https://badaj.to/punkty-pobran, https://badaj.to/poznaj-nas/o-nas, https://badaj.to/kontakt, https://badaj.to/kategorie-produktow/pakiety-badan, https://badaj.to/kategorie-produktow/oferta-specjalna and https://badaj.to/uslugi-dodatkowe/badania-z-zamrozonego-materialu and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://badaj.to/badania-krwi-w-domu has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 198 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Another code is already utilizing YouTube API, GTM4WP plugin can not load YouTube tracking!”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 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,459 words of copy

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

3 checks passed
  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

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 Clarity (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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 1 of them by other companies (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 badaj.to, 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
E-commerce
WooCommerce
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 badaj.to, including 25 speed issues, 4 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