Website review, no card needed

medigroup.rs logo

medigroup.rs website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 84 checks

This review found 32 issues worth fixing on medigroup.rs, 17 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
1.9 s1.5 sMay 30Nov 141.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Nov 7, 20261.8 s
Nov 14, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
115 ms96 msMay 30Nov 1499 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026110 ms
Jun 6, 2026111 ms
Jun 13, 2026112 ms
Jun 20, 2026113 ms
Jun 27, 2026113 ms
Jul 4, 2026113 ms
Jul 11, 2026112 ms
Jul 18, 2026111 ms
Jul 25, 2026109 ms
Aug 1, 2026106 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026104 ms
Sep 5, 2026105 ms
Sep 12, 2026104 ms
Sep 19, 2026103 ms
Sep 26, 2026102 ms
Oct 3, 2026101 ms
Oct 10, 2026100 ms
Oct 17, 202699 ms
Oct 24, 202699 ms
Oct 31, 202699 ms
Nov 7, 202698 ms
Nov 14, 202699 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 medigroup.rs (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. medigroup.rs at 1.9 s1.9 s
  2. medigroup.rs at 3.7 s3.7 s
  3. medigroup.rs at 5.6 s5.6 s
  4. medigroup.rs at 7.5 s7.5 s
  5. medigroup.rs at 9.3 s9.3 s
  6. medigroup.rs at 11.2 s11.2 s
  7. medigroup.rs at 13.1 s13.1 s
  8. medigroup.rs at 15.0 s15.0 s

Speed

8 to fix39
  • Use efficient cache lifetimes

    3.3 s · 7.5 MB

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

  • Improve image delivery

    1.7 s · 2.1 MB

    9 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

  • Font display

    3.0 s

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

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 39

    39/100

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

  • Reduce unused CSS

    900 ms · 328 KiB

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

  • Reduce unused JavaScript

    150 ms · 804 KiB

    About 804 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 2,454 HTML elements

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

  • Minify JavaScript

    222 KiB

    222 KiB could be saved by minifying JavaScript.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Cookiebot, Cloudflare CDN and Google CDN and others), adding 292 KiB and 153 ms of main-thread time.

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    39 KiB

    Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need.

  • Minify CSS

    20 KiB

    20 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 131 ms

    131 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Time to Interactive: 34.7 s

    34.7 s

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

  • Speed Index: 13.5 s

    13.5 s

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

  • Cumulative Layout Shift: 0.842

    0.842

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

  • Largest Contentful Paint: 5.8 s

    5.8 s

    Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mesec muškog zdravlja - pregled urologa, movembar | MediGro…”.

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

6 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 99 ms

    99 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Total Blocking Time: 72 ms

    72 ms

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

Images and page weight

3 to fix45
  • Page weight: 8.0 MB in 77 requests

    8.0 MB

    Your homepage downloads 8.0 MB in 77 requests on a phone: scripts 3.3 MB (37), images 3.0 MB (10) and fonts 1.2 MB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    zakazite-ultrazvuk-abdomena-promo-mobile-baner-medigroup.jpg weighs 490 KiB. On a phone connection a single image that size takes seconds.

  • 6 images in older formats

    6 images (2.2 MB) 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 2.3 g of CO₂ per visit

    2.27 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8893
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 15 text elements with low contrast

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

  • 7 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

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

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

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

SEO

2 to fixGoogle 10088
  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “MediGroup - Vaš partner za zdravlje | Najveći privatni zdravstveni sistem”.

  • Meta description is long (175 characters)

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

  • 358 internal links, 24 external

    The homepage links to 358 pages on medigroup.rs and 24 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “MediGroup je najveći privatni zdravstveni sistem u regionu”.

  • Canonical URL set

    The canonical URL is https://www.medigroup.rs/.

  • Structured data in place

    Structured data found: DiagnosticLab, Organization 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.medigroup.rs/sitemaps.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.medigroup.rs/llms.txt (2 KiB, 18 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.medigroup.rs/lokacije, whose canonical is https://www.medigroup.rs/lokacije?city=all-cities&hospitaltype=all-locations-type. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.medigroup.rs/lekari, https://www.medigroup.rs/cenovnik, https://www.medigroup.rs/lab-kalkulator and https://www.medigroup.rs/promotivna-ponuda have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.medigroup.rs/usluge, https://www.medigroup.rs/lokacije/bolnice/opsta-bolnica-medigroup-novi-beograd, https://www.medigroup.rs/lokacije, https://www.medigroup.rs/lokacije/domovi-zdravlja/dijagnosticki-centar-slavija and https://www.medigroup.rs/lokacije/poliklinika-medigroup-kragujevac took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 261 words of copy

    The homepage carries about 261 words of visible text.

3 checks passed
  • 26 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 2 email links.

Privacy and tracking

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies, 1 of them by other companies (measured from a US location before any click).

  • 9 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • 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 medigroup.rs, 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
Microsoft Clarity
Hosting
Mainstream doo Beograd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on medigroup.rs, including 16 speed issues, 2 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